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.
- Devel package for openSUSE:Factory
-
49
derived packages
- Links to openSUSE:Factory / python-setuptools
- Has a link diff
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout devel:languages:python/python-setuptools && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
_link | 0000000124 124 Bytes | |
fix-sle11-test-failure.patch | 0000000592 592 Bytes | |
psfl.txt | 0000011900 11.6 KB | |
python-setuptools.changes | 0000059236 57.8 KB | |
python-setuptools.spec | 0000003665 3.58 KB | |
setuptools-36.0.1.zip | 0000711296 695 KB | |
zpl.txt | 0000002366 2.31 KB |
Revision 111 (latest revision is 279)
Dirk Mueller (dirkmueller)
committed
(revision 111)
- update to 36.0.1 * #1042: Fix import in py27compat module that still referenced six directly, rather than through the externs module (vendored packages hook). * #980 and others: Once again, Setuptools vendors all of its dependencies. It seems to be the case that in the Python ecosystem, all build tools must run without any dependencies (build, runtime, or otherwise). At such a point that a mechanism exists that allows build tools to have dependencies, Setuptools will adopt it. * #1015: Fix test failures on Python 3.7. * #1024: Add workaround for Jython #2581 in monkey module. * #992: Revert change introduced in v34.4.1, now considered invalid. * #1016: Revert change introduced in v35.0.0 per #1014, referencing #436. The approach had unintended consequences, causing sdist installs to be missing files.
Comments 2
I noticed that the package also contains windows executeables. Should we ship those?
I don't think that we need those .exe, I've just removed it.