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.

Author nascheme
Recipients doko, nas, nascheme, rpetrov
Date 2009-02-12.18:29:28
SpamBayes Score 3.98203e-08
Marked as misclassified No
Message-id <20090212182926.GD3683@arctrix.com>
In-reply-to <1234445556.88.0.573185737896.issue4151@psf.upfronthosting.co.za>
Content
On Thu, Feb 12, 2009 at 01:32:37PM +0000, Matthias Klose wrote:
> still seen on the 2.6 branch. applying r69374 on the branch doesn't fix
> it there.

The fix is spread over a number of commits: r69374, r69322, r69315,
r69305, r69304, r69303, r69302.  It could be backported but changing
the build system is always fraught with portability traps and that's
why it ends up turning to crud over time.

Obviously most core Python developers don't build in a separate
directory otherwise this feature won't have been broken for so long.
History
Date User Action Args
2009-02-12 18:29:31naschemesetrecipients: + nascheme, doko, nas, rpetrov
2009-02-12 18:29:29naschemelinkissue4151 messages
2009-02-12 18:29:29naschemecreate