Accepting request 508196 from home:sebix

needed for python-shodan

OBS-URL: https://build.opensuse.org/request/show/508196
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-click-plugins?expand=0&rev=1

python-click-plugins.spec

@@ -0,0 +1,69 @@
+#
+# spec file for package python-click-plugins
+#
+# Copyright (c) 2017 SUSE LINUX GmbH, Nuernberg, Germany.
+#
+# All modifications and additions to the file contributed by third parties
+# remain the property of their copyright owners, unless otherwise agreed
+# upon. The license for this file, and modifications and additions to the
+# file, is the same license as for the pristine package itself (unless the
+# license for the pristine package is not an Open Source License, in which
+# case the license is the MIT License). An "Open Source License" is a
+# license that conforms to the Open Source Definition (Version 1.9)
+# published by the Open Source Initiative.
+
+# Please submit bugfixes or comments via http://bugs.opensuse.org/
+
+
+%{?!python_module:%define python_module() python-%{**} python3-%{**}}
+%bcond_without test
+Name:           python-click-plugins
+Version:        1.0.3
+Release:        0
+License:        BSD-3-Clause
+Summary:        An extension for click to register CLI commands via setuptools entry-points
+Url:            https://github.com/click-contrib/click-plugins
+Group:          Development/Languages/Python
+Source:         https://files.pythonhosted.org/packages/source/c/click-plugins/click-plugins-%{version}.tar.gz
+BuildRequires:  python-rpm-macros
+BuildRequires:  %{python_module devel}
+BuildRequires:  %{python_module setuptools}
+%if %{with test}
+BuildRequires:  %{python_module click >= 3.0}
+BuildRequires:  %{python_module pytest}
+%endif
+Requires:       %{python_module click >= 3.0}
+BuildRoot:      %{_tmppath}/%{name}-%{version}-build
+BuildArch:      noarch
+
+%python_subpackages
+
+%description
+Use a decorator to get setuptools entry points that allows others to use your commandline utility as a home for their related sub-commands. You get to choose where these sub-commands or sub-groups can be registered but the plugin developer gets to choose they ARE registered. You could have all plugins register alongside the core commands, in a special sub-group, across multiple sub-groups, or some combination.
+
+%prep
+%setup -q -n click-plugins-%{version}
+
+%build
+
+%python_build
+
+%install
+%python_install
+
+%if %{with test}
+%check
+%python_exec setup.py test
+%endif
+
+%files %{python_files}
+%defattr(-,root,root,-)
+%doc AUTHORS.txt CHANGES.md README.rst
+%if 0%{?leap_version} >= 420200 || 0%{?suse_version} > 1320
+%%license LICENSE.txt
+%else
+%doc LICENSE.txt
+%endif
+%{python_sitelib}/*
+
+%changelog