Mirror
/
cpython
mirror of https://github.com/python/cpython
4
1
Fork 0
Code Issues Releases Wiki Activity

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

Remove references to Distutils in configure.rst
This commit is contained in:
Adam Turner 2023-08-16 22:13:05 +01:00 committed by GitHub
parent fbb7cbc0e9
commit e88eb3775e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
Doc/using/configure.rst
View File

@ -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
----------------
@ -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
---------------------
@ -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:
@ -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
@ -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:
@ -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:
@ -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