Release 1.7 planning

I'm planning to make a 1.7 release around Nov 2 to Nov 6 (tentative timeline).

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 Oct 30.

This release will be the first one where we create the release blog post in the repo (either in CHANGELOG.md or in a temporary file which we'll add to CHANGELOG.md at the time of the release).

Here are some other major changes I'm hoping to include:

Enable --new-type-inference by default (subject to no major known regressions).
Enable TypeVarTuple by default.

I've encountered these (minor) regressions or potential regressions so far:

i'm not sure if this the right place to mention this but, you might need to add setuptools as a dependency for python 3.12+

i'm not sure if this the right place to mention this but, you might need to add setuptools as a dependency for python 3.12+

Already done in ff7ac75

It would be great to have:

These are all fixes for dmypy inspect, they should be all low-risk, as they don't touch "regular" daemon logic.

#15913 please

This was merged a while ago, so it will be included.

I've now cut the release branch: https://github.com/python/mypy/tree/release-1.7

We can still cherry-pick important/low-risk fixes and documentation updates.

May be good to add #16381 (Unpack crash fix)

Cherry-picked these PRs:

I wouldn't mind a cherry pick of #16407

I wrote 1.7 release notes in the changelog, which will be copied to the release blog post: https://github.com/python/mypy/blob/master/CHANGELOG.md

Please review. I'll leave a comment here when I've copied it to the blog, after which we shouldn't make any major changes to the changelog.

The release will probably go out tomorrow, 10 Nov, if I don't get distracted.

@JukkaL

@JukkaL Two comments on the blog post:

I think it is worth mentioning new --enable-incomplete-feature=PreciseTupleTypes. And maybe also in general mention that from now on we will try to use --enable-incomplete-feature as a more systematic way to try new features. Note there are some docs https://mypy.readthedocs.io/en/latest/command_line.html#enabling-incomplete-experimental-features, feel free to edit them if you want.
You refer to PEP 692 in description of TypedDict unpack. I think it may be worth mentioning that there are some intentional deviations from the PEP. The author of the PEP actually agrees it should be amended, but PEP is already accepted, so I don't know how they will sort it out. The summary is that unlike in the current edition of the PEP mypy always treats signatures with Unpack[SomeTypedDict] as equivalent to their expanded forms.

Another thing is that there are two crashes with TypeVarTuple (one came with a PR, I will merge it soon). Not sure what to do with this:

Trying to define a tuple with at least 1 element causes a crash if you try to define a tuple with *exactly* 1 element #16425
Overloaded def including TypeVarTuple and variable length Tuple crash #16427

Cherry-picked #16444.

Changelog updates: #16446 (I will leave it open for a while but will merge it fairly soon)

Mypy 1.7 is out: https://mypy-lang.blogspot.com/2023/11/mypy-17-released.html

Congrats with the release guys!

Sadly, I think I found a regression: #16451. Let me know if I can provide more details.

FYI, this release "regressed" pydantic usage. This snippet:

from pydantic import BaseModel

class Foo(BaseModel):
    pass

Now raises:

test.py:3: error: Explicit "Any" is not allowed  [misc]
    class Foo(BaseModel):
    ^~~~~~~~~~~~~~~~~~~~
test.py:3: error: Type of decorated function contains type "Any"
("Callable[[DefaultNamedArg(dict[str, Any] | None, '__pydantic_extra__'), DefaultNamedArg(set[str], '__pydantic_fields_set__'), DefaultNamedArg(dict[str, Any] | None, '__pydantic_private__')], None]")  [misc]
    class Foo(BaseModel):
    ^~~~~~~~~~~~~~~~~~~~
Found 2 errors in 1 file (checked 1 source file)

I'd guess that this behavior is correct... there is, in fact, an explicit Any in the BaseModel type definition, but it's going to mean a lot of code has to be updated to ignore this behavior.

@jessemyers-lettuce

@jessemyers-lettuce could you open a new issue with more details? I can't reproduce.

@hauntsaninja

@hauntsaninja Done. See #16454

Possible candidates for 1.7.1:

Two more potential candidates for 1.7.1:

Fix missing meet case exposed by len narrowing #16470 (technically can be seen a regression)
Ignore position if imprecise arguments are matched by name #16471 (less important, but one of the issues fixed is a regression in 1.6.0)

Another candidate from me for 1.7.1:

Fix crash on strict-equality with recursive types #16483

There may be a recent 1-2% perf regression, possibly related to some of the fixes that we are planning to include in 1.7.1. Perf data: https://github.com/mypyc/mypyc-benchmark-results/blob/master/reports/benchmarks/mypy_self_check.md

I'm planning to run some performance comparisons locally to get a better idea of whether there actually is a regression, since the automatically generated performance metrics are a bit noisy. The regression is small enough that even if it's real, we can probably proceed, but it seems worth it first check if there is some trivial fix.

I nominate #16484 for 1.7.1

@ilevkivskyi

Cherry-picked these PRs for the point release:

Thank you @ilevkivskyi for all the fixes!

I'm planning to publish 1.7.1 soon (either later today or tomorrow).

1.7.1 is out now.

Navigation Menu

Repository navigation

Release 1.7 planning #16341

4 remaining items

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Release 1.7 planning #16341

Description

Activity

JukkaL commented on Oct 27, 2023

KRRT7 commented on Oct 27, 2023

AlexWaygood commented on Oct 27, 2023

wRAR commented on Oct 28, 2023

ilevkivskyi commented on Oct 29, 2023

JukkaL commented on Oct 30, 2023

JukkaL commented on Oct 30, 2023

ilevkivskyi commented on Oct 31, 2023

JukkaL commented on Nov 1, 2023

hauntsaninja commented on Nov 6, 2023

JukkaL commented on Nov 9, 2023

ilevkivskyi commented on Nov 10, 2023

ilevkivskyi commented on Nov 10, 2023

4 remaining items

JukkaL commented on Nov 10, 2023

JukkaL commented on Nov 10, 2023

JukkaL commented on Nov 10, 2023

DanielNoord commented on Nov 10, 2023

jessemyers-lettuce commented on Nov 10, 2023

hauntsaninja commented on Nov 10, 2023

jessemyers-lettuce commented on Nov 11, 2023

ilevkivskyi commented on Nov 11, 2023

ilevkivskyi commented on Nov 12, 2023

ilevkivskyi commented on Nov 13, 2023

JukkaL commented on Nov 15, 2023

mr-c commented on Nov 16, 2023

JukkaL commented on Nov 22, 2023

JukkaL commented on Nov 23, 2023

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions