native-api
native-api
Both the interpreters are free-threaded. See https://github.com/orgs/pyenv/discussions/2998#discussioncomment-9919105 . ``` $ pyenv shell 3.14t-dev $ python3.14t -c 'import sysconfig; print(sysconfig.get_config_var("Py_GIL_DISABLED"))' 1 $ python3.14 -c 'import sysconfig; print(sysconfig.get_config_var("Py_GIL_DISABLED"))' 1 ```
We did this because that's what the build produces. This is how it's supposed to be in Linux, according to @hugovk . I doubt we'll be doing users a favor...
> Exactly, which differs from how the Python.org installer works. The key word is _installer_ . If you check the discussion on the link, the installer contains _two_ builds of...
That's intended. In fact, not excluding alphas from the get-go was an oversight.
We excluded unstable versions from auto-resolution on an assumption that otherwise, it would always resolve to an unstable version -- as the closest to the bleeding edge -- while most...
> I guess my thought is that something should be done in the case where there is no stable version available. If I enter `3.12`, it can't resolve to a...
My best idea is a `--prerelease` switch for `pyenv latest` which would include prereleases -- but not `-dev` as otherwise it would always prevail. Not sure if we should fall...
> My best idea is a `--prerelease` switch for `pyenv latest` which would include prereleases Maybe we should even *only* include prereleases.
Please upgrade Pyenv to 2.4.8
Basic documentation added in https://github.com/pyenv/pyenv/pull/2916