Plone.autoinclude

Latest version: v2.0.2

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

Scan your dependencies

Page 1 of 2

2.0.2

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

Bug fixes:


- If a distribution is not found, try to normalize the name like recent setuptools is doing and try again [ale-rt] (32)

2.0.1

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

Bug fixes:


- Replace ``pkg_resources`` with ``importlib.metadata``/``importlib.resources``. [gforcada] (4126)

2.0.0

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

Breaking changes:


- Support Plone 6.0, 6.1, 6.2, Python 3.9-3.13, and Buildout 4.
Drop support for older Plone, Python and Buildout versions.
Drop support for PyPy. Technically it may still work, but we no longer test it. It is irrelevant for Plone.
[maurits] (24)


Bug fixes:


- Fix importing module when the module name differs from the project name.
This can easily happen with ``setuptools`` 75.8.1, though maybe 75.8.2 fixes it in some cases.
[maurits] (25)

1.0.1

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

Bug fixes:


- Revert "Use setuptools/pkg_resources regex to compute safe name for a project" to fix an error importing packages with dashes. [davisagli] (22)

1.0.0

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

Bug fixes:


- Use setuptools/pkg_resources regex to compute safe name for a project.
[gforcada] (17)

1.0.0a5

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

New features:


- Raise an exception when a module is not found.
When environment variable ``AUTOINCLUDE_ALLOW_MODULE_NOT_FOUND_ERROR=1`` is set, we log an error and continue.
To accept ``ModuleNotFoundError`` only in specific packages, use a comma-separated list of project names, with or without spaces.
See `issue 19 <https://github.com/plone/plone.autoinclude/issues/19>`_.
[maurits] (19)

Page 1 of 2

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.