➜

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 eric.araujo
Recipients Bruce.Sherwood, eric.araujo, r.david.murray, ronaldoussoren
Date 2010-11-02.23:20:52
SpamBayes Score 0.0008820974
Marked as misclassified No
Message-id <1288740053.45.0.904084260083.issue10215@psf.upfronthosting.co.za>
In-reply-to
Content 
So your answer is actually *no*, it does not install into Python3.framework :)

If there had been separate Python.framework and Python3.framework, the answer to this bug would be obvious.  But since 2.x and 3.x Pythons are installed as versions of the same framework, it sort of makes sense that Versions/Current can point to a 3.x version.

Do I make sense?
History
Date User Action Args
2010-11-02 23:20:53eric.araujosetrecipients: + eric.araujo, ronaldoussoren, r.david.murray, Bruce.Sherwood
2010-11-02 23:20:53eric.araujosetmessageid: <1288740053.45.0.904084260083.issue10215@psf.upfronthosting.co.za>
2010-11-02 23:20:52eric.araujolinkissue10215 messages
2010-11-02 23:20:52eric.araujocreate