Skip to content

Commit

Permalink
[3.12] GH-92584: Remove references to Distutils in configure.rst (GH-…
Browse files Browse the repository at this point in the history
…108043) (#108063)

GH-92584: Remove references to Distutils in configure.rst (GH-108043)

Remove references to Distutils in configure.rst
(cherry picked from commit e88eb37)

Co-authored-by: Adam Turner <[email protected]>
  • Loading branch information
miss-islington and AA-Turner authored Aug 16, 2023
1 parent 2cbb452 commit 931df0a
Showing 1 changed file with 6 additions and 11 deletions.
17 changes: 6 additions & 11 deletions Doc/using/configure.rst
Original file line number Diff line number Diff line change
Expand Up @@ -686,7 +686,6 @@ Main files of the build system
* :file:`pyconfig.h` (created by :file:`configure`);
* :file:`Modules/Setup`: C extensions built by the Makefile using
:file:`Module/makesetup` shell script;
* :file:`setup.py`: C extensions built using the ``setuptools`` package.

Main build steps
----------------
Expand All @@ -695,8 +694,7 @@ Main build steps
* A static ``libpython`` library (``.a``) is created from objects files.
* ``python.o`` and the static ``libpython`` library are linked into the
final ``python`` program.
* C extensions are built by the Makefile (see :file:`Modules/Setup`)
and ``python setup.py build``.
* C extensions are built by the Makefile (see :file:`Modules/Setup`).

Main Makefile targets
---------------------
Expand Down Expand Up @@ -748,9 +746,6 @@ Example on Linux x86-64::
At the beginning of the files, C extensions are built as built-in modules.
Extensions defined after the ``*shared*`` marker are built as dynamic libraries.

The :file:`setup.py` script only builds C extensions as shared libraries using
the :mod:`distutils` module.

The :c:macro:`PyAPI_FUNC()`, :c:macro:`PyAPI_API()` and
:c:macro:`PyMODINIT_FUNC()` macros of :file:`Include/pyport.h` are defined
differently depending if the ``Py_BUILD_CORE_MODULE`` macro is defined:
Expand Down Expand Up @@ -784,7 +779,7 @@ Preprocessor flags
headers in a nonstandard directory ``<include dir>``.

Both :envvar:`CPPFLAGS` and :envvar:`LDFLAGS` need to contain the shell's
value for setup.py to be able to build extension modules using the
value to be able to build extension modules using the
directories specified in the environment variables.

.. envvar:: BASECPPFLAGS
Expand Down Expand Up @@ -821,8 +816,8 @@ Compiler flags
.. envvar:: CFLAGS_NODIST

:envvar:`CFLAGS_NODIST` is used for building the interpreter and stdlib C
extensions. Use it when a compiler flag should *not* be part of the
distutils :envvar:`CFLAGS` once Python is installed (:issue:`21121`).
extensions. Use it when a compiler flag should *not* be part of
:envvar:`CFLAGS` once Python is installed (:gh:`65320`).

In particular, :envvar:`CFLAGS` should not contain:

Expand Down Expand Up @@ -952,7 +947,7 @@ Linker flags

:envvar:`LDFLAGS_NODIST` is used in the same manner as
:envvar:`CFLAGS_NODIST`. Use it when a linker flag should *not* be part of
the distutils :envvar:`LDFLAGS` once Python is installed (:issue:`35257`).
:envvar:`LDFLAGS` once Python is installed (:gh:`65320`).

In particular, :envvar:`LDFLAGS` should not contain:

Expand All @@ -974,7 +969,7 @@ Linker flags
directory ``<lib dir>``.

Both :envvar:`CPPFLAGS` and :envvar:`LDFLAGS` need to contain the shell's
value for setup.py to be able to build extension modules using the
value to be able to build extension modules using the
directories specified in the environment variables.

.. envvar:: LIBS
Expand Down

0 comments on commit 931df0a

Please sign in to comment.