Skip to content

Release 1.8 planning #16602

Closed
Closed

Description

@wesleywright

I'm planning to make a 1.8 release sometime around Dec 15.

Please post here any issues you'd like to see fixed in the release, or PRs you'd like to have merged. I'll cut the release branch around early next week.

### Tasks
- [ ] https://github.com/python/mypy/pull/16541
- [ ] https://github.com/python/mypy/pull/16608
- [x] Cherry-pick 16541 once landed
- [x] Cherry-pick 16608 once landed
- [x] cherry-pick 16655
- [ ] https://github.com/python/mypy/pull/16524

Activity

  1. self-assigned this
    on Dec 1, 2023
  2. added
    metaIssues tracking a broad area of work
    and removed on Dec 1, 2023
  3. AlexWaygood commented on Dec 3, 2023

    @AlexWaygood
    Member

    Sounds great! Here's a few PRs that might be worth considering:

  4. AlexWaygood commented on Dec 3, 2023

    @AlexWaygood
    Member

    There's a few more outstanding issues reporting regressions in mypy 1.7 that are worth noting, but I don't think any of them have PRs linked to them yet. I personally wouldn't hold up the 1.8 release for any of them:

  5. hauntsaninja commented on Dec 4, 2023

    @hauntsaninja
    Collaborator

    I'd like to see #16608 merged

  6. wesleywright commented on Dec 4, 2023

    @wesleywright
    CollaboratorAuthor

    I've cut a release-1.8 branch for this release. It's based on the latest master commit (7c33e7c) so it should already contain #16504, #16330, and #16513.

  7. wesleywright commented on Dec 7, 2023

    @wesleywright
    CollaboratorAuthor

    cherry-picked #16608 onto release-1.8

  8. wesleywright commented on Dec 12, 2023

    @wesleywright
    CollaboratorAuthor

    cherry-picked #16541. hopefully #16524 lands in the next couple of days.

  9. AlexWaygood commented on Dec 12, 2023

    @AlexWaygood
    Member

    Looks like our CI is broken on master (https://github.com/python/mypy/actions/runs/7186189373/job/19571043378), apparently because of pypa/hatch#1113. (We simulate various typed packages as part of our tests; they all use hatchling as their backend.)

  10. hauntsaninja commented on Dec 12, 2023

    @hauntsaninja
    Collaborator

    Thanks, #16655 to fix that. (We switched to hatchling because setuptools editable installs no longer work well with type checkers)

  11. hauntsaninja commented on Dec 13, 2023

    @hauntsaninja
    Collaborator

    I'd also say we shouldn't block 1.8 on #16524. I can make a point release for it whenever its merged.

  12. wesleywright commented on Dec 13, 2023

    @wesleywright
    CollaboratorAuthor

    Cherry-picked #16655. I'll likely finish out the release in the next couple of days; I'll cherry-pick #16524 if it lands before then, otherwise I'll just move forward.

  13. cdce8p commented on Dec 15, 2023

    @cdce8p
    Collaborator

    It might be a bit late but the last typeshed update #16665 includes some useful improvements for asyncio functions with callbacks. Those are among the first uses of TypeVarTuples in typeshed.

  14. wesleywright commented on Dec 21, 2023

    @wesleywright
    CollaboratorAuthor
  15. intgr commented on Dec 26, 2023

    @intgr
    Contributor

    @ymyzk Can you please add mypy 1.8.0 to mypy-play.net?

  16. ymyzk commented on Dec 26, 2023

    @ymyzk

    @intgr Thanks for the reminder. Yes, I just added mypy 1.8.0: https://mypy-play.net/?mypy=1.8.0&python=3.12&flags=version

  17. meshy commented on Jan 30, 2024

    @meshy
    Contributor

    Should this issue be closed now that 1.8 has been released?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

metaIssues tracking a broad area of work

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions