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 gavan, ned.deily, ronaldoussoren
Date 2013-06-03.09:50:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1370253051.47.0.664713590182.issue18117@psf.upfronthosting.co.za>
In-reply-to
Content
Linking with "-framework Python" is always a bad idea because you have no control over which version of Python you link with other than by changing global system state (the Current link). Also: include files aren't included using the framework conventions (e.g. we use "#include <Python.h>", not "#include <Python/Python.h>").

I'd prefer to remove the Current link from "from source" installs instead adding them to the py3k installer, that makes is clearer that you are not supposed to use "-framework Python".

I'm also not too keen on renaming the Python framework for Python 3.4.
History
Date User Action Args
2013-06-03 09:50:51ronaldoussorensetrecipients: + ronaldoussoren, ned.deily, gavan
2013-06-03 09:50:51ronaldoussorensetmessageid: <1370253051.47.0.664713590182.issue18117@psf.upfronthosting.co.za>
2013-06-03 09:50:51ronaldoussorenlinkissue18117 messages
2013-06-03 09:50:51ronaldoussorencreate