Pep 420 native namespace

[szakitibi]

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.

[szakitibi]

@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 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]

@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.

[mauritsvanrees]

LGTM, and seems especially logical since we don't use setuptools as build-system here.