-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Adapt to executable naming in the free-threaded build #2965
Comments
As a workaround, you can use a custom build definition that removes the
|
If I had to guess, this is because they added a python3.13t executable to the build:
|
Upgrade Pyenv to the latest release which has #2960 |
Thanks for diagnosing! I switched to using pyenv from a clone of the repo so I can update faster. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Prerequisite
pyenv
and the defaultpython-build
plugin only. Please refrain from reporting issues of other plugins here.Description
env PYENV_DEBUG=1 <faulty command> 2>&1 | tee trace.log
and attachtrace.log
. E.g. if you have a problem with installing Python, runenv PYENV_DEBUG=1 pyenv install -v <version> 2>&1 | tee trace.log
(note the-v
option topyenv install
).config.log
from the build directory/tmp
.env PYENV_DEBUG=1 pyenv install -f -k -v <version> 2>&1 | tee trace.log
config.log
from the build directory. When usingpyenv install
with-k
as per above, the build directory will be under$PYENV_ROOT/sources
.This used to work (#2851) but seems to have broken recently.
Lots of output, that ends with:
trace.log: https://gist.github.com/ngoldbaum/ed263d2bf0e30f31b573a1d7cfa04c5b
config.log: https://gist.github.com/ngoldbaum/ff670ca701780008ebd46598bee9e728
The text was updated successfully, but these errors were encountered: