Skip to content

gh-93939: Build C extensions without setup.py #94474

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
miss-islington merged 4 commits into from
Jul 14, 2022
Merged

gh-93939: Build C extensions without setup.py #94474

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
7b40b31
gh-93939: Build C extensions without setup.py
tiran Jun 17, 2022
9e8fb83
old is the new new
tiran Jul 12, 2022
7858569
Fix multissltests, use sharedmods target
tiran Jul 13, 2022
45e1ba0
Add whatsnew entry
tiran Jul 13, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Add whatsnew entry
  • Loading branch information
@tiran
tiran committed Jul 13, 2022
commit 45e1ba0de26e3319fc1cb441c5ac008daf1ff71d
6 changes: 6 additions & 0 deletions Doc/whatsnew/3.12.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -353,6 +353,12 @@ Changes in the Python API
Build Changes
=============

* Python no longer uses ``setup.py`` to build shared C extension modules.
Build parameters like headers and libraries are detected in ``configure``
script. Extensions are built by ``Makefile``. Most extensions use
``pkg-config`` and fall back to manual detection.
(Contributed by Christian Heimes in :gh:`93939`.)

* ``va_start()`` with two parameters, like ``va_start(args, format),``
is now required to build Python.
``va_start()`` is no longer called with a single parameter.
Expand Down