we've been recently approached by a colleague from Red Hat working on
According to their testing, Fedora Python performance could be improved by ~15%
by building /usr/bin/python* statically with libpython*.a. That sounds like a
worthy thing to do.
Since Python 3.8 Python extension modules are no longer linked to libpython.so
and we can do the following:
* build /usr/bin/python3(.8) statically with libpython*.a
* build and ship libpython3.8.so.1.0 for packages that "embed" Python
The change in the python3 package is trivial:
However it can have serious impact on Python extension modules that are linked
to libpython3.8.so.1.0 by various "nonstandard" build mechanisms or by compiling
code for Python extension module and code that embeds Python into one file.
We will likely propose a Fedora 32 Change for this, however I'm opening this
topic for discussion before we do so.
Testing the proposed Pull Request with your code is also helpful. Let me know
how can we make that easier (e.g. if you want a Copr or a Fedora 30/31 python38
package with this change).
We are retiring python2 and introducing python27 later this week. Rawhide only.
As for now, nothing should break, except python2-debug will exist no more.
Packages (build)requiring python2 or python2-devel should continue to work for
now. If not, let us know.
If you plan to keep a Python 2 package in Fedora 32+, talk to me, I can help you
draft an exception request.
Will post a reply here once it is done.
The following packages build subpackages for python2-debug (and should stop
doing it in Fedora 32+):
- gcc-python-plugin (FTBFS)
- python-mysql (PR exists)
- python-psycopg2 (notified in an existing bugzilla)
Python 3.8.0b4 is ready in rawhide (as python3).
The python38 package was updated in F31, F30 and F29:
Please test your code with Python 3.8.0b4 extensively and report issues.
-------- Forwarded Message --------
Subject: [Python-Dev] [RELEASE] ACTION REQUIRED: Python 3.8.0b4 now available
Date: Fri, 30 Aug 2019 11:09:37 +0200
From: Łukasz Langa <lukasz(a)langa.pl>
To: Python Committers <python-committers(a)python.org>, Python-Dev
<python-dev(a)python.org>, python-list(a)python.org, python-announce(a)python.org
It's time for the *last beta release* of Python 3.8. Go find it at:
This release is the *last* of four planned beta release previews. Beta release
previews are intended to give the wider community the opportunity to test new
features and bug fixes and to prepare their projects to support the new feature
release. The next pre-release of Python 3.8 will be 3.8.0c1, the first release
candidate, currently scheduled for 2019-09-30.
*Call to action*
We strongly encourage maintainers of third-party Python projects to test with
3.8 during the beta phase and report issues found to the Python bug
tracker as soon as possible. Please note this is the last beta release, there
is not much time left to identify and fix issues before the release of 3.8.0. If
you were hesitating trying it out before, now is the time.
While the release is planned to be feature complete entering the beta phase, it
is possible that features may be modified or, in rare cases, deleted up until
the start of the release candidate phase (2019-09-30). Our goal is have no ABI
changes after beta 3 and no code changes after 3.8.0c1, the release candidate.
*To achieve that, it will be extremely important to get as much exposure for 3.8
as possible during the beta phase. That beta phase is coming to an end. Please
Please keep in mind that this is a preview release and its use
is not recommended for production environments.
Many developers worked hard for the past four weeks to squash remaining bugs,
some requiring non-obvious decisions. Many thanks to the most active, namely
Raymond Hettinger, Steve Dower, Victor Stinner, Terry Jan Reedy, Serhiy
Storchaka, Pablo Galindo Salgado, Tal Einat, Zackery Spytz, Ronald Oussoren,
Neil Schemenauer, Inada Naoki, Christian Heimes, and Andrew Svetlov.
3.8.0 would not reach the Last Beta without you. Thank you!