On Wed, Mar 9, 2011 at 10:50 AM, Casey Duncan <[email protected]> wrote:
> On Tue, Mar 8, 2011 at 4:35 PM, Tristam MacDonald <[email protected]>
> wrote:
>> On Tue, Mar 8, 2011 at 6:25 PM, Richard Jones <[email protected]>
>> wrote:
>>>
>>> Actually I've found that's a little dangerous. Depending on how it's
>>> done (and there's three methods that spring immediately to mind:
>>> source, python.org binary and ActiveState binary) it'll most likely
>>> confusticate your "default" python installation, potentially breaking
>>> other things.
>>
>> Yeah, this is one of the reasons I am loath to install a custom python. It
>> has broken a lot of things at various times in the past.
>
> I'm not sure how anyone that uses python seriously on Mac doesn't
> install a custom one, and many of them at that. Maybe I'm lucky, but
> I've installed a ton of Pythons on Mac OS 10.3-10.6 from source, to
> binaries to MacPorts framework builds (which never really worked for
> me), and never confused things that use the system Python. Right now
> "python" defaults to 2.7, but I also have 2.5 through 3.1 installed
> with 3.2 coming soon.
>
> Just out of curiosity, what broke for you, and what do you think caused it?
I have several versions installed:
- as mentioned, I have ActiveState's 2.6 installed over the system
version (the only way to install it AFAIK) to make it possible to use
PIL and pyglet
- I have manually-compiled 2.4, 2.5, 3.1 and 3.2 and those live in
/usr/local/ and tend to not affect anything
The ActiveState install fixed stuff that was broken for me, but I find
that random little things (like the inability to use the pyglet cocoa
branch :-) do still pop up every now and then.
I also have a bunch of virtualenvs that messed things up initially too
because I was a virtualenv noob and forgot to say --no-site-packages.
Richard
--
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pyglet-users?hl=en.
