Visitar URL original
TODO list for Python 3.11 support · Issue #1516 · pylint-dev/astroid · GitHub
Skip to content

TODO list for Python 3.11 support #1516

Closed

Description

@DanielNoord

Activity

  1. added this to the 2.13.0 milestone on Apr 17, 2022
  2. cdce8p commented on Apr 22, 2022

    @cdce8p
    Member

    Some recent AST changes:

  3. rkhwaja commented on Jul 31, 2022

    @rkhwaja

    The wrapt dependency needs to be ">=1.14" for python 3.11. See changelog

  4. Pierre-Sassoulas commented on Jul 31, 2022

    @Pierre-Sassoulas
    Member

    @rkhwaja I think pip handle that, if pylint require wrapt >= 1.12 but python 3.11 require wrapt >= 1.14 then pip download >= 1.14. We should not change our lower bound, as we could imagine that wrapt >=1.14 is incompatible with python 3.7 and changing this would break pylint for python 3.7.

  5. rkhwaja commented on Aug 2, 2022

    @rkhwaja

    You could add a dependency like "wrapt>=1.14,<2;python_version>='3.11'" and then both the old and the new python will work.

    I don't know if you have other users than pylint but they would all just work too if you did it this way.

  6. Pierre-Sassoulas commented on Aug 2, 2022

    @Pierre-Sassoulas
    Member

    But is this required at all ? wrapt is the package that should handle the metadata about the pytho interpreters it supports and pip takes it into account.

  7. cdce8p commented on Aug 19, 2022

    @cdce8p
    Member

    But is this required at all ? wrapt is the package that should handle the metadata about the pytho interpreters it supports and pip takes it into account.

    Took me a moment to understand the issue. wrap doesn't pin a max supported version (which is the recommendation). Thus pip will happily install 1.12 even on python 3.11 if the dependency resolution requires it. However, only 1.14 is compatible. The options

    • Add wrapt>=1.14,<2;python_version>='3.11' like @rkhwaja suggested
    • Or just bump the min requirement to 1.14. 1.14 is compatible with Python >=3.5 so that wouldn't be an issue.
    • End-users can always add the wrapt>=1.14 constraint themselves. Although that won't fix existing environments.
  8. DanielNoord commented on Aug 21, 2022

    @DanielNoord
    CollaboratorAuthor
    • Or just bump the min requirement to 1.14. 1.14 is compatible with Python >=3.5 so that wouldn't be an issue.

    See #1745

  9. modified the milestones: 2.14.0, 2.15.0 on Jan 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions