Subject: Re: [boost] boost.python problem in release branch (GSoc work)
From: Ralf W. Grosse-Kunstleve (rwgk_at_[hidden])
Date: 2009-11-12 19:49:42
For Beman (and the records):
This problem is now resolved, thanks to the thorough work of Troy Straszheim. Troy found out that the problem was due to a very long-standing bug exposed by recent changes in Python. It was just an unfortunate coincidence that the GSoC changes came at the same time.
----- Original Message ----
From: Ralf W. Grosse-Kunstleve <rwgk_at_[hidden]>
Sent: Fri, November 6, 2009 10:44:42 PM
Subject: [boost] boost.python problem in release branch (GSoc work)
I just found out that two boost.python tests (svn trunk and release) are not valgrind clean. I fear this could be a serious problem, although I've not seen actual failures apart from the valgrind diagnostics. What I know at the moment is:
produce valgrind errors with trunk revision 56305 but not 56304 (fedora 8 64-bit).
The critical revision 56305 is:
Merged 2009 GSoC work from sandbox-branches/bhy/py3k branch back into trunk.
It is merged into the release branch already.
Unfortunately, without revision 56305 boost.python does not work with Python 2.6.3 and 2.6.4, i.e. backing out rev. 56305 and some followup revisions would only replace one problem with another.
How far along is the 1.41 release? Is there a chance it could be delayed for a few days?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk