This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: 3.2: build --without-threads fails
Type: compile error Stage: resolved
Components: Build Versions: Python 3.2
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: georg.brandl, python-dev, skrah, vstinner
Priority: release blocker Keywords: buildbot

Created on 2011-05-16 17:56 by skrah, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (10)
msg136114 - (view) Author: Stefan Krah (skrah) * (Python committer) Date: 2011-05-16 17:56
The new Fedora buildbot (--without-threads) fails to compile:

http://www.python.org/dev/buildbot/all/builders/AMD64%20Fedora%20without%20threads%203.2/builds/1


I didn't check the release branch yet.
msg136116 - (view) Author: Stefan Krah (skrah) * (Python committer) Date: 2011-05-16 18:27
A backport of 79fcd71d0356 fixes the problem.
msg136424 - (view) Author: Stefan Krah (skrah) * (Python committer) Date: 2011-05-21 09:28
Georg, I think this might be a release blocker. I hope it is
not too late for 3.2.1.


Victor, was there any reason that 79fcd71d0356 wasn't backported?
Otherwise I'll go ahead and push it to 3.2.
msg136450 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2011-05-21 15:28
No, it's not too late -- rc2 is shifted to next weekend.
msg136917 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2011-05-25 22:40
New changeset bb8bb4db2bc5 by Stefan Krah in branch '3.2':
Issue #12090: backport 79fcd71d0356
http://hg.python.org/cpython/rev/bb8bb4db2bc5
msg138570 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2011-06-18 07:52
Is this done then?
msg138574 - (view) Author: Stefan Krah (skrah) * (Python committer) Date: 2011-06-18 08:55
Yes, this is fixed in 3.2. I just left the issue open as a reminder
for the release branch.
msg138703 - (view) Author: STINNER Victor (vstinner) * (Python committer) Date: 2011-06-20 12:14
> Yes, this is fixed in 3.2.
> I just left the issue open as a reminder for the release branch.

The issue is still open, can it be closed? What do you mean by "release branch"?
msg138704 - (view) Author: Stefan Krah (skrah) * (Python committer) Date: 2011-06-20 12:25
STINNER Victor <report@bugs.python.org> wrote:
> > Yes, this is fixed in 3.2.
> > I just left the issue open as a reminder for the release branch.
> 
> The issue is still open, can it be closed? What do you mean by "release branch"?

This one: http://hg.python.org/releasing/3.2.1/

The issue isn't fixed there yet.
msg138729 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2011-06-20 15:18
It doesn't need to; this branch is inactive at the moment.
History
Date User Action Args
2022-04-11 14:57:17adminsetgithub: 56299
2011-06-20 15:18:49georg.brandlsetstatus: open -> closed

messages: + msg138729
2011-06-20 12:25:59skrahsetmessages: + msg138704
2011-06-20 12:14:03vstinnersetmessages: + msg138703
2011-06-18 08:55:07skrahsetresolution: fixed
messages: + msg138574
stage: resolved
2011-06-18 07:52:55georg.brandlsetmessages: + msg138570
2011-05-25 22:40:20python-devsetnosy: + python-dev
messages: + msg136917
2011-05-21 15:28:11georg.brandlsetmessages: + msg136450
2011-05-21 09:28:42skrahsetpriority: normal -> release blocker

messages: + msg136424
2011-05-18 16:58:51Arfreversetnosy: + vstinner
2011-05-16 18:27:18skrahsetmessages: + msg136116
2011-05-16 17:56:50skrahcreate