Setuptools

Latest version: v69.5.1

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

Page 77 of 109

11.3

Not secure

====

* Expose ``EntryPoint.resolve`` in place of EntryPoint._load, implementing the
simple, non-requiring load. Deprecated all uses of ``EntryPoint._load``
except for calling with no parameters, which is just a shortcut for
``ep.require(); ep.resolve();``.

Apps currently invoking ``ep.load(require=False)`` should instead do the
following if wanting to avoid the deprecating warning::

getattr(ep, "resolve", lambda: ep.load(require=False))()

11.2

Not secure

====

* Pip 2326: Report deprecation warning at stacklevel 2 for easier diagnosis.

11.1

Not secure

====

* Issue 281: Since Setuptools 6.1 (Issue 268), a ValueError would be raised
in certain cases where VersionConflict was raised with two arguments, which
occurred in ``pkg_resources.WorkingSet.find``. This release adds support
for indicating the dependent packages while maintaining support for
a VersionConflict when no dependent package context is known. New unit tests
now capture the expected interface.

11.0

Not secure

====

* Interop 3: Upgrade to Packaging 15.0; updates to PEP 440 so that >1.7 does
not exclude 1.7.1 but does exclude 1.7.0 and 1.7.0.post1.

10.2.1

Not secure

======

* Issue 323: Fix regression in entry point name parsing.

10.2

Not secure

====

* Deprecated use of EntryPoint.load(require=False). Passing a boolean to a
function to select behavior is an anti-pattern. Instead use
``Entrypoint._load()``.
* Substantial refactoring of all unit tests. Tests are now much leaner and
re-use a lot of fixtures and contexts for better clarity of purpose.

Page 77 of 109

Releases

Has known vulnerabilities

Previous Next

Setuptools

Page 77 of 109

11.3

11.2

11.1

11.0

10.2.1

10.2

Page 77 of 109

Links

Releases