Skip to content

Release 1.1 planning #14730

Closed
Closed

Description

@koogoro

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

Activity

  1. added
    metaIssues tracking a broad area of work
    and removed on Feb 18, 2023
  2. Avasam commented on Feb 18, 2023

    @Avasam
    SponsorContributor

    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.

  3. cdce8p commented on Feb 19, 2023

    @cdce8p
    Collaborator

    Fix for a crash with dataclass_transform

    Edit:

    --
    Additionally, this one would resolve one of the issues with pydantic dataclasses. The other one needs to be fixed by pydantic itself.

  4. hauntsaninja commented on Feb 22, 2023

    @hauntsaninja
    Collaborator

    +1 to getting in the currently open dataclass_transform PRs

  5. ichard26 commented on Feb 23, 2023

    @ichard26
  6. koogoro commented on Feb 24, 2023

    @koogoro
    CollaboratorAuthor

    It looks like #14437 was included in the base of the release branch, and #14695 and #14752 have been cherry-picked.

  7. hauntsaninja commented on Feb 27, 2023

    @hauntsaninja
    Collaborator

    Could cherry pick #14792

  8. tmke8 commented on Mar 1, 2023

    @tmke8
    Contributor

    Support for @override would be nice. The following PR implements it:

    But there was an open question about the interaction with @overload.

  9. koogoro commented on Mar 2, 2023

    @koogoro
    CollaboratorAuthor

    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.

  10. AlexWaygood commented on Mar 2, 2023

    @AlexWaygood
    Member

    Argh, you might have to cherry-pick these two to fix the mypyc build on the 1.1 branch — sorry:

  11. AlexWaygood commented on Mar 2, 2023

    @AlexWaygood
    Member

    Here's a PR to fix the mypyc build on the 1.1. branch:

  12. Viicos commented on Mar 5, 2023

    @Viicos
    Contributor

    By any chance do you think this one could be included as well?

    It 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).

  13. koogoro commented on Mar 6, 2023

    @koogoro
    CollaboratorAuthor

    @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.

  14. Viicos commented on Mar 6, 2023

    @Viicos
    Contributor

    @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.

    Sure thanks for the answer. There's no hurry for this one anyway

  15. koogoro commented on Mar 7, 2023

    @koogoro
    CollaboratorAuthor

    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.

  16. AlexWaygood commented on Mar 7, 2023

    @AlexWaygood
    Member

    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 main branch via python/typeshed#9758, but the fix didn't make it into 1.1.1. (This is my error.)

  17. koogoro commented on Mar 8, 2023

    @koogoro
    CollaboratorAuthor

    #14853 might be a candidate for a point release if the fix is simple enough.

  18. jchalupka-pan commented on Mar 10, 2023

    @jchalupka-pan

    #14853 might be a candidate for a point release if the fix is simple enough.

    @koogoro The issue has been fixed. Not hurrying up of course, I just don't know if you have been notified somehow :)

  19. wesleywright commented on Mar 11, 2023

    @wesleywright
    Collaborator

    I've got a couple of dataclass_transform fixes inflight:

  20. AlexWaygood commented on Mar 11, 2023

    @AlexWaygood
    Member

    This fixes a (minor) regression; could be worth backporting:

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

      Issue actions