> I dunno about the bug, but simple_json is not what you should be
> installing... The package name is simplejson.
Thanks for pointing out the typo. I updated my bug report.
However, this doesn't resolve the problem. In fact I ran into the
problem originally using zc.buildout, building PIL and py
I dunno about the bug, but simple_json is not what you should be
installing... The package name is simplejson.
-bob
On Sun, Oct 19, 2008 at 4:42 PM, Amos Latteier <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I just got a new aluminum macbook. It's great expect that it seems to
> ship with a broken easy_i
Hi,
I just got a new aluminum macbook. It's great expect that it seems to
ship with a broken easy_install. I tracked down the problem and
submitted a bug to apple (bug #6302565). I'm sending the details
to this mailing list in hopes that it can help others, or perhaps others
can point out a better
Idan Gazit wrote:
If I want macpython / 2.6 to be the default python interpreter -- what
is the best route? I can think of the two following ways:
1. Change $PATH so that /usr/local/bin precedes /usr/bin
2. Symlink /usr/bin/python to /usr/local/bin/python or to
/Library/Frameworks/Python.fram
Idan Gazit wrote:
On Oct 19, 2008, at 8:12 PM, Kevin Walzer wrote:
Not sure if 2.6 does the same, but I thought it did. It certainly
doesn't touch /etc/paths.d, nor should it. ~/.MacOSX/environment.plist
isn't affected either as far as I know.
A little bit of rooting around inside the insta
On Oct 19, 2008, at 8:12 PM, Kevin Walzer wrote:
Not sure if 2.6 does the same, but I thought it did. It certainly
doesn't touch /etc/paths.d, nor should it. ~/.MacOSX/
environment.plist isn't affected either as far as I know.
A little bit of rooting around inside the installer packages /
On Oct 19, 2008, at 8:12 PM, Kevin Walzer wrote:
What does "echo $PATH" show in Terminal? In my case it shows
something like this:
/Library/Frameworks/Python.framework/Versions/Current/bin:/sw/bin:/
sw/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/
usr/local/bin:/
Nop
Idan Gazit wrote:
On Oct 19, 2008, at 7:48 PM, Kevin Walzer wrote:
The installer will modify your path settings so that MacPython comes
up before the version shipped by Apple. However, the current Mac build
of Python 2.5 is broken if you need to run Tkinter apps such as IDLE:
Hm,
Dunno why,
On Oct 19, 2008, at 7:48 PM, Kevin Walzer wrote:
The installer will modify your path settings so that MacPython comes
up before the version shipped by Apple. However, the current Mac
build of Python 2.5 is broken if you need to run Tkinter apps such
as IDLE:
Hm,
Dunno why, but it certain
On Sun, Oct 19, 2008 at 10:48 AM, Kevin Walzer <[EMAIL PROTECTED]> wrote:
> Idan Gazit wrote:
>>
>> Hi Folks,
>>
>> Now that 2.6 is released, I wanted to install it on my local machine. What
>> I'm having trouble wrapping my head around is how to make sure that
>> macpython 2.6 doesn't break anythi
Idan Gazit wrote:
Hi Folks,
Now that 2.6 is released, I wanted to install it on my local machine.
What I'm having trouble wrapping my head around is how to make sure that
macpython 2.6 doesn't break anything involving leopard python.
If I want macpython / 2.6 to be the default python interpr
Hi Folks,
Now that 2.6 is released, I wanted to install it on my local machine.
What I'm having trouble wrapping my head around is how to make sure
that macpython 2.6 doesn't break anything involving leopard python.
If I want macpython / 2.6 to be the default python interpreter -- what
is
12 matches
Mail list logo
