GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Request to Declare Python 3.13 Compatibility on PyPI · Issue #2072 · gitpython-developers/GitPython

Request to Declare Python 3.13 Compatibility on PyPI #2072

New issue
Copy link
New issue
Copy link
Closed
Task
#2196
Closed
Request to Declare Python 3.13 Compatibility on PyPI#2072
Task
#2196
Copy link

Description

@grokas-splunk
grokas-splunk
opened on Sep 8, 2025
Issue body actions

Hey GitPython maintainers,

I am reaching out on behalf of Splunk SOAR, as part of our internal migration effort to Python 3.13.

What we’re requesting

  • Confirm whether this package is compatible with Python 3.13 (which I can see it is)
    • I can see CI tests being ran and passing against Python 3.13
  • Update the package metadata to reflect Python 3.13 compatibility for easier tracking and recognition, and publish a new PyPI release

Thanks a ton for your support in this matter.

Best,
Splunk SOAR Engineering Team

Reacted by Rick Otten

Activity

  1. EliahKagan commented on Sep 9, 2025

    @EliahKagan
    EliahKagan
    on Sep 9, 2025
    Member
    More actions

    GitPython is compatible with Python 3.13 on Unix-like systems, and it is believed to be mostly compatible with Python 3.13 on Windows, but there is an incompatibility due to a Windows-specific breaking change in Python 3.13 related to how one of the standard library functions classifies paths as relative or absolute.

    In practice, I think it is highly likely to work already for most users on Windows, but we do have a failing test on 3.13 on Windows, and there may be realistic scenarios where users on Windows would encounter problems with GitPython on Python 3.13--either in connection with the code exercised by that test, or in connection with other code that no test currently exercises in a way that relates to the incompatibility. (Regarding CI, we run CI on Python 3.13, but not with that version on Windows currently.)

    See #1955 for full details. I hope to get to this sometime soon, especially with Python 3.14 being just around the corner, but unfortunately I do not know when I'll get to it. Alternatively, if someone else wants to complete that, it would definitely be fine with me. I think that, at a minimum, the three "Windows:" steps related to absolute paths should be done before adding the classifier that explicitly declares Python 3.13 compatibility.

    I can imagine an argument for considering Windows to be a secondary platform, such that it would not have to wait on this. But I think many users of software that depends on GitPython are likely running Windows, so that would probably not be a good idea. @Byron please let me know if you have a position on this.

    Regarding the metadata, please note that while we do currently list trove classifiers indicating compatibility with some versions of Python that are well tested and specifically believed to be compatible, the actual hard specification states no upper bound and permits installation on Python 3.13 on all systems:

    GitPython/setup.py

    Line 77 in 2d4c541

    python_requires=">=3.7",

    However, I understand that's not a declaration that, in practice, there is no degradation on 3.13. Accordingly, I understand that this, by itself, is probably not what you're looking for.

  2. EliahKagan
    linked a pull request that will close this issueSupport Python 3.13 on Windows #1955on Sep 9, 2025
  3. Byron commented on Sep 9, 2025

    @Byron
    Byron
    on Sep 9, 2025
    Member
    More actions

    Thanks for looping me in.

    It's probably not possible to state compatibility for non-Windows systems only? Alternatively, is it possible to state experimental (or otherwise degraded) support?

    Any of the above would work today. Otherwise, I'd also want to wait until the issues on Windows have been resolved, probably something that has to happen on our side unless Python is recognising this as a bug - to use it's a regression for sure.

  4. EliahKagan commented on Sep 9, 2025

    @EliahKagan
    EliahKagan
    on Sep 9, 2025
    Member
    More actions

    unless Python is recognising this as a bug

    The breaking change from Python 3.12 to Python 3.13 on Windows in os.path.isabs was intentional, improves correctness of isabs itself (paths that start with only one directory separator on Windows are not absolute, because they are relative to the current drive), and makes os.path functionality more consistent with pathlib.Path. So I think the change is, overall, an improvement in Python's standard library, and won't likely be regarded as a bug there.

  5. Byron commented on Sep 9, 2025

    @Byron
    Byron
    on Sep 9, 2025
    Member
    More actions

    I see, so so GitPython would have to adjust its usage to be compatible.

  6. Byron
    added the
    Task
    issue type on Jul 20, 2026
  7. sciencewhiz commented on Jul 27, 2026

    @sciencewhiz
    sciencewhiz
    on Jul 27, 2026
    More actions

    3.1.56 declares support for python 3.13 (and .14 and .15), but doesn't fix the underlying path issue on windows.

    Reacted by Eliah Kagan
    Reacted by Eliah Kagan
  8. Byron commented on Jul 27, 2026

    @Byron
    Byron
    on Jul 27, 2026
    Member
    More actions

    Right, thanks for the heads-up. This happened, and somehow all other points mentioned in #1955 got lost. Will try to address them in a follow-up PR.

    Reacted by Eliah Kagan
    Reacted by Eliah Kagan
  9. Byron
    added 2 commits that reference this issue on Jul 28, 2026

    fix Windows path handling for Python 3.13+ (#1955) #(2072)

    8c0966f

    fix Windows path handling for Python 3.13+ (#1955) #(2072)

    f3391b0
  10. Byron
    added 2 commits that reference this issue on Aug 4, 2026

    fix Windows path handling for Python 3.13+ (#1955) #(2072)

    c3a4637

    fix Windows path handling for Python 3.13+ (#1955) #(2072)

    da58f39
  11. Byron
    closed this as completedin #2196on Aug 4, 2026
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

    Task

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.