On 3/4/19 2:29 AM, Joni Orponen wrote:
> On Sat, Mar 2, 2019 at 7:08 AM Larry Hastings <larry(a)hastings.org
> <mailto:email@example.com>> wrote:
> This bug in bpo-33329:
> This is also potentially affecting PGO builds of 2.7 on Debian Buster
> with GCC. Somehow building with Clang is fine.
> Does the configure time choice of compiler make a difference here for
> 3.4 and 3.5?
I don't know. I only build with the default compiler on my machine,
gcc. (My machine is Linux, 64-bit.) It'd be swell if you tried the RCs
A reminder: it is time for the next quarterly maintenance release of Python 3.7. The cutoff for 3.7.3rc1 is scheduled for Monday 2019-03-11 by the end of the day AOE. Please review open issues and ensure that any that you believe need to be addressed in 3.7.3 are either resolved or marked as a release blocker. And any assistance you can provide in helping resolve issues will be greatly appreciated! Following the rc1 cutoff, changes merged to the 3.7 branch will be released in 3.7.4 three months from now unless you mark the issue as a release blocker prior to 3.7.3 final, planned for 2019-03-25, and explain why the change should be cherry-picked into the final release.
nad(a)python.org -- 
On behalf of the Python development community, I'm chuffed to announce
the availability of Python 3.4.10rc1 and Python 3.5.7rc1.
Both Python 3.4 and 3.5 are in "security fixes only" mode. Both
versions only accept security fixes, not conventional bug fixes, and
both releases are source-only.
The "final" releases on both these branches should be out in about two
weeks. Of particular note: that release of Python 3.4, Python 3.4.10
final, will be the final release ever in the Python 3.4 series. After
3.4.10, the branch will be closed for good and I'll retire as Python 3.4
Release Manager. I'll still be the Python 3.5 Release Manager until 3.5
similarly concludes, approximately eighteen months from now.
You can find Python 3.4.10rc1 here:
And you can find Python 3.5.7rc1 here:
This bug in bpo-33329:
was fixed for 3.6+, but it also affects 3.4 and 3.5. The bug is that
with newer versions of glibc--which I'm pretty sure has shipped on all
major Linux distros by now--the test suite may send signals that are
invalid somehow. As a result the test suite... blocks forever? I
think? Anyway the observed resulting behavior is that there are three
regression tests in each branch that seemingly never complete. I
started the 3.4 regression test suite /nine hours ago/ and it still
claims to be running--and the 3.5 test suite isn't far behind.
Technically, no, it's not a security bug. But I simply can't ship 3.4
and 3.5 in this sorry state.
Obviously it'd be best if the folks involved with the original PRs
(Antoine?) took over. I'm sending this to a wider audience just because
I'd hoped to tag the next RCs for 3.4 and 3.5 this weekend, and the
original participants in this fix may not be available, and I'm hoping I
won't have to slip the schedule.
Thanks for your time,