This whole issue (the side-by-side install of Stackless and "normal"
Python)
is more complicated than it seems (unless I really want a 150MB copy of
something that is 99% the same and then remember which one is which, and
which packages are installed where) -- and since Stackless is meant
as a (mostly) fully compatible drop-in for "normal" Python IMHO the
"right" thing to do is replace (or originate) the /Library/Framework
python
install. Note that on the Mac if you even *have* a /Library/Framework
install, then you've already installed a non-factory Python distribution
(the stock OS-X one is in /System/Library/...) so the ramifications
are less than if we were replacing the version that shipped with the OS.
I suppose it might be a good idea to provide an alternative installer
that does a side-by-side install... maybe the first person who needs
it can contribute to the cause... :-)
On Oct 14, 2009, at 9:52 PM, Richard Tew wrote:
On Wed, Oct 7, 2009 at 8:56 AM, Carlos Eduardo de Paula
<[email protected]> wrote:
We might have to change the files inside Mac/BuildScript/scripts as
well
because they have references to Python.framework.
Will take a look at it later.
Okay, so no-one is asking for it, but it'd be nice for it to be there
in case anyone wanted it :-)
Anyone?
Cheers,
Richard.
_______________________________________________
Stackless mailing list
[email protected]
http://www.stackless.com/mailman/listinfo/stackless
_______________________________________________
Stackless mailing list
[email protected]
http://www.stackless.com/mailman/listinfo/stackless
