fedora-docs-l10n/fedora-release-notes/f36/pages/developers/Development_Python — English @ Fedora Weblate: >>> import sysconfig >>> for key in sysconfig.get_path

Source string Source string

English

>>> import sysconfig
>>> for key in sysconfig.get_path_names():
...     print(f'{key} = {sysconfig.get_path(key)}')
... 
stdlib = /usr/lib64/python3.10
platstdlib = /usr/lib64/python3.10
purelib = /usr/lib/python3.10/site-packages
platlib = /usr/lib64/python3.10/site-packages
include = /usr/include/python3.10
scripts = /usr/bin
data = /usr

Needs editing

The string is read only.

Skip

	English	Actions
	Python
	Setuptools 59
	Fedora Linux 36 provides _python-setuptools_ 59. This includes the removal of the `use_2to3` setup command. For more details, see the https://github.com/pypa/setuptools/blob/main/CHANGES.rst[upstream changelog].
	New installation scheme of Python packages
	In Fedora Linux 36, Python changes the way installation paths of Python packages are handled. These changes affect the main Python in Fedora 36, Python 3.10, as well as any newer Python version included. Most Fedora Linux users should not be affected by the change but there are situations where there might be slight differences.
	When Python packages are installed by `sudo pip`, `sudo python setup.py install` or similar methods, Python packages are installed to `/usr/local/lib(64)/python3.10/site-packages/`. This has already been https://fedoraproject.org/wiki/Changes/Making_sudo_pip_safe[happening since Fedora Linux 27]. However the way this is achieved has been significantly re-implemented in Fedora Linux 36 and that has created several minor differences.
	The `sysconfig` Python module from the standard library defines several installation schemes. By default, the installation scheme used on Fedora 36 when installing Python packages using root privileges (for example via `sudo`) is `{prefix}/lib(64)/python3.10/site-packages/`, where `{prefix}` is defined as `/usr/local` by default. When building RPM packages, `{prefix}` is defined as `/usr` by default. When Python itself runs from a Python virtual environment, `{prefix}` is defined as the path for the virtual environment.
	Previously, the `/local/` part was only artificially added when installing packages via `distutils`, now it is also defined in `sysconfig`. This was changed to be more consistent with what other Python distributors are doing, so that the scheme is more likely to be accepted in upstream Python and to work well with upstream tools like setuptools or pip, which we cannot modify when they are installed or upgraded using pip directly from the https://pypi.org/[Python Package Index].
	Here are the differences that might be observed with the new approach:
	`sysconfig.get_path(key)` returns paths with `/local/`
	Previously, on Fedora Linux 35 outside of a virtual environment:
	>>> import sysconfig >>> for key in sysconfig.get_path_names(): ... print(f'{key} = {sysconfig.get_path(key)}') ... stdlib = /usr/lib64/python3.10 platstdlib = /usr/lib64/python3.10 purelib = /usr/lib/python3.10/site-packages platlib = /usr/lib64/python3.10/site-packages include = /usr/include/python3.10 scripts = /usr/bin data = /usr
	Now, on Fedora Linux 36 (except during RPM build):
	>>> import sysconfig >>> for key in sysconfig.get_path_names(): ... print(f'{key} = {sysconfig.get_path(key)}') ... stdlib = /usr/lib64/python3.10 platstdlib = /usr/lib64/python3.10 purelib = /usr/local/lib/python3.10/site-packages platlib = /usr/local/lib64/python3.10/site-packages include = /usr/include/python3.10 scripts = /usr/local/bin data = /usr/local
	The values now reflect the reality of where packages are actually going to be installed with pip, setuptools, distutils, etc. However, if your Python code uses the values to determine where to load Python packages from, it won't see dnf-installed packages, which are installed in `/usr/lib(64)/python3.10/site-packages/`. Generally, `sysconfig.get_path(key)` gives results that determine where the Python packages should be installed to. To fix affected code, avoid assumptions that "where to install packages to" is the same as "where to load Python modules from".
	Example fixes from affected open source projects:
	https://github.com/rhinstaller/anaconda/pull/3646[anaconda/dracut: Don't assume Python modules are in sysconfig.get_path('purelib')]
	https://github.com/rpm-software-management/dnf/pull/1782[dnf: Determine the default plugin path at configure time, rather than runtime]
	If you need to restore the previous behavior of `sysconfig.get_path(key)`, you may explicitly set the `{base}` and `{platbase}` variables to `/usr`:
	>>> for key in sysconfig.get_path_names(): ... print(f'{key} = {sysconfig.get_path(key, vars={"base": "/usr", "platbase": "/usr"})}') ... stdlib = /usr/lib64/python3.10 platstdlib = /usr/lib64/python3.10 purelib = /usr/lib/python3.10/site-packages platlib = /usr/lib64/python3.10/site-packages include = /usr/include/python3.10 scripts = /usr/bin data = /usr
	RPM build–related caveats
	When Python runs during RPM build, it sets the defaults for `{base}` and `{platbase}` variables to `/usr`. This behavior is triggered when the `$RPM_BUILD_ROOT` environment variable is set. That has several caveats:
	Executing Python in Python's subprocess
	If the Python code that runs in RPM build (for example in `%check`) executes another Python instance via a subprocess, it is relatively easy to inadvertently unset all environment variables. When this happens, the inner Python will not know it runs within RPM build and will return paths with the `/usr/local/` prefix.
	In the most trivial example, the surrounding environment variables are implicitly passed to subprocess and everything works as expected:
	>>> import os, subprocess, sys >>> 'RPM_BUILD_ROOT' in os.environ True >>> command = [sys.executable, '-c', 'import sysconfig; print(sysconfig.get_path("purelib"))'] >>> subprocess.check_output(command) b'/usr/lib/python3.10/site-packages\n'
	But when a custom environment is passed, it breaks the detection, because `$RPM_BUILD_ROOT` is no longer set:

Loading…

None

String updated in the repository

English

English 342 characters edited Current translation Read only

a year ago

Browse all string changes

Things to check

Ellipsis

The string uses three dots (...) instead of an ellipsis character (…)

Reset

Glossary

English	English
No related strings found in the glossary.

String information

Source string description

type: delimited block -

Flags

no-wrap, read-only

Source string location

./pages/developers/Development_Python.adoc:52

String age

a year ago

Last updated

a year ago

Source string age

a year ago

Translation file

pot/f36/pages/developers/Development_Python.pot, string 12

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.