%global _empty_manifest_terminate_build 0 Name: python-Setuptools-Autometa Version: 0.1.1.post3 Release: 1 Summary: Add autometa keyword to the setuptools.setup function which automatically fills version, description and long_description keywords License: BSD URL: https://przybys.eu/software/setuptools-autometa Source0: https://mirrors.aliyun.com/pypi/web/packages/28/c6/36a7d55f487b1bfe39e24181a1e84ea7a49f3db9eb8610b2fb061e8d0395/Setuptools-Autometa-0.1.1.post3.tar.gz BuildArch: noarch %description To use it, pass the module (without .py), or the package name as the autometa keyword argument for setup():: #! /usr/bin/env python from setuptools import setup setup( autometa='test', name='Test', packages=['test'], ... ) Setuptools-Autometa will parse the specified module or package's __init__.py and set version to its __version__ attribute, description to the first line of its docstring, and long_description to the rest of the docstring. Additionally build_sphinx command's version and release options will be set. For example following package's __init__.py:: """First line of docstring. Many more lines of docstring. """ __version__ = '1.2.3.dev0' # alternatively: (1, 2, 3, 'dev0') Is equivalent to writing:: setup( version='1.2.3.dev0', description='First line of docstring', long_description='Many\nmore\nlines\nof\ndocstring.' ... ) **NOTE:** Please note, that the version is parsed by running `ast.literal_eval`_ on the right side of the assignment to __version__, so keep in mind that it can only be a string literal, or a list/tuple of string/integer literals. **NOTE:** Setuptools-Autometa assumes a `PEP 0257`_ compliant docstring, that is its first line has to end with a period and be separated from the description by a blank line. Additionally you can whitelist which fields are to be parsed by using the autometa_fields keyword argument and setting it to an iterable of field names ('description', 'long_description', 'version'). .. _`ast.literal_eval`: https://docs.python.org/3/library/ast.html#ast.literal_eval .. _`PEP 0257`: https://www.python.org/dev/peps/pep-0257 %package -n python3-Setuptools-Autometa Summary: Add autometa keyword to the setuptools.setup function which automatically fills version, description and long_description keywords Provides: python-Setuptools-Autometa BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-Setuptools-Autometa To use it, pass the module (without .py), or the package name as the autometa keyword argument for setup():: #! /usr/bin/env python from setuptools import setup setup( autometa='test', name='Test', packages=['test'], ... ) Setuptools-Autometa will parse the specified module or package's __init__.py and set version to its __version__ attribute, description to the first line of its docstring, and long_description to the rest of the docstring. Additionally build_sphinx command's version and release options will be set. For example following package's __init__.py:: """First line of docstring. Many more lines of docstring. """ __version__ = '1.2.3.dev0' # alternatively: (1, 2, 3, 'dev0') Is equivalent to writing:: setup( version='1.2.3.dev0', description='First line of docstring', long_description='Many\nmore\nlines\nof\ndocstring.' ... ) **NOTE:** Please note, that the version is parsed by running `ast.literal_eval`_ on the right side of the assignment to __version__, so keep in mind that it can only be a string literal, or a list/tuple of string/integer literals. **NOTE:** Setuptools-Autometa assumes a `PEP 0257`_ compliant docstring, that is its first line has to end with a period and be separated from the description by a blank line. Additionally you can whitelist which fields are to be parsed by using the autometa_fields keyword argument and setting it to an iterable of field names ('description', 'long_description', 'version'). .. _`ast.literal_eval`: https://docs.python.org/3/library/ast.html#ast.literal_eval .. _`PEP 0257`: https://www.python.org/dev/peps/pep-0257 %package help Summary: Development documents and examples for Setuptools-Autometa Provides: python3-Setuptools-Autometa-doc %description help To use it, pass the module (without .py), or the package name as the autometa keyword argument for setup():: #! /usr/bin/env python from setuptools import setup setup( autometa='test', name='Test', packages=['test'], ... ) Setuptools-Autometa will parse the specified module or package's __init__.py and set version to its __version__ attribute, description to the first line of its docstring, and long_description to the rest of the docstring. Additionally build_sphinx command's version and release options will be set. For example following package's __init__.py:: """First line of docstring. Many more lines of docstring. """ __version__ = '1.2.3.dev0' # alternatively: (1, 2, 3, 'dev0') Is equivalent to writing:: setup( version='1.2.3.dev0', description='First line of docstring', long_description='Many\nmore\nlines\nof\ndocstring.' ... ) **NOTE:** Please note, that the version is parsed by running `ast.literal_eval`_ on the right side of the assignment to __version__, so keep in mind that it can only be a string literal, or a list/tuple of string/integer literals. **NOTE:** Setuptools-Autometa assumes a `PEP 0257`_ compliant docstring, that is its first line has to end with a period and be separated from the description by a blank line. Additionally you can whitelist which fields are to be parsed by using the autometa_fields keyword argument and setting it to an iterable of field names ('description', 'long_description', 'version'). .. _`ast.literal_eval`: https://docs.python.org/3/library/ast.html#ast.literal_eval .. _`PEP 0257`: https://www.python.org/dev/peps/pep-0257 %prep %autosetup -n Setuptools-Autometa-0.1.1.post3 %build %py3_build %install %py3_install install -d -m755 %{buildroot}/%{_pkgdocdir} if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi pushd %{buildroot} if [ -d usr/lib ]; then find usr/lib -type f -printf "\"/%h/%f\"\n" >> filelist.lst fi if [ -d usr/lib64 ]; then find usr/lib64 -type f -printf "\"/%h/%f\"\n" >> filelist.lst fi if [ -d usr/bin ]; then find usr/bin -type f -printf "\"/%h/%f\"\n" >> filelist.lst fi if [ -d usr/sbin ]; then find usr/sbin -type f -printf "\"/%h/%f\"\n" >> filelist.lst fi touch doclist.lst if [ -d usr/share/man ]; then find usr/share/man -type f -printf "\"/%h/%f.gz\"\n" >> doclist.lst fi popd mv %{buildroot}/filelist.lst . mv %{buildroot}/doclist.lst . %files -n python3-Setuptools-Autometa -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Tue Jun 20 2023 Python_Bot - 0.1.1.post3-1 - Package Spec generated