Skip to content

Pep 420 native namespace - #98

Open
szakitibi wants to merge 2 commits into
collective:mainfrom
szakitibi:pep-420-native-namespace
Open

Pep 420 native namespace#98
szakitibi wants to merge 2 commits into
collective:mainfrom
szakitibi:pep-420-native-namespace

Conversation

@szakitibi

Copy link
Copy Markdown

This is a breaking change that we need for Plone 6.2, because setuptools dropped pkg_resources module near the end of 2025.

See also plone/Products.CMFPlone#3928.

@mamico
mamico self-requested a review July 1, 2026 09:44
@szakitibi

Copy link
Copy Markdown
Author

@mamico Is there a release manager for this product?

I see a few other PRs (#73, #86, #90, #96) have been merged in the past year, but no release since last May and version 2.0.0.

@mamico

mamico commented Aug 11, 2026

Copy link
Copy Markdown
Collaborator

@mamico Is there a release manager for this product?

I see a few other PRs (#73, #86, #90, #96) have been merged in the past year, but no release since last May and version 2.0.0.

@szakitibi In my opinion, there are currently no new features or bug fixes that require a new release. However, if you need a new release that includes this PR, I can do it.

@szakitibi

Copy link
Copy Markdown
Author

@szakitibi In my opinion, there are currently no new features or bug fixes that require a new release.

Indeed, currently there is no pressure for the release. The Plone 6.2.x-latest requirements has the horse-with-no-namespace out of box.

However the namespaces in the Plone ecosystem has been moved to PEP 420 already - see PLIP#3928. The plone, Products and collective namespace has most products released as PEP 420 compliant. The pas namespace has to be moved eventually, to keep up with Plone core. E.g. pas.plugins.ldap already has 2.0.0rc2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants