Ok, right
I thought ApplePython = MacPython
and got confused by this paragraph on the MacPython site, NOT python.org
"The downside of Apple including 2.3 is that running MacPython 2.3.3
on Mac OS X 10.3 is a bit of a problem: when you install the full
MacPython 2.3.3 distribution (the one labell
On Apr 15, 2006, at 16:03, Bob Ippolito wrote:
> It's possible that the wxPython guys screwed up, or it's possible
> that you downloaded an installer for Apple's Python 2.3 framework
> and expected it to work with an entirely different version of
> Python installed in another location. You
On Apr 15, 2006, at 5:57 PM, Bob Ippolito wrote:Installers for extensions are specific to a particular version ofPython anyway. But is that always necessary? I am sure it is sometimes, particularly when the OS changes dramatically like from 10.3 to 10.4.But what about the case of the Alias researc
On Apr 15, 2006, at 14:10, Troy Rollins wrote:The thing I'm slightly unclear about is the best way to change my path on OSX. Changing things like ~/.profile and ~/.bash_profile change it for the shell, but do not change it systemwide. I've modified my ~/.MacOSX.environment.plist, which seems
On Apr 15, 2006, at 5:57 PM, Bob Ippolito wrote:
> Is there any particular reason to change it in
> MacOSX.environment.plist? What applications do you use that aren't
> started from the shell, yet look in $PATH for Python? I've never
> seen one, but then again I don't use GUI text editors
On Apr 15, 2006, at 2:43 PM, Daniel Lord wrote:
> The recommended approach (and it used to be the default on install
> for MacPython--I beleive it may still be but is optional now) is to
> install MacPython in /usr/local/bin leaving Apple's Python 2.3
> intact. Then you put /usr/local/bin in your
I realised that on OS X it is almost impossible (or at least I can't
find a way) to capture F-key or meta-key presses using the python
curses module. The following email has some code which illustrates
the problem (it reports key-presses in 3 different ways). For some
reason I don't understand it
It is _not_ a good thing to remove Apple's Python. Don't panic though.
First, let's stop this from happening to anybody else...
Can you tell me where those instructions are that recommend that on
Python.org? I believe they refer to a previous _MacPython_ that was
installed which is not the sa
> Hi,
>
> I'm using 10.3.9
>
> removed Python 2.3 as per instructions on python.org
>
> installed Python 2.4
>
> and now can't launch some apps which reference 2.3
Please point me to the instructions on python.org which tell you to
remove Python 2.3 from your Mac, so that I can stamp them out!
> I could make some nasty remarks about emacs and you could then
> strike back with remarks about vi, but lets not go there :-)
Thanks for reminding me of vi.
As I understand it (I'm afraid I've never seen the point of knowing
much about vi :-) the model vi uses is quite different -- "lean and
me
Hi,
I'm using 10.3.9
removed Python 2.3 as per instructions on python.org
installed Python 2.4
and now can't launch some apps which reference 2.3
dyld: /Applications/Alias/MotionBuilder 7 PLE/MotionBuilder 7
PLE.app/Contents/MacOS/ple can't open library:
/System/Library/Frameworks/Python.frame
11 matches
Mail list logo
