Support installing CPython 3.13.0a2+ with the `--disable-gil` flag

[edgarrmondragon]

Support installing CPython 3.13.0a2+ with the `--disable-gil` flag

[native-api]

You can pass any custom Configure options via the PYTHON_CONFIGURE_OPTS envvar. See https://github.com/pyenv/pyenv/blob/master/plugins/python-build/README.md#special-environment-variables .

[edgarrmondragon]

@native-api Gotcha, that seemed to work. For reference:

$ PYTHON_CONFIGURE_OPTS='--disable-gil' pyenv install 3.13-dev
$ pyenv shell 3.13-dev
$ python3.13 -c 'import sysconfig; print(sysconfig.get_config_var("Py_GIL_DISABLED"))'
1

Thanks!

[native-api]

Is there a way to install two 3.13-dev versions but to different directories to test builds both with enabled and disabled gil? Pyenv-alias plugin does not work any more, just renaming folders will break the installation.

It is possible by calling Python-build directly. See its --help and README.

[ZmicierGT]

Is there a way to install two 3.13-dev versions but to different directories to test builds both with enabled and disabled gil? Pyenv-alias plugin does not work any more, just renaming folders will break the installation.

[ZmicierGT]

@native-api Thank you, it helped. Some details for those who'll search for it in the future. You may find python-build readme here. The sequence of commands I used:

% python-build 3.13-dev /Users/zmicier/.pyenv/versions/3.13-dev_gil
% PYTHON_CONFIGURE_OPTS='--disable-gil' pyenv install 3.13-dev
% pyenv shell 3.13-dev_gil
% python3.13 -c 'import sysconfig; print(sysconfig.get_config_var("Py_GIL_DISABLED"))'
0
% pyenv shell 3.13-dev
% python3.13 -c 'import sysconfig; print(sysconfig.get_config_var("Py_GIL_DISABLED"))'
1

However, seems that the current nogil implementation is less stable than the experimental nogil 3.9.10 fork.