-
Notifications
You must be signed in to change notification settings - Fork 881
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python 3.13 support #4284
Comments
#4100 should unblock Python 3.13. But I'm a bit unsure about the CI failure (it wasn't there before), and I'm looking into it. For some reason I cannot recreate that error (which looks like some float point number precision issue) on my Ubuntu machine running Python 3.13. Maybe be some dependency-related constant update or something.
|
thanks so much for working on this @DanielYang59! 🥇 i see you're way ahead of me :) the difference is small so maybe numerics and based on the doc string, the class being tested maybe should have been removed by now anyway. so i think safe enough to just update the expected value to the new actual pymatgen/src/pymatgen/analysis/eos.py Lines 511 to 541 in ee65dca
|
No problem at all!
I would have a look at the reason and let me you (if I could find it), because currently it could be reliably recreated in CI. Maybe some constant get updated at certain version, probably similar to: |
Unfortunately I'm unable to recreate this issue nor find the reason after some time debugging, this is what I know so far:
Above results are generated with the same Python (3.13.2), scipy(1.15.1) and numpy (1.26.4) versions, only noticeable difference is GitHub CI runner is now using Ubuntu 24.04 (my local machine is still Ubuntu 22.04) As the result is generated with |
pymatgen
currently pinspython<3.13
pymatgen/pyproject.toml
Line 24 in 5b997f7
The text was updated successfully, but these errors were encountered: