-
-
Notifications
You must be signed in to change notification settings - Fork 711
Fix --with-python option not being honored when cache exists #41260
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
base: develop
Are you sure you want to change the base?
Conversation
When running ./configure with --with-python=pythonX.Y, if a previous configure run had cached a different Python path in ac_cv_path_PYTHON3, the cached value would be used instead of re-checking the specified Python. This fix clears the cache variable when --with-python is explicitly specified, forcing configure to always check the specified Python. Fixes sagemath#41258
|
@dimpase Can you test the issue is solved? |
|
I want to try this to compile sage in F43 with 3.13. As @dimpase pointed out it can be built with 3.14 but these do not pass, even though it can be used. I got: |
Have you done Hmm, it's probably this: I must say I don't know Fedora packaging: I see |
|
Yes, it installed 4 packages, that one, python3.13, python3.13-libs and python3.13-tkinter.
|
can you get |
How would I? Looking for a previous version? |
No, I don't don't understand why the package is listed here |
|
It is only in EPEL repository. |
can one install packages from there in Fedora 43? |
|
I tried unsuccesfully |
@jamesjer - is it normal that Fedora 43 has no fully functional Python 3.13 install? (One can argue that without setuptools package one can't do a lot of Python development) |
|
Yes, this is normal. On Fedora 43, the system python is version 3.14, and all other python packages were built with 3.14. There is a python3.13 package, but all you get is the bits distributed with python 3.13 itself. If you want other python packages for 3.13, such as setuptools, you have to build them yourself. Those doing python development will normally use python virtual environments to manage the various versions they work with. |
When running
./configure with --with-python=pythonX.Y, if a previousconfigure run had cached a different Python path in
ac_cv_path_PYTHON3,the cached value would be used instead of re-checking the specified Python.
This fix clears the cache variable when
--with-pythonis explicitlyspecified, forcing configure to always check the specified Python.
Fixes #41258
📝 Checklist
⌛ Dependencies