Setupmeta

Latest version: v3.8.0

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

Scan your dependencies

Page 3 of 9

3.0.0

------------------

* Yield PEP-440_ compliant versions

* Versions yielded by ``setupmeta`` 3.0 will differ from pre-3.0 versions:

* Character ``"+"`` is used exclusively to demarcate the local part of the version

* Character ``"."`` is used exclusively to demarcate local segments
(this is not configurable yet, and won't be unless by popular request)

* The "main" part remains intact, except for ``devcommit``, furthermore only known PEP-440
"main version part" bits can ever be in the main part (anything that is mistakenly
specified to be in the main part gets automatically shifted to the local part)

* "local" part is always shown now, no need to use ``"!"`` character (now deprecated),
except for ``{devcommit}`` and ``{dirty}`` markers, which will not lead to a local part
being shown when exactly on git tag.

* See [pep-440.rst](./docs/pep-440.rst) for more details

2.9.0

------------------

* Don't auto-complete ``classifiers`` from ``classifiers.txt`` any more,
the added value of that is negligible (and potentially confusing)

2.8.3

------------------

* Don't warn when bumping for the first time (with no git tags yet)

* Use the most common ``setuptools.find_packages()`` call (without arguments)

* Moved repo to https://github.com/codrsquad

2.8.2

------------------

* Respect ``requirements.in`` when present

2.8.1

------------------

* Explicitly state ``python_requires`` in ``setup.py`` to satisfy conda-forge linter

* Bundled tests in sdist, to allow for users wanting to rerun the tests to be able to do so from sdist

* Using https://pypi.org/project/check-manifest/

2.8.0

------------------

* Removed commands ``twine`` and ``uber_egg``, turns out they're not useful

Page 3 of 9

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.