%global _empty_manifest_terminate_build 0 Name: python-semver Version: 3.0.0 Release: 1 Summary: Python helper for Semantic Versioning (https://semver.org) License: BSD URL: https://github.com/python-semver/python-semver Source0: https://mirrors.nju.edu.cn/pypi/web/packages/9f/93/b7389cdd7e573e70cfbeb4b0bbe101af1050a6681342f5d2bc6f1bf2d150/semver-3.0.0.tar.gz BuildArch: noarch %description A Python module for `semantic versioning`_. Simplifies comparing versions. |GHAction| |python-support| |downloads| |license| |docs| |black| |openissues| |GHDiscussion| This project works for Python 3.7 and greater only. If you are looking for a compatible version for Python 2, use the maintenance branch |MAINT|_. The last version of semver which supports Python 2.7 to 3.5 will be 2.x.y However, keep in mind, the major 2 release is frozen: no new features nor backports will be integrated. We recommend to upgrade your workflow to Python 3 to gain support, bugfixes, and new features. The module follows the ``MAJOR.MINOR.PATCH`` style: * ``MAJOR`` version when you make incompatible API changes, * ``MINOR`` version when you add functionality in a backwards compatible manner, and * ``PATCH`` version when you make backwards compatible bug fixes. Additional labels for pre-release and build metadata are supported. To import this library, use: >>> import semver Working with the library is quite straightforward. To turn a version string into the different parts, use the ``semver.Version.parse`` function: >>> ver = semver.Version.parse('1.2.3-pre.2+build.4') >>> ver.major 1 >>> ver.minor 2 >>> ver.patch 3 >>> ver.prerelease 'pre.2' >>> ver.build 'build.4' To raise parts of a version, there are a couple of functions available for you. The function ``semver.Version.bump_major`` leaves the original object untouched, but returns a new ``semver.Version`` instance with the raised major part: >>> ver = semver.Version.parse("3.4.5") >>> ver.bump_major() Version(major=4, minor=0, patch=0, prerelease=None, build=None) It is allowed to concatenate different "bump functions": >>> ver.bump_major().bump_minor() Version(major=4, minor=1, patch=0, prerelease=None, build=None) To compare two versions, semver provides the ``semver.compare`` function. The return value indicates the relationship between the first and second version: >>> semver.compare("1.0.0", "2.0.0") -1 >>> semver.compare("2.0.0", "1.0.0") 1 >>> semver.compare("2.0.0", "2.0.0") 0 There are other functions to discover. Read on! %package -n python3-semver Summary: Python helper for Semantic Versioning (https://semver.org) Provides: python-semver BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-semver A Python module for `semantic versioning`_. Simplifies comparing versions. |GHAction| |python-support| |downloads| |license| |docs| |black| |openissues| |GHDiscussion| This project works for Python 3.7 and greater only. If you are looking for a compatible version for Python 2, use the maintenance branch |MAINT|_. The last version of semver which supports Python 2.7 to 3.5 will be 2.x.y However, keep in mind, the major 2 release is frozen: no new features nor backports will be integrated. We recommend to upgrade your workflow to Python 3 to gain support, bugfixes, and new features. The module follows the ``MAJOR.MINOR.PATCH`` style: * ``MAJOR`` version when you make incompatible API changes, * ``MINOR`` version when you add functionality in a backwards compatible manner, and * ``PATCH`` version when you make backwards compatible bug fixes. Additional labels for pre-release and build metadata are supported. To import this library, use: >>> import semver Working with the library is quite straightforward. To turn a version string into the different parts, use the ``semver.Version.parse`` function: >>> ver = semver.Version.parse('1.2.3-pre.2+build.4') >>> ver.major 1 >>> ver.minor 2 >>> ver.patch 3 >>> ver.prerelease 'pre.2' >>> ver.build 'build.4' To raise parts of a version, there are a couple of functions available for you. The function ``semver.Version.bump_major`` leaves the original object untouched, but returns a new ``semver.Version`` instance with the raised major part: >>> ver = semver.Version.parse("3.4.5") >>> ver.bump_major() Version(major=4, minor=0, patch=0, prerelease=None, build=None) It is allowed to concatenate different "bump functions": >>> ver.bump_major().bump_minor() Version(major=4, minor=1, patch=0, prerelease=None, build=None) To compare two versions, semver provides the ``semver.compare`` function. The return value indicates the relationship between the first and second version: >>> semver.compare("1.0.0", "2.0.0") -1 >>> semver.compare("2.0.0", "1.0.0") 1 >>> semver.compare("2.0.0", "2.0.0") 0 There are other functions to discover. Read on! %package help Summary: Development documents and examples for semver Provides: python3-semver-doc %description help A Python module for `semantic versioning`_. Simplifies comparing versions. |GHAction| |python-support| |downloads| |license| |docs| |black| |openissues| |GHDiscussion| This project works for Python 3.7 and greater only. If you are looking for a compatible version for Python 2, use the maintenance branch |MAINT|_. The last version of semver which supports Python 2.7 to 3.5 will be 2.x.y However, keep in mind, the major 2 release is frozen: no new features nor backports will be integrated. We recommend to upgrade your workflow to Python 3 to gain support, bugfixes, and new features. The module follows the ``MAJOR.MINOR.PATCH`` style: * ``MAJOR`` version when you make incompatible API changes, * ``MINOR`` version when you add functionality in a backwards compatible manner, and * ``PATCH`` version when you make backwards compatible bug fixes. Additional labels for pre-release and build metadata are supported. To import this library, use: >>> import semver Working with the library is quite straightforward. To turn a version string into the different parts, use the ``semver.Version.parse`` function: >>> ver = semver.Version.parse('1.2.3-pre.2+build.4') >>> ver.major 1 >>> ver.minor 2 >>> ver.patch 3 >>> ver.prerelease 'pre.2' >>> ver.build 'build.4' To raise parts of a version, there are a couple of functions available for you. The function ``semver.Version.bump_major`` leaves the original object untouched, but returns a new ``semver.Version`` instance with the raised major part: >>> ver = semver.Version.parse("3.4.5") >>> ver.bump_major() Version(major=4, minor=0, patch=0, prerelease=None, build=None) It is allowed to concatenate different "bump functions": >>> ver.bump_major().bump_minor() Version(major=4, minor=1, patch=0, prerelease=None, build=None) To compare two versions, semver provides the ``semver.compare`` function. The return value indicates the relationship between the first and second version: >>> semver.compare("1.0.0", "2.0.0") -1 >>> semver.compare("2.0.0", "1.0.0") 1 >>> semver.compare("2.0.0", "2.0.0") 0 There are other functions to discover. Read on! %prep %autosetup -n semver-3.0.0 %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-semver -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Fri Apr 21 2023 Python_Bot - 3.0.0-1 - Package Spec generated