Skip to content

Stop supporting Python 3.4 to run mypy #6564

Closed

Description

@gvanrossum

Python 3.4 has reached its end of life: https://mail.python.org/pipermail/python-dev/2019-March/156705.html

We can still support targeting it with --python-version 3.4, but we should no longer feel bound to support running mypy with 3.4.

Activity

  1. ilevkivskyi commented on Mar 18, 2019

    @ilevkivskyi
    Member

    +1 from me. Some PRs fail on 3.4 because it has some syntax limitations, I think the latest example is Michael's union PR.

  2. JukkaL commented on Mar 19, 2019

    @JukkaL
    Collaborator

    Let's do this.

    I think that mypyc doesn't support 3.4. This means that once we ship a mypyc-compiled mypy by default, we should either drop 3.4 support or add Python 3.4 support to mypyc. The latter seems pointless because of the EoL, so dropping 3.4 support seems to make the most sense from this point of view as well.

  3. self-assigned this
    on Mar 26, 2019
  4. emmatyping commented on Mar 26, 2019

    @emmatyping
    Member

    Apologies, fat fingered. I am about ready with a PR.

  5. added a commit that references this issue on Mar 27, 2019
    affb032
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions