Setuptools

Latest version: v75.8.0

Safety actively analyzes 696915 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 85 of 114

8.0.4

Not secure
=====

* Upgrade ``packaging`` to 14.4, fixing an error where there is a
different result for if 2.0.5 is contained within >2.0dev and >2.0.dev even
though normalization rules should have made them equal.
* Issue 296: Add warning when a version is parsed as legacy. This warning will
make it easier for developers to recognize deprecated version numbers.

8.0.3

Not secure
=====

* Issue 296: Restored support for ``__hash__`` on parse_version results.

8.0.2

Not secure
=====

* Issue 296: Restored support for ``__getitem__`` and sort operations on
parse_version result.

8.0.1

Not secure
=====

* Issue 296: Restore support for iteration over parse_version result, but
deprecated that usage with a warning. Fixes failure with buildout.

8.0

Not secure
===

* Implement PEP 440 within
pkg_resources and setuptools. This change
deprecates some version numbers such that they will no longer be installable
without using the ``===`` escape hatch. See `the changes to test_resources
<https://bitbucket.org/pypa/setuptools/commits/dcd552da643c4448056de84c73d56da6d70769d5#chg-setuptools/tests/test_resources.py>`_
for specific examples of version numbers and specifiers that are no longer
supported. Setuptools now "vendors" the `packaging
<https://github.com/pypa/packaging>`_ library.

7.0

Not secure
===

* Issue 80, Issue 209: Eggs that are downloaded for ``setup_requires``,
``test_requires``, etc. are now placed in a ``./.eggs`` directory instead of
directly in the current directory. This choice of location means the files
can be readily managed (removed, ignored). Additionally,
later phases or invocations of setuptools will not detect the package as
already installed and ignore it for permanent install (See 209).

This change is indicated as backward-incompatible as installations that
depend on the installation in the current directory will need to account for
the new location. Systems that ignore ``*.egg`` will probably need to be
adapted to ignore ``.eggs``. The files will need to be manually moved or
will be retrieved again. Most use cases will require no attention.

Page 85 of 114

Links

Releases

Has known vulnerabilities

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.