Skip to content

Conversation

@gforcada
Copy link
Member

@gforcada gforcada commented Nov 21, 2025

Part of plone/Products.CMFPlone#3928

Seems that this package was using zope.meta rather than plone.meta, should we keep it this way, or move it to plone.meta as this PR is partially doing, probably it needs some adjustments, but as I'm doing the PRs for all native namespaces, I prefer to leave it half done here, and then I revisit it 😅

@mister-roboto
Copy link

@gforcada thanks for creating this Pull Request and helping to improve Plone!

TL;DR: Finish pushing changes, pass all other checks, then paste a comment:

@jenkins-plone-org please run jobs

To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass, but it takes 30-60 min. Other CI checks are usually much faster and the Plone Jenkins resources are limited, so when done pushing changes and all other checks pass either start all Jenkins PR jobs yourself, or simply add the comment above in this PR to start all the jobs automatically.

Happy hacking!

@coveralls
Copy link

coveralls commented Nov 23, 2025

Pull Request Test Coverage Report for Build 19616695035

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • 23 unchanged lines in 2 files lost coverage.
  • Overall coverage decreased (-11.6%) to 86.007%

Files with Coverage Reduction New Missed Lines %
src/plone/autoinclude/zcml.py 7 60.0%
src/plone/autoinclude/loader.py 16 81.99%
Totals Coverage Status
Change from base Build 18440828463: -11.6%
Covered Lines: 203
Relevant Lines: 230

💛 - Coveralls

@gforcada gforcada force-pushed the pep-420-native-namespace branch from afd068f to 86dd0a9 Compare November 23, 2025 09:12
@gforcada
Copy link
Member Author

@mauritsvanrees do we need the full 3.10-3.13 matrix for unit and integration, or could we save some CI cycles like we do on meta.yml and only run 3.10 and 3.13 ?

Other than that, the conversion from zope.meta to plone.meta seems to be fine eyeballing the diff

@mauritsvanrees
Copy link
Member

3.10 and 3.13 should be fine.

The paths need to be on one line.  Otherwise you get test outcome like this:

```
py313-integration: commands[1]> -test-path=test-packages/example.different/src
py313-integration: Exception running subprocess [Errno 2] No such file or directory: '-test-path=test-packages/example.different/src'
py313-integration: exit 2 (0.00 seconds) /Users/maurits/community/plone-coredev/6.2/src/plone.autoinclude> -test-path=test-packages/example.different/src
py313-integration: command failed but is marked ignore outcome so handling it as success
```
We had 'tests' and 'Tests'.
@mauritsvanrees
Copy link
Member

3.10 and 3.13 should be fine.

Actually, let's test them all. The tests don't take long. And they are the kind of tests where I fear there could be corner cases. On the other hand: it would be more useful to test on a range of setuptools versions, like we do in zc.buildout. But it's okay for now.

I did fix a problem in the integration tests, where the paths were wrong because the backslash at the end was removed. And somehow tox thought these errors could be ignored.

@mauritsvanrees mauritsvanrees merged commit 315be32 into main Nov 23, 2025
20 of 22 checks passed
@mauritsvanrees mauritsvanrees deleted the pep-420-native-namespace branch November 23, 2025 20:19
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.

5 participants