Skip to content

Release 0.940 planning #12021

Closed
Closed
@JukkaL

Description

@JukkaL

I'm planning to make a 0.940 release in February (tentative timeline). If things go according to plan, I'd cut the release branch in the first half of February.

Here are some things that I'd like to have in the release:

We also need at least one typeshed sync.

Any help with the above issues would be greatly appreciated!

Please post here any issues you'd like to see fixed in the release, or PRs you'd like to have merged. After cutting the release branch, only high-priority fixes can be cherry-picked.

Activity

AlexWaygood

AlexWaygood commented on Jan 19, 2022

@AlexWaygood
Member

For typeshed, having the following issues fixed would be really nice, if at all possible (I'm trying to work on a solution for the first two in #11915 -- but note that it'll only work for stub files; the bugs will still be there for .py files):

cdce8p

cdce8p commented on Jan 19, 2022

@cdce8p
Collaborator

I would like to suggest my PR from summer last year. It's something that already works in pyright. Once mypy supports it the remaining type checkers might consider it too if they haven't already. It could help cut down duplicate overload definitions in typeshed. The PR is fully tested and only waiting for review.

hauntsaninja

hauntsaninja commented on Jan 19, 2022

@hauntsaninja
Collaborator

I have an almost green typeshed sync here: #11905
It's currently blocked on a single regression (which in my mind isn't a release blocker)

I'd like to get #12023 merged (the crash is blocking me at work / has been reported many times).

#12005 is an issue we should fix (somewhat, but not fully related to #11887 which we should also fix, but is trickier and not quite as bad).

henryiii

henryiii commented on Jan 19, 2022

@henryiii
Contributor

I'd really like to see Self support make it in, since it's in typing_extensions and supported by several other type checkers, and was just accepted by the SC. But understandable if it isn't finished in time.

RJPercival

RJPercival commented on Feb 1, 2022

@RJPercival

Is there any chance of getting a v0.932 in the meantime so that we can get fixes for #11850 and #12132 (enum bugs) released please? These bugs have made mypy unusable for my project.

intgr

intgr commented on Feb 2, 2022

@intgr
Contributor

I, for one, would prefer a release of functionality that is already merged, on a shorter timescale. I would very much like to see mypy adopt time-based releases, rather than going through a feature crunch that sometimes delays useful working contributions for months.

The wait for version 0.920 was literally painful for me and my team. Now I'm waiting for support for match statement that was merged 2 weeks ago. It's not perfect, but it's better than the current state of even not being able to suppress warnings on match statements (#11829).

hauntsaninja

hauntsaninja commented on Feb 17, 2022

@hauntsaninja
Collaborator

@JukkaL thoughts on release timeline? master is starting to accumulate a number of nice fixes (including some that would be appreciated at my day job)

JukkaL

JukkaL commented on Feb 18, 2022

@JukkaL
CollaboratorAuthor

Sorry for the delay! We've had a few(!) viruses going through our family in the last weeks. I was only able to start work on the release yesterday. Since we are late, I'm thinking of focusing on 3.10 features and low-risk changes only. This would mean postponing at least this change to the next release:

I agree that the release process hasn't been going too smoothly in the last several releases. We can discuss options for speeding up releases separately. I've been working on some process changes that may make it feasible to switch to monthly releases, for example, but we'd probably need one or two extra volunteer release managers to help share the work. I opened #12210 to discuss the release process.

JukkaL

JukkaL commented on Feb 18, 2022

@JukkaL
CollaboratorAuthor

Here's the rough priority order of my next tasks:

  1. Investigate and fix/work around some regressions I've found (including Temporary moratorium on literal constants (until the end of 2022) typeshed#7258)
  2. Python 3.10 feature work (match statement, ParamSpec improvements) (time boxed)
  3. Merge other fixes and improvements (time boxed)
  4. Make the release!

31 remaining items

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @srittau@wrobell@intgr@JelleZijlstra@JukkaL

        Issue actions

          Release 0.940 planning · Issue #12021 · python/mypy