Skip to content

Compatibility with Python 3.12 or 3.13? #1015

Open

Description

@tianhuil

It looks like invoke only works up to Python 3.11. Is there any interest in moving up to later version of python? This is a great project and I haven't found a replacement for it! Please maintain it.

Activity

  1. alwaysmpe commented on Nov 22, 2024

    @alwaysmpe

    What problem are you having? I'm using invoke on 3.13 without problems (although the type annotations need refining) so it at least partially works

  2. SnoopJ commented on Dec 3, 2024

    @SnoopJ

    Not sure if there was a particular problem @tianhuil was having, but at the very least the classifier list and test environments do not go past Python 3.11 and should probably be updated to include those newer versions.

  3. sandeep-gh commented on Jan 16, 2025

    @sandeep-gh

    i am having this issue with python 3.12:

    from patchwork.files import exists
      File "/home/kabira/Development/cloudworks-monallabs/patchwork/patchwork/files.py", line 7, in <module>
        from invoke.vendor import six
    ImportError: cannot import name 'six' from 'invoke.vendor' (/home/adming/Execution/cloudworks/venv/lib/python3.12/site-packages/invoke/vendor/__init__.py)
    
    
  4. alwaysmpe commented on Jan 16, 2025

    @alwaysmpe

    @sandeep-gh that looks like a version problem, the main branch of invoke doesn't vendorize six, so you might need to get a different version of invoke, either one provided by the project you're using or an older version, or update the project you're using

  5. sandeep-gh commented on Jan 16, 2025

    @sandeep-gh

    yes, my bad. Its the patchwork module that has not been updated and is causing the problem.

  6. schwaerz commented on Feb 13, 2025

    @schwaerz

    There is a rather old ticket about one thing that does not work when running invoke in Windows with python 3.12+: #571

    As soon as you are trying to use any binary installed from pypi, invoke won't find them anymore with 3.12+.

  7. jbbqqf commented on May 24, 2026

    @jbbqqf

    Hi @tianhuil — drive-by triage check: I think this can be closed as resolved.

    Python 3.12, 3.13 and 3.14 are all supported on current main:

    If you're hitting a concrete failure on a specific 3.12/3.13/3.14 setup that's not already covered by a more recent issue (e.g. #1052 for one remaining 3.14 PTY case), it'd help to reopen with a minimal repro and the failing version. Otherwise this one looks safe to close.


    Drive-by triage from an outside contributor (data engineer GCP/Python, jbbqqf). Comment drafted with Claude assistance; evidence and conclusion are mine. Happy to be told I missed something.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions