Does virtualenv work on Mac nowadays? It might be another approach. It works great for keeping different installations on the same machine separate. Not sure how it would work with framework builds though.
On Thu, Aug 25, 2011 at 7:18 AM, Vinay Sajip <vinay_sa...@yahoo.co.uk>wrote: > Ronald Oussoren <ronaldoussoren <at> mac.com> writes: > > > And one final workaround: the configure script has an option named > '--with-framework-name=NAME'. This > > will install the framework as NAME.framework instead of Python.framework. > I > use this to install > > multiple build variants of Python, and to keep my regular > Python.framework > separate from development builds. > > This sounds like a good approach to try. > > Thanks, > > Vinay Sajip > > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG@python.org > http://mail.python.org/mailman/listinfo/pythonmac-sig > unsubscribe: http://mail.python.org/mailman/options/Pythonmac-SIG >
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig unsubscribe: http://mail.python.org/mailman/options/Pythonmac-SIG
