-
Notifications
You must be signed in to change notification settings - Fork 38
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
Fails to build with Python 3.13 #1677
Comments
Thanks @vedranmiletic for the report. For now, please try lower version since 3.13 is too new. Thanks. |
@hainm Thanks for the quick response. By the way, I would, but it is not my choice to make. I am packaging AmberTools in Arch User Repository and Arch Linux recently moved to Python 3.13 as the default version. |
I am not familiar with the Arch User Repository, but is there some way to "pin" python to a given version? As an additional example, parts of AmberTools (I'm not sure about pytraj), still require version 1.26 of numpy, rather than the current version 2. And we know you will find problems if/when Arch upgrades to gcc14. Of course, this dependency issue is a big part of what makes package managers like But in any event, thanks for your work in this area. If you find code changes that would make AmberTools more compatible with current upstream software, let us know -- that would help everyone, not just the Arch Linux folks. |
In theory, yes. In practice this means that each user has to compile Python 3.12 before compiling AmberTools, and for me this is no go. I am considering depending on Miniforge (which includes 3.12) instead of that, but I would prefer patching software.
If that is the
Arch Linux has already upgraded to GCC 14, but GCC 13 is provided as a binary since CUDA needs it so we can easily depend on that.
True, it is what it is. Furthermore, Arch is rolling-release with all advantages and disadvantages of that.
Great! I would be glad to upstream the patches so I don't have to carry them locally. For a start I patched a CUDA CMake config file to allow using CUDA 12.6 (the only version provided by Arch), but that file is not part of AmberClassic. Where should I submit a patch? |
Noticed this when building AmberTools 24:
The text was updated successfully, but these errors were encountered: