Release 1.1 planning #14730
Copy link
Copy link
Closed
Labels
Description
I'm planning to make release 1.1 by the end of February.
Please post here any issues you'd like to see fixed in the release, or PRs you'd like to have merged into the release branch
Reactions are currently unavailable
Activity
Avasam commentedon Feb 18, 2023
It's small, but I'd really like #14437 for QoL improvement in stubtest.
Another typeshed QoL improvement (and mypy bug with aliased properties) that would be nice is #13975 / #6700
and stubtest name mangling weirdness: #14560
Out of all my issues, these are the 3 I care more about right now and would also help typeshed.
cdce8p commentedon Feb 19, 2023
Fix for a crash with
dataclass_transformFix crash withdataclass_transformcache #14734Edit:
release-1.1.--
Additionally, this one would resolve one of the issues with
pydanticdataclasses. The other one needs to be fixed by pydantic itself.hauntsaninja commentedon Feb 22, 2023
+1 to getting in the currently open dataclass_transform PRs
ichard26 commentedon Feb 23, 2023
koogoro commentedon Feb 24, 2023
It looks like #14437 was included in the base of the release branch, and #14695 and #14752 have been cherry-picked.
hauntsaninja commentedon Feb 27, 2023
Could cherry pick #14792
tmke8 commentedon Mar 1, 2023
Support for
@overridewould be nice. The following PR implements it:But there was an open question about the interaction with
@overload.koogoro commentedon Mar 2, 2023
Cherry-picked #14792. It might be better to wait for the next release for a new feature, since the release is already a bit late at this point.
AlexWaygood commentedon Mar 2, 2023
Argh, you might have to cherry-pick these two to fix the mypyc build on the 1.1 branch — sorry:
types-setuptoolsbuild dependency #14787AlexWaygood commentedon Mar 2, 2023
Here's a PR to fix the mypyc build on the 1.1. branch:
Viicos commentedon Mar 5, 2023
By any chance do you think this one could be included as well?
__new__#14471It has been requested by a couple of people, and unfortunately I'm kind of stuck on this one. If you think it is fixable without too much hassle I'd be grateful to get help on this one!
(I'm posting it here as it might be considered as a feature and not a fix according to the new release versioning scheme).
koogoro commentedon Mar 6, 2023
@Viicos Let's wait on this change until the next release. These are intended to happen monthly, so it shouldn't be too long until the next one. In general, I'd prefer not to cherry-pick changes onto the release at this point unless it's fixing a bug that would be introduced by this release.
Viicos commentedon Mar 6, 2023
Sure thanks for the answer. There's no hurry for this one anyway
koogoro commentedon Mar 7, 2023
Release made! Here's the blog post: https://mypy-lang.blogspot.com/2023/03/mypy-111-released.html
(The version number is 1.1.1 since 1.1.0 was not building on wheels.)
I'll keep this open for a little bit to track potential bugs introduced in this release that we'd want to create an expedited 1.1.2 release for.
AlexWaygood commentedon Mar 7, 2023
We've just had a regression reported over at typeshed:
This regression was caused by python/typeshed#9362. It's already been fixed on the typeshed
mainbranch via python/typeshed#9758, but the fix didn't make it into 1.1.1. (This is my error.)koogoro commentedon Mar 8, 2023
#14853 might be a candidate for a point release if the fix is simple enough.
jchalupka-pan commentedon Mar 10, 2023
@koogoro The issue has been fixed. Not hurrying up of course, I just don't know if you have been notified somehow :)
wesleywright commentedon Mar 11, 2023
I've got a couple of dataclass_transform fixes inflight:
AlexWaygood commentedon Mar 11, 2023
This fixes a (minor) regression; could be worth backporting: