Check-manifest

Latest version: v0.50

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

Scan your dependencies

Page 8 of 8

0.9

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

* Add suggestion pattern for `.travis.yml`.

* When check-manifest -u (or -c) doesn't know how to write a rule matching a
particular file, it now apologizes explicitly.

* Copy the source tree to a temporary directory before running python setup.py
sdist to avoid side effects from setuptools plugins or stale
\*.egg-info/SOURCES.txt files
(`issue 1 <https://github.com/mgedmin/check-manifest/issues/1>`_).

* Warn if `*.egg-info` or `*.mo` is actually checked into the VCS.

* Don't complain if `*.mo` files are present in the sdist but not in the VCS
(`issue 2 <https://github.com/mgedmin/check-manifest/issues/2>`_).

0.8

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

* Entry point for zest.releaser_. If you install both zest.releaser and
check-manifest, you will be asked if you want to check your manifest during
``fullrelease``.

.. _zest.releaser: https://pypi.python.org/pypi/zest.releaser

0.7

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

* First release available from the Python Package Index.

* Moved from https://gist.github.com/4277075
to https://github.com/mgedmin/check-manifest

* Added README.rst, CHANGES.rst, setup.py, tox.ini (but no real tests yet),
MANIFEST.in, and a Makefile.

* Fixed a bug in error reporting (when setup.py failed, the user would get
`TypeError: descriptor '__init__' requires an 'exceptions.Exception' object
but received a 'str'`).

Page 8 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.