🚀 Motivation and context
When creating a dev environment, I encountered a number of issues with dependencies that turned out to be related to my version of Python to be too new.
First I attempted to stick with my system default 3.14 (maybe just too new at this moment in time) and then switched to 3.12 (middle of its support lifespan) but still facing those issues.
Roughly, the issues encountered:
pandas>=1.5.2 isn't enough any more. It's also required to add <3.0.0 because neither pytests nor pre-commits work with pandas 3.0.0
- pre-commit versions essentially all break.
mypy and flake8 failed because of deprecated ast
ufmt failed for some related reason
To recreate the problem: follow the dev env setup steps here using Python >=3.12 and run pytest and/or pre-commit run --all-files
Description
Bump pinned versions of dependencies so that newer versions of Python can be supported.
I'd have a PR ready and tested with 3.12 and 3.14 but following the suggested 'open issue to discuss' first. (see this branch for reference)
If desired, I could try my modified version with older versions of Python too. Please let me know what's the oldest one that should be supported.
Alternatives
Alternative could be to specify the range of supported versions of Python and dependencies in both documentation and requirements-files. Since Python 3.12 is already half-way down it's support life, this is probably the less desirable option?
Additional context
No response
🚀 Motivation and context
When creating a dev environment, I encountered a number of issues with dependencies that turned out to be related to my version of Python to be too new.
First I attempted to stick with my system default 3.14 (maybe just too new at this moment in time) and then switched to 3.12 (middle of its support lifespan) but still facing those issues.
Roughly, the issues encountered:
pandas>=1.5.2isn't enough any more. It's also required to add<3.0.0because neither pytests nor pre-commits work with pandas 3.0.0mypyandflake8failed because of deprecatedastufmtfailed for some related reasonTo recreate the problem: follow the dev env setup steps here using Python >=3.12 and run
pytestand/orpre-commit run --all-filesDescription
Bump pinned versions of dependencies so that newer versions of Python can be supported.
I'd have a PR ready and tested with 3.12 and 3.14 but following the suggested 'open issue to discuss' first. (see this branch for reference)
If desired, I could try my modified version with older versions of Python too. Please let me know what's the oldest one that should be supported.
Alternatives
Alternative could be to specify the range of supported versions of Python and dependencies in both documentation and requirements-files. Since Python 3.12 is already half-way down it's support life, this is probably the less desirable option?
Additional context
No response