sysconfig
— 提供对 Python 配置信息的访问
¶
Added in version 3.2.
源代码：
Lib/sysconfig
The
sysconfig
模块提供对 Python 配置信息的访问，像安装路径列表和当前平台相关配置变量。
配置变量
¶
Python 分发包含
Makefile
和
pyconfig.h
头文件是必要的，以构建 Python 二进制文件本身和编译第三方 C 扩展使用
setuptools
.
sysconfig
将在这些文件中找到的所有变量放在字典中，可以访问使用
get_config_vars()
or
get_config_var()
.
注意，在 Windows，其集要小得多。
-
sysconfig.
get_config_vars
(
*
args
)
¶
-
不带自变量，返回当前平台相关的所有配置变量字典。
带自变量，返回在配置变量字典中找到每个自变量结果的值列表。
对于每个自变量，若找不到值，返回
None
.
-
sysconfig.
get_config_var
(
名称
)
¶
-
返回值为单变量
name
。相当于
get_config_vars().get(name)
.
若
name
找不到，返回
None
.
用法范例：
>>> import sysconfig
>>> sysconfig.get_config_var('Py_ENABLE_SHARED')
0
>>> sysconfig.get_config_var('LIBDIR')
'/usr/local/lib'
>>> sysconfig.get_config_vars('AR', 'CXX')
['ar', 'g++']
安装路径
¶
Python uses an installation scheme that differs depending on the platform and on the installation options. These schemes are stored in
sysconfig
under unique identifiers based on the value returned by
os.name
. The schemes are used by package installers to determine where to copy files to.
Python currently supports nine schemes:
-
posix_prefix
: scheme for POSIX platforms like Linux or macOS. This is the default scheme used when Python or a component is installed.
-
posix_home
: scheme for POSIX platforms, when the
home
option is used. This scheme defines paths located under a specific home prefix.
-
posix_user
: scheme for POSIX platforms, when the
user
option is used. This scheme defines paths located under the user’s home directory (
site.USER_BASE
).
-
posix_venv
: scheme for
Python virtual environments
on POSIX platforms; by default it is the same as
posix_prefix
.
-
nt
: scheme for Windows. This is the default scheme used when Python or a component is installed.
-
nt_user
: scheme for Windows, when the
user
option is used.
-
nt_venv
: scheme for
Python virtual environments
on Windows; by default it is the same as
nt
.
-
venv
: a scheme with values from either
posix_venv
or
nt_venv
depending on the platform Python runs on.
-
osx_framework_user
: scheme for macOS, when the
user
option is used.
Each scheme is itself composed of a series of paths and each path has a unique identifier. Python currently uses eight paths:
-
stdlib
: directory containing the standard Python library files that are not platform-specific.
-
platstdlib
: directory containing the standard Python library files that are platform-specific.
-
platlib
: directory for site-specific, platform-specific files.
-
purelib
: directory for site-specific, non-platform-specific files (‘pure’ Python).
-
包括
: directory for non-platform-specific header files for the Python C-API.
-
platinclude
: directory for platform-specific header files for the Python C-API.
-
脚本
：脚本文件的目录。
-
data
：数据文件的目录。
User scheme
¶
This scheme is designed to be the most convenient solution for users that don’t have write permission to the global site-packages directory or don’t want to install into it.
Files will be installed into subdirectories of
site.USER_BASE
(written as
userbase
hereafter). This scheme installs pure Python modules and extension modules in the same location (also known as
site.USER_SITE
).
posix_user
¶
|
路径
|
安装目录
|
|
stdlib
|
userbase/lib/pythonX.Y
|
|
platstdlib
|
userbase/lib/pythonX.Y
|
|
platlib
|
userbase/lib/pythonX.Y/site-packages
|
|
purelib
|
userbase/lib/pythonX.Y/site-packages
|
|
包括
|
userbase/include/pythonX.Y
|
|
脚本
|
userbase/bin
|
|
data
|
userbase
|
nt_user
¶
|
路径
|
安装目录
|
|
stdlib
|
userbase\PythonXY
|
|
platstdlib
|
userbase\PythonXY
|
|
platlib
|
userbase\PythonXY\site-packages
|
|
purelib
|
userbase\PythonXY\site-packages
|
|
包括
|
userbase\PythonXY\Include
|
|
脚本
|
userbase\PythonXY\Scripts
|
|
data
|
userbase
|
osx_framework_user
¶
|
路径
|
安装目录
|
|
stdlib
|
userbase/lib/python
|
|
platstdlib
|
userbase/lib/python
|
|
platlib
|
userbase/lib/python/site-packages
|
|
purelib
|
userbase/lib/python/site-packages
|
|
包括
|
userbase/include/pythonX.Y
|
|
脚本
|
userbase/bin
|
|
data
|
userbase
|
Home scheme
¶
The idea behind the “home scheme” is that you build and maintain a personal stash of Python modules. This scheme’s name is derived from the idea of a “home” directory on Unix, since it’s not unusual for a Unix user to make their home directory have a layout similar to
/usr/
or
/usr/local/
. This scheme can be used by anyone, regardless of the operating system they are installing for.
posix_home
¶
|
路径
|
安装目录
|
|
stdlib
|
home/lib/python
|
|
platstdlib
|
home/lib/python
|
|
platlib
|
home/lib/python
|
|
purelib
|
home/lib/python
|
|
包括
|
home/include/python
|
|
platinclude
|
home/include/python
|
|
脚本
|
home/bin
|
|
data
|
home
|
Prefix scheme
¶
The “prefix scheme” is useful when you wish to use one Python installation to perform the build/install (i.e., to run the setup script), but install modules into the third-party module directory of a different Python installation (or something that looks like a different Python installation). If this sounds a trifle unusual, it is—that’s why the user and home schemes come before. However, there are at least two known cases where the prefix scheme will be useful.
First, consider that many Linux distributions put Python in
/usr
, rather than the more traditional
/usr/local
. This is entirely appropriate, since in those cases Python is part of “the system” rather than a local add-on. However, if you are installing Python modules from source, you probably want them to go in
/usr/local/lib/python2.X
而不是
/usr/lib/python2.X
.
Another possibility is a network filesystem where the name used to write to a remote directory is different from the name used to read it: for example, the Python interpreter accessed as
/usr/local/bin/python
might search for modules in
/usr/local/lib/python2.X
, but those modules would have to be installed to, say,
/mnt/@server/export/lib/python2.X
.
posix_prefix
¶
|
路径
|
安装目录
|
|
stdlib
|
prefix/lib/pythonX.Y
|
|
platstdlib
|
prefix/lib/pythonX.Y
|
|
platlib
|
prefix/lib/pythonX.Y/site-packages
|
|
purelib
|
prefix/lib/pythonX.Y/site-packages
|
|
包括
|
prefix/include/pythonX.Y
|
|
platinclude
|
prefix/include/pythonX.Y
|
|
脚本
|
prefix/bin
|
|
data
|
prefix
|
nt
¶
|
路径
|
安装目录
|
|
stdlib
|
prefix\Lib
|
|
platstdlib
|
prefix\Lib
|
|
platlib
|
prefix\Lib\site-packages
|
|
purelib
|
prefix\Lib\site-packages
|
|
包括
|
prefix\Include
|
|
platinclude
|
prefix\Include
|
|
脚本
|
prefix\Scripts
|
|
data
|
prefix
|
Installation path functions
¶
sysconfig
provides some functions to determine these installation paths.
-
sysconfig.
get_scheme_names
(
)
¶
-
Return a tuple containing all schemes currently supported in
sysconfig
.
-
sysconfig.
get_default_scheme
(
)
¶
-
Return the default scheme name for the current platform.
Added in version 3.10:
This function was previously named
_get_default_scheme()
and considered an implementation detail.
3.11 版改变：
When Python runs from a virtual environment, the
venv
scheme is returned.
