Skip to content

1.9.0 Release Tracking Issue #16843

Closed
Closed
@jhance

Description

@jhance
Collaborator

I will be cutting the release branch today (truly a January release!) and probably actually release sometime next week.

Please comment here if there are any outstanding PRs you wish to ensure are in the release branch. I will cherry-pick them if they are not merged before I cut the branch.

Activity

added
metaIssues tracking a broad area of work
on Jan 31, 2024
self-assigned this
on Jan 31, 2024
AlexWaygood

AlexWaygood commented on Jan 31, 2024

@AlexWaygood
Member

We haven't done a typeshed sync in a while; we might want to do one before the next release. The automated one two weeks ago failed due to merge conflicts with the cherry-picked commits: https://github.com/python/mypy/actions/runs/7522542054

cdce8p

cdce8p commented on Jan 31, 2024

@cdce8p
Collaborator

I would really love to see this one included. It's a simple one line fix (+ tests), that just needs a review.

This here would be nice as well, although I need to investigate one small issue first

jhance

jhance commented on Jan 31, 2024

@jhance
CollaboratorAuthor

#16844 for typeshed sync. Thanks for pointing that out.

hauntsaninja

hauntsaninja commented on Jan 31, 2024

@hauntsaninja
Collaborator

Could be nice to have #15043 in 1.9

jhance

jhance commented on Feb 6, 2024

@jhance
CollaboratorAuthor

The release branch is up (delayed due to typeshed 3.7 issue). So far it looks pretty good - I've tested it on our internal codebase and all the errors seem like they are the fault of our code, not of mypy.

I don't think we are going to block on #15043 for this release, because while the PR itself is apparently ok, it doesn't actually fix the issue completely that its trying to address. Releases are monthly (and this one, like all the ones I do, is late) so we could probably get it + more fixes in for next release.

hauntsaninja

hauntsaninja commented on Feb 7, 2024

@hauntsaninja
Collaborator

It might be worth cherry picking python/typeshed#11353

AlexWaygood

AlexWaygood commented on Feb 7, 2024

@AlexWaygood
Member

It might be worth cherry picking python/typeshed#11353

No need — it's already in the release-1.9 branch (we did two typeshed syncs in quick succession)

cdce8p

cdce8p commented on Feb 7, 2024

@cdce8p
Collaborator

Not sure if it's worth mentioning yet. The release will include support for basic TypeVar defaults PEP 696. Would be great to have some more early testers. An example from the PEP

class Bot: ...

BotT = TypeVar("BotT", bound=Bot, default=Bot)

class Context(Generic[BotT]):
    bot: BotT

class MyBot(Bot): ...

reveal_type(Context().bot)         # type is Bot  # notice this is not Any which is what it would be currently
reveal_type(Context[MyBot]().bot)  # type is MyBot

Important

Not yet working / supported

  • Defaults for TypeVarTuples
  • Defaults which reference other TypeVars
  • The new syntax but I think that is obvious as mypy doesn't support PEP 695 yet.
cdce8p

cdce8p commented on Feb 12, 2024

@cdce8p
Collaborator

@jhance What's the current status? Anything we can help with? AFAICT it's just removing the +dev version suffix and the blog post. Would be awesome to get the release out soon 🔥🚀

11 remaining items

Loading
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

      Participants

      @jhance@svalentin@JelleZijlstra@hauntsaninja@DanielNoord

      Issue actions

        1.9.0 Release Tracking Issue · Issue #16843 · python/mypy