Pyroma

Latest version: v4.2

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

Scan your dependencies

Page 6 of 7

1.5

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

- Fixed issue 13: Pyroma would fail if there was no description.

- Dropping support for Python 3.1. It still works, but it is unsupported.

- Added support for command line options, implementing 14 and 15.

1.4

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

- Issue 13: Pyroma would fail when checking a package name if no source
distribution could be found.

- Added a check that the package has a source distribution on PyPI.

1.3.1

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

- Issue 11: pyroma would fail if long_description was a non-string.

- zest.releaser now only runs Pyroma on Python packages.

- Because packages that use external test-runners can not get more
that 9/10, this value is now also seen as acceptable when running
Pyroma through zest.releaser.

1.3

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

- Added a test to make sure the version number is a string.

- Made sure errors were printed also when a fatal error was encountered.

- Better log messages.

- The zest.releaser hook is now done before tagging, as it's more useful there.
Especially in conjunction with check-manifest.

- Having no long_description no longer causes pyroma to fail.

1.2

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

- Removed the running of tests. I always found it a bit iffy, and getting
rid of it solved a lot of issues. Pyroma is now focused solely on
packaging quality.

- A package on PyPI with several versions will no longer return an error.

- Now looks for documentation on pythonhosted.org or readthedocs.org.

- Adds a hook for zest.releaser, so it can be run after doing the checkout,
before uploading to PyPI.

1.1

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

- Better handling if there is no package data, for example if setup.py doesn't
call setup() unless you run it as the "__main__" script.

- If setup.py doesn't call setup() look for a main() script and try to run it.

Page 6 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.