Skip to content

Make untagged versions PEP 440-compliant#394

Open
savannahostrowski wants to merge 4 commits into
python:mainfrom
savannahostrowski:pep-440-version
Open

Make untagged versions PEP 440-compliant#394
savannahostrowski wants to merge 4 commits into
python:mainfrom
savannahostrowski:pep-440-version

Conversation

@savannahostrowski
Copy link
Copy Markdown
Member

@ned-deily
Copy link
Copy Markdown
Member

While making this change, it would be good to also address the updating of the README file (#169).

@hugovk
Copy link
Copy Markdown
Member

hugovk commented May 26, 2026

In python/cpython#99968 (comment) you suggested targeting at least 3.16 onward, although this PR applies to all of 3.10-3.16.

If we only target 3.16, this won't have any affect until after the first 3.16 alpha in October (it's on 3.16.0a0 until then). I think it's okay to also apply this to the 3.15 beta, to help shake out any issues.

Shall we do that for a few 3.15 releases before applying it to the full set, or just go for them all now?

@savannahostrowski
Copy link
Copy Markdown
Member Author

@hugovk If you're cool with that, I think 3.15+ would be great. I've pushed a change for that.

@ned-deily I think I'd prefer to tackle this in a separate PR so we can keep this one scoped on the PEP 440 compliance. I've assigned myself to #169 though, so I can look at that next.

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.

3 participants