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 paul.moore
Recipients brian.curtin, cgohlke, christian.heimes, loewis, paul.moore, ralf.gommers, silverbacknet, theller, tim.golden, trent
Date 2014-02-04.14:01:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1391522515.41.0.824590067587.issue16296@psf.upfronthosting.co.za>
In-reply-to
Content
Maybe it's not applicable to 3.3 somehow, which is what I tried. I applied the patch to the distutils in the system installed Python, then ran pip install numpy from a virtualenv.

It's quite possible that a million things could have gone wrong in that process - but that's all I had time to check (I'm only really interested in this as a courtesy to the numpy people, who asked me to raise the bug on numpy, then directed me to this patch as a fix).
History
Date User Action Args
2014-02-04 14:01:55paul.mooresetrecipients: + paul.moore, loewis, theller, christian.heimes, tim.golden, trent, brian.curtin, cgohlke, silverbacknet, ralf.gommers
2014-02-04 14:01:55paul.mooresetmessageid: <1391522515.41.0.824590067587.issue16296@psf.upfronthosting.co.za>
2014-02-04 14:01:55paul.moorelinkissue16296 messages
2014-02-04 14:01:55paul.moorecreate