.. data:: base_exec_prefix
- Equivalent to :data:`exec_prefix`, but refering to the base Python installation.
+ Equivalent to :data:`exec_prefix`, but referring to the base Python installation.
When running under :ref:`sys-path-init-virtual-environments`,
:data:`exec_prefix` gets overwritten to the virtual environment prefix.
.. data:: base_prefix
- Equivalent to :data:`prefix`, but refering to the base Python installation.
+ Equivalent to :data:`prefix`, but referring to the base Python installation.
When running under :ref:`virtual environment <venv-def>`,
:data:`prefix` gets overwritten to the virtual environment prefix.
.. note::
There are other ways how "virtual environments" could be implemented, this
- documentation referes implementations based on the ``pyvenv.cfg`` mechanism,
+ documentation refers implementations based on the ``pyvenv.cfg`` mechanism,
such as :mod:`venv`. Most virtual environment implementations follow the
model set by :mod:`venv`, but there may be exotic implementations that
diverge from it.
.. function:: linked_with_musl()
- Return ``False`` if there is no evidence the interperter was compiled with
+ Return ``False`` if there is no evidence the interpreter was compiled with
``musl``, otherwise return a version triple, either ``(0, 0, 0)`` if the
version is unknown, or the actual version if it is known. Intended for use
in ``skip`` decorators. ``emscripten`` and ``wasi`` are assumed to be