Download, build, install, upgrade, and uninstall Python packages -- easily!
setuptools is a collection of enhancements to the Python distutils (for Python 2.3 and up) that allow you to more easily build and distribute Python packages, especially ones that have dependencies on other packages.
- Developed at devel:languages:python
-
21
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory/python-setuptools && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
fix-sle11-test-failure.patch | 0000000592 592 Bytes | |
psfl.txt | 0000011900 11.6 KB | |
python-setuptools.changes | 0000054407 53.1 KB | |
python-setuptools.spec | 0000004058 3.96 KB | |
setuptools-26.1.1.tar.gz | 0000637041 622 KB | |
setuptools-5.4.1-create-sitedir.patch | 0000000767 767 Bytes | |
setuptools-certpath.patch | 0000000684 684 Bytes | |
zpl.txt | 0000002366 2.31 KB |
Revision 25 (latest revision is 81)
Dominique Leuenberger (dimstar_suse)
accepted
request 424067
from
Jan Matejek (matejcik)
(revision 25)
- fix certificate handling with certifi, add support for SUSE's CA bundle (setuptools-certpath.patch, fixes boo#993968) - remove shebang lines, strip executable bit from README, to silence the easy rpmlint warnings - update to 26.1.1: * Re-release of 26.1.0 with pytest pinned to allow for automated deployement and thus proper packaging environment variables, fixing issues with missing executable launchers. * #763: ``pkg_resources.get_default_cache`` now defers to the `appdirs project <https://pypi.org/project/appdirs>`_ to resolve the cache directory. Adds a vendored dependency on appdirs to pkg_resources. * #748: By default, sdists are now produced in gzipped tarfile format by default on all platforms, adding forward compatibility for the same behavior in Python 3.6 (See Python #27819). * #459 via #736: On Windows with script launchers, sys.argv[0] now reflects the name of the entry point, consistent with the behavior in distlib and pip wrappers. * #752 via #753: When indicating ``py_limited_api`` to Extension, it must be passed as a keyword argument. * Add Extension(py_limited_api=True). When set to a truthy value, that extension gets a filename apropriate for code using Py_LIMITED_API. When used correctly this allows a single compiled extension to work on all future versions of CPython 3. The py_limited_api argument only controls the filename. To be compatible with multiple versions of Python 3, the C extension will also need to set -DPy_LIMITED_API=... and be modified to use only the functions in the limited API.
Comments 0