Skip to content

1.16 Release Planning #18739

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jhance opened this issue Feb 25, 2025 · 8 comments
Open

1.16 Release Planning #18739

jhance opened this issue Feb 25, 2025 · 8 comments
Assignees
Labels
meta Issues tracking a broad area of work

Comments

@jhance
Copy link
Collaborator

jhance commented Feb 25, 2025

I am planning to release 1.16 in the coming weeks.

If there are any PRs you would like to ensure are included, please mention here.

This issue will be updated once the release branch is cut.

@jhance jhance self-assigned this Feb 25, 2025
@jhance jhance added the meta Issues tracking a broad area of work label Feb 25, 2025
@hauntsaninja
Copy link
Collaborator

hauntsaninja commented Mar 7, 2025

Note there's a crash on mypy master we may want to address #18764

Update: fixed by Ivan

@ilevkivskyi
Copy link
Member

@cdce8p
Copy link
Collaborator

cdce8p commented Apr 4, 2025

What's the current status here? Has the release branch been cut already?

If not, I'd suggest to do it after the current typeshed sync #18880. This is the last commit with support for type checking Python 3.8. For the next typeshed sync, we'll need to drop support for --python-version 3.8 completely. Might be great to get one last release out before that.

@svalentin
Copy link
Collaborator

If possible, we should include #18906 in the new release. It fixes high pri daemon bug

@jorenham
Copy link
Contributor

If not, I'd suggest to do it after the current typeshed sync #18880. This is the last commit with support for type checking Python 3.8. For the next typeshed sync, we'll need to drop support for --python-version 3.8 completely. Might be great to get one last release out before that.

Why not just drop 3.8? It has been EOL for over 6 months now

@cdce8p
Copy link
Collaborator

cdce8p commented Apr 16, 2025

Why not just drop 3.8? It has been EOL for over 6 months now

We already dropped 3.8. It's just that mypy still supports checking 3.8 code with --python-version 3.8 for now. This will become impossible with the next typeshed update #18930.

@jorenham
Copy link
Contributor

Hmm that's too bad. Because #18930 contains ctypes improvements (python/typeshed#13777 and python/typeshed#13760) that matter to numpy.

@cdce8p
Copy link
Collaborator

cdce8p commented Apr 16, 2025

Hmm that's too bad. Because #18930 contains ctypes improvements (python/typeshed#13777 and python/typeshed#13760) that matter to numpy.

I'd be fine with dropping it now as well. The idea just was to do one last release before then. The release branch could have even been cut already. I just don't know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Issues tracking a broad area of work
Projects
None yet
Development

No branches or pull requests

6 participants