%global _empty_manifest_terminate_build 0 Name: python-entrypoints Version: 0.4 Release: 1 Summary: Discover and load entry points from installed packages. License: MIT License URL: https://github.com/takluyver/entrypoints Source0: https://mirrors.nju.edu.cn/pypi/web/packages/ea/8d/a7121ffe5f402dc015277d2d31eb82d2187334503a011c18f2e78ecbb9b2/entrypoints-0.4.tar.gz BuildArch: noarch %description **This package is in maintenance-only mode.** New code should use the `importlib.metadata module `_ in the Python standard library to find and load entry points. Entry points are a way for Python packages to advertise objects with some common interface. The most common examples are ``console_scripts`` entry points, which define shell commands by identifying a Python function to run. *Groups* of entry points, such as ``console_scripts``, point to objects with similar interfaces. An application might use a group to find its plugins, or multiple groups if it has different kinds of plugins. The **entrypoints** module contains functions to find and load entry points. You can install it from PyPI with ``pip install entrypoints``. To advertise entry points when distributing a package, see `entry_points in the Python Packaging User Guide `_. The ``pkg_resources`` module distributed with ``setuptools`` provides a way to discover entrypoints as well, but it contains other functionality unrelated to entrypoint discovery, and it does a lot of work at import time. Merely *importing* ``pkg_resources`` causes it to scan the files of all installed packages. Thus, in environments where a large number of packages are installed, importing ``pkg_resources`` can be very slow (several seconds). By contrast, ``entrypoints`` is focused solely on entrypoint discovery and it is faster. Importing ``entrypoints`` does not scan anything, and getting a given entrypoint group performs a more focused scan. When there are multiple versions of the same distribution in different directories on ``sys.path``, ``entrypoints`` follows the rule that the first one wins. In most cases, this follows the logic of imports. Similarly, Entrypoints relies on ``pip`` to ensure that only one ``.dist-info`` or ``.egg-info`` directory exists for each installed package. There is no reliable way to pick which of several `.dist-info` folders accurately relates to the importable modules. %package -n python3-entrypoints Summary: Discover and load entry points from installed packages. Provides: python-entrypoints BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-entrypoints **This package is in maintenance-only mode.** New code should use the `importlib.metadata module `_ in the Python standard library to find and load entry points. Entry points are a way for Python packages to advertise objects with some common interface. The most common examples are ``console_scripts`` entry points, which define shell commands by identifying a Python function to run. *Groups* of entry points, such as ``console_scripts``, point to objects with similar interfaces. An application might use a group to find its plugins, or multiple groups if it has different kinds of plugins. The **entrypoints** module contains functions to find and load entry points. You can install it from PyPI with ``pip install entrypoints``. To advertise entry points when distributing a package, see `entry_points in the Python Packaging User Guide `_. The ``pkg_resources`` module distributed with ``setuptools`` provides a way to discover entrypoints as well, but it contains other functionality unrelated to entrypoint discovery, and it does a lot of work at import time. Merely *importing* ``pkg_resources`` causes it to scan the files of all installed packages. Thus, in environments where a large number of packages are installed, importing ``pkg_resources`` can be very slow (several seconds). By contrast, ``entrypoints`` is focused solely on entrypoint discovery and it is faster. Importing ``entrypoints`` does not scan anything, and getting a given entrypoint group performs a more focused scan. When there are multiple versions of the same distribution in different directories on ``sys.path``, ``entrypoints`` follows the rule that the first one wins. In most cases, this follows the logic of imports. Similarly, Entrypoints relies on ``pip`` to ensure that only one ``.dist-info`` or ``.egg-info`` directory exists for each installed package. There is no reliable way to pick which of several `.dist-info` folders accurately relates to the importable modules. %package help Summary: Development documents and examples for entrypoints Provides: python3-entrypoints-doc %description help **This package is in maintenance-only mode.** New code should use the `importlib.metadata module `_ in the Python standard library to find and load entry points. Entry points are a way for Python packages to advertise objects with some common interface. The most common examples are ``console_scripts`` entry points, which define shell commands by identifying a Python function to run. *Groups* of entry points, such as ``console_scripts``, point to objects with similar interfaces. An application might use a group to find its plugins, or multiple groups if it has different kinds of plugins. The **entrypoints** module contains functions to find and load entry points. You can install it from PyPI with ``pip install entrypoints``. To advertise entry points when distributing a package, see `entry_points in the Python Packaging User Guide `_. The ``pkg_resources`` module distributed with ``setuptools`` provides a way to discover entrypoints as well, but it contains other functionality unrelated to entrypoint discovery, and it does a lot of work at import time. Merely *importing* ``pkg_resources`` causes it to scan the files of all installed packages. Thus, in environments where a large number of packages are installed, importing ``pkg_resources`` can be very slow (several seconds). By contrast, ``entrypoints`` is focused solely on entrypoint discovery and it is faster. Importing ``entrypoints`` does not scan anything, and getting a given entrypoint group performs a more focused scan. When there are multiple versions of the same distribution in different directories on ``sys.path``, ``entrypoints`` follows the rule that the first one wins. In most cases, this follows the logic of imports. Similarly, Entrypoints relies on ``pip`` to ensure that only one ``.dist-info`` or ``.egg-info`` directory exists for each installed package. There is no reliable way to pick which of several `.dist-info` folders accurately relates to the importable modules. %prep %autosetup -n entrypoints-0.4 %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-entrypoints -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Fri Apr 21 2023 Python_Bot - 0.4-1 - Package Spec generated