Skip to content

Conversation

@gforcada
Copy link
Member

@gforcada gforcada commented Dec 5, 2025

Closes #115

Copy link
Member

@davisagli davisagli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would change the default, not remove the support for the others. If we do remove it, we should raise a clear error in case a template is still explicitly requesting one of the no longer supported values.

@gforcada
Copy link
Member Author

gforcada commented Dec 6, 2025

Fair point, let me amend the MR then

@gforcada
Copy link
Member Author

gforcada commented Dec 6, 2025

Changed 🎉 Now it should no longer be a breaking change, but a feature.

@gforcada gforcada requested a review from davisagli December 6, 2025 09:03
Change the default value when creating python namespaces to use the
native namespace option (available since Python 3.3).

Setuptools is about (end of 2025) to drop support for the other two styles,
so it is time to move on.
@gforcada gforcada merged commit 42c7807 into main Dec 16, 2025
7 checks passed
@gforcada gforcada deleted the native-namespaces branch December 16, 2025 06:53
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.

Create native namespaces

3 participants