Closed
Description
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:
- Reachability/exhaustiveness checking for match statements #12010
- Basic ParamSpec Concatenate and literal support #11847
- Make --namespace-packages the default #9636
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.
Metadata
Metadata
Assignees
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
AlexWaygood commentedon Jan 19, 2022
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):.py
files, but now fixed for stub files by Fix "Implicit type aliases not recognised with PEP 604 + import cycles" (but only for stubs) #11915 🥳TypeAlias
with new union syntax (PEP 604) #11098(Mutable)Sequence
is imported fromcollections.abc
intypeshed/stdlib/builtins.pyi
#11860cdce8p commentedon Jan 19, 2022
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 commentedon Jan 19, 2022
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 commentedon Jan 19, 2022
I'd really like to see
Self
support make it in, since it's intyping_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 commentedon Feb 1, 2022
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 commentedon Feb 2, 2022
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 onmatch
statements (#11829).sobolevn commentedon Feb 6, 2022
List of my PRs that I would like to see in this release.
Easy
Enum
StrEnum
support for python3.11 #12035Enum
definition for invalid base classes #12026Enum
type #11805Dataclasses
__hash__
method to@dataclasses.dataclass
, refs #11463 #11496match_args
support toattr.s()
#12111match_args
support toattr.s()
#12111python2
raise Exception(), None
on Python2.7 #11786__truediv__
for python2 with__future__
import, refs #11740 #11787TypeGuard
TypeGuard
type outside of.ret_type
, refs #11765 #11790TypeGuard
, refs #11780 #11797More complex ones
Most of the PRs below will change inference:
Literal
type math #11992**
affects inference in{}
expressions, refs #11691 #11693if
expr #11128self
are handled properly #11366Hashable
as a real protocol, refs #11799 #11802Cache related:
@classmethod
and@staticmethod
were not shown in error messages when cached #11793Most of them aren't reviewed yet 🙂
filecmp
are missingPathlike
forcommon
argument python/typeshed#7034hauntsaninja commentedon Feb 17, 2022
@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 commentedon Feb 18, 2022
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 commentedon Feb 18, 2022
Here's the rough priority order of my next tasks:
31 remaining items