Skip to content

Conversation

bmispelon
Copy link
Member

No description provided.

@bmispelon bmispelon changed the title Switched to Python 3.12 [WIP] Switched to Python 3.12 Oct 29, 2024
@bmispelon
Copy link
Member Author

TODO: need to do something about the PYTHONWARNINGS failing.

@bmispelon bmispelon mentioned this pull request Nov 1, 2024
@bmispelon
Copy link
Member Author

Trac does not (officially) support Python 3.12 (I couldn't find a link to their Python support policy, but it's not listed in the trove classifiers on https://pypi.org/project/Trac/).

Because our Trac test suite is not super solid, I'm a bit hesitant with moving to 3.12.

Instead, I suggest we run Trac on 3.11 which will let us update Django 5.0 (and even 5.1).

@bmispelon bmispelon closed this Nov 1, 2024
@bmispelon bmispelon deleted the py312 branch November 1, 2024 19:49
@bmispelon bmispelon mentioned this pull request Nov 1, 2024
@pauloxnet
Copy link
Member

Trac does not (officially) support Python 3.12 (I couldn't find a link to their Python support policy, but it's not listed in the trove classifiers on https://pypi.org/project/Trac/).

In didn't know that. I added a comment in the Trac's issue 13774.

Because our Trac test suite is not super solid, I'm a bit hesitant with moving to 3.12.
Instead, I suggest we run Trac on 3.11 which will let us update Django 5.0 (and even 5.1).

I agree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants