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 ronaldoussoren
Recipients brett.cannon, eric.araujo, ned.deily, ronaldoussoren, tarek
Date 2013-06-07.15:01:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <ADE4B9DF-4DB4-4B66-9DD7-561BFBFA8EE9@mac.com>
In-reply-to <1370616849.11.0.310709338221.issue18136@psf.upfronthosting.co.za>
Content
On 7 Jun, 2013, at 16:54, Brett Cannon <report@bugs.python.org> wrote:

> 
> If that's true, does this simply mean I need to build Python without any installed libraries to avoid this conflict?

That's correct. There are other bugreports about other python installations influencing the build, although I'd have to search for the bug number.  

IMHO the root cause for this is that the source/build directories for Python's build are inserted at the wrong location in the compiler search path. Fixing that should be fairly easy, but does require search through the makefile and configure script, which is why I haven't actually tried to fix this yet.

> Or does this go away if I don't have Homebrew in a non-standard location?

Doesn't homebrew use /usr/local as the default location? That would be worse, as there is no easy way to tell the compiler to exclude /usr/local from its default search path.
History
Date User Action Args
2013-06-07 15:01:01ronaldoussorensetrecipients: + ronaldoussoren, brett.cannon, tarek, ned.deily, eric.araujo
2013-06-07 15:01:01ronaldoussorenlinkissue18136 messages
2013-06-07 15:01:01ronaldoussorencreate