location of libs... on Panther

Sigh...

My Mac OS X Panther installation of wxPython appears to be all screwed up
and I'm getting segmentation faults among other things. I thought I had
2.4.x working after upgrading to Panther last week, but now I'm not so sure,
I might be remembering some Jaguar tests. I tried renaming the 2.4 libs
before installing the 2.5.1.0p7 (apple) build and since then I haven't been
able to get 2.4 or 2.5 to run. Before I go any further, could someone list
the paths of Jaguar and Panther installations of wxPython so I can clean
everything out including symlinks and then try doing a clean install of 2.4
to make sure that is working before attempting 2.5 again.

Apple's Python 2.3 is working.

ka

Hmmm...

I think Robin made the same mistake I made when I first built the Package for Panther.

Apple's Panther lives in:
/System/Library/Frameworks/Python.Framework

But this is not where extension modules are supposed to go. (Since this is a system folder and Apple doesn't want people mucking inside of those.) site-packages is supposed to just be a symlink to /Library/Python/2.3, where the extension modules should go.

However, when I just checked site-packages inside of /System/Library/Frameworks/Python.Framework, it is no longer a symlink and contains only two extension modules: wx and wxPython. So that is very likely the cause of your problems here.

BTW, on Jaguar Python should be found at /Library/Frameworks/Python.Framework.

Kevin

···

On Jan 20, 2004, at 7:20 PM, Kevin Altis wrote:

Sigh...

My Mac OS X Panther installation of wxPython appears to be all screwed up
and I'm getting segmentation faults among other things. I thought I had
2.4.x working after upgrading to Panther last week, but now I'm not so sure,
I might be remembering some Jaguar tests. I tried renaming the 2.4 libs
before installing the 2.5.1.0p7 (apple) build and since then I haven't been
able to get 2.4 or 2.5 to run. Before I go any further, could someone list
the paths of Jaguar and Panther installations of wxPython so I can clean
everything out including symlinks and then try doing a clean install of 2.4
to make sure that is working before attempting 2.5 again.

Apple's Python 2.3 is working.

ka

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwindows.org

Thanks! There are a bunch of scripts /usr/bin, libs in /usr/local/lib and
probably other places as well. How much of this is leftover from Jaguar I
don't know. I guess what I would like to be able to do is have a script that
will completely delete any trace of previous wxPython installs completely.
Obviously part of what I'm worried about here is stepping the Apple
installed files. The files that have a wx in them are easy enough to spot,
but there are a lot of other scripts like helpviewer, pywrap... I'll start
with what is in /usr/local/bin and /usr/local/lib and delete files with the
same names in /usr/bin...

ka

···

-----Original Message-----
From: Kevin Ollivier [mailto:kevino@tulane.edu]
Sent: Tuesday, January 20, 2004 8:01 PM
To: wxPython-dev@lists.wxwindows.org
Subject: Re: [wxPython-dev] location of libs... on Panther

Hmmm...

I think Robin made the same mistake I made when I first built the
Package for Panther.

Apple's Panther lives in:
/System/Library/Frameworks/Python.Framework

But this is not where extension modules are supposed to go. (Since this
is a system folder and Apple doesn't want people mucking inside of
those.) site-packages is supposed to just be a symlink to
/Library/Python/2.3, where the extension modules should go.

However, when I just checked site-packages inside of
/System/Library/Frameworks/Python.Framework, it is no longer a symlink
and contains only two extension modules: wx and wxPython. So that is
very likely the cause of your problems here.

BTW, on Jaguar Python should be found at
/Library/Frameworks/Python.Framework.

Kevin

On Jan 20, 2004, at 7:20 PM, Kevin Altis wrote:

> Sigh...
>
> My Mac OS X Panther installation of wxPython appears to be all screwed
> up
> and I'm getting segmentation faults among other things. I thought I had
> 2.4.x working after upgrading to Panther last week, but now I'm not so
> sure,
> I might be remembering some Jaguar tests. I tried renaming the 2.4 libs
> before installing the 2.5.1.0p7 (apple) build and since then I haven't
> been
> able to get 2.4 or 2.5 to run. Before I go any further, could someone
> list
> the paths of Jaguar and Panther installations of wxPython so I can
> clean
> everything out including symlinks and then try doing a clean install
> of 2.4
> to make sure that is working before attempting 2.5 again.
>
> Apple's Python 2.3 is working.
>
> ka
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwindows.org
> For additional commands, e-mail: wxPython-dev-help@lists.wxwindows.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwindows.org

Hi Kevin,

Actually, if you see anything like python or pythonw in /usr/local/bin, go ahead and delete them - these are remaining from Jaguar Python. For wxPython stuff, in both cases it should simply write inside of /usr/local, so they should get overwritten whenever you update your wxPython install.

Kevin

···

On Jan 20, 2004, at 9:52 PM, Kevin Altis wrote:

Thanks! There are a bunch of scripts /usr/bin, libs in /usr/local/lib and
probably other places as well. How much of this is leftover from Jaguar I
don't know. I guess what I would like to be able to do is have a script that
will completely delete any trace of previous wxPython installs completely.
Obviously part of what I'm worried about here is stepping the Apple
installed files. The files that have a wx in them are easy enough to spot,
but there are a lot of other scripts like helpviewer, pywrap... I'll start
with what is in /usr/local/bin and /usr/local/lib and delete files with the
same names in /usr/bin...

ka

-----Original Message-----
From: Kevin Ollivier [mailto:kevino@tulane.edu]
Sent: Tuesday, January 20, 2004 8:01 PM
To: wxPython-dev@lists.wxwindows.org
Subject: Re: [wxPython-dev] location of libs... on Panther

Hmmm...

I think Robin made the same mistake I made when I first built the
Package for Panther.

Apple's Panther lives in:
/System/Library/Frameworks/Python.Framework

But this is not where extension modules are supposed to go. (Since this
is a system folder and Apple doesn't want people mucking inside of
those.) site-packages is supposed to just be a symlink to
/Library/Python/2.3, where the extension modules should go.

However, when I just checked site-packages inside of
/System/Library/Frameworks/Python.Framework, it is no longer a symlink
and contains only two extension modules: wx and wxPython. So that is
very likely the cause of your problems here.

BTW, on Jaguar Python should be found at
/Library/Frameworks/Python.Framework.

Kevin

On Jan 20, 2004, at 7:20 PM, Kevin Altis wrote:

Sigh...

My Mac OS X Panther installation of wxPython appears to be all screwed
up
and I'm getting segmentation faults among other things. I thought I had
2.4.x working after upgrading to Panther last week, but now I'm not so
sure,
I might be remembering some Jaguar tests. I tried renaming the 2.4 libs
before installing the 2.5.1.0p7 (apple) build and since then I haven't
been
able to get 2.4 or 2.5 to run. Before I go any further, could someone
list
the paths of Jaguar and Panther installations of wxPython so I can
clean
everything out including symlinks and then try doing a clean install
of 2.4
to make sure that is working before attempting 2.5 again.

Apple's Python 2.3 is working.

ka

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwindows.org

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwindows.org

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwindows.org

Kevin Ollivier wrote:

Hmmm...

I think Robin made the same mistake I made when I first built the Package for Panther.

Apple's Panther lives in: /System/Library/Frameworks/Python.Framework

But this is not where extension modules are supposed to go. (Since
this is a system folder and Apple doesn't want people mucking inside
of those.) site-packages is supposed to just be a symlink to /Library/Python/2.3, where the extension modules should go.

Grrr... I guess I need to pay more attention to the pythonmac-sig list. Is there a message there or some other doc that documents this that you
can point me to? Is there a distutils hack that helps facilitate
installing things in the right place?

I did examine site-pacakges (on my freshly installed from scratch
Panther) before installing for the first time and I'm fairly certain I
would have noticed that it was a symlink... Oh well.

However, when I just checked site-packages inside of /System/Library/Frameworks/Python.Framework, it is no longer a
symlink

Yep I've heard that the Installer program will do that, if it has a
directory in it's file list then it will blow away symlinks that are in
the way.

and contains only two extension modules: wx and wxPython. So that is very likely the cause of your problems here.

But it should be mentioned that putting the packages there does allow them to work okay. It's just not the "right" place, and if there were any other packages already installed in the right place then blowing away the symlink will cause you to not be able to access them since /library/Python/2.3 is not on the sys.path. (You'd think that if Apple wanted things done this way they would have installed a site.py that put that dir on the sys.path, and also patched distutils to install stuff there. <grumble> )

My Mac OS X Panther installation of wxPython appears to be all
screwed up and I'm getting segmentation faults among other things.
I thought I had 2.4.x working after upgrading to Panther last week,
but now I'm not so sure, I might be remembering some Jaguar tests.
I tried renaming the 2.4 libs before installing the 2.5.1.0p7
(apple) build and since then I haven't been able to get 2.4 or 2.5
to run. Before I go any further, could someone list the paths of
Jaguar and Panther installations of wxPython so I can clean everything out including symlinks and then try doing a clean
install of 2.4 to make sure that is working before attempting 2.5
again.

Jaguar wxPython 2.4:
* some scripts in /usr/local/bin
* wxMac libs in /usr/local/lib
* other wxMac stuff under /usr/local/share/wx
* Python packages in /Library/Frameworks/.../site-packages

Panther wxPython 2.4:
* same as above except /System/Library/Frameworks/.../site-packages
(Kevin O: is that where the installer you built will put them or did the
final one put them in /Library/Python/2.3 ?)

"Apple" wxPython 2.5 :
* scripts in /usr/bin
* wxMac libs, headers, share, etc in /usr/lib/wxPython-2.5.1.0p7
* Python packages in /Library/Frameworks/.../site-packages
* Don't forget to redo the symlink

Also, in /Library/Receipts is a copy of the Installer package that you used to install before, and is what the Installer uses to know if it is doing an upgrade or a fresh install. When I clean things up manually I also remove the old installers in that dir.

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Hi Robin,

Kevin Ollivier wrote:

Hmmm...
I think Robin made the same mistake I made when I first built the Package for Panther.
Apple's Panther lives in: /System/Library/Frameworks/Python.Framework
But this is not where extension modules are supposed to go. (Since
this is a system folder and Apple doesn't want people mucking inside
of those.) site-packages is supposed to just be a symlink to /Library/Python/2.3, where the extension modules should go.

Grrr... I guess I need to pay more attention to the pythonmac-sig list. Is there a message there or some other doc that documents this that you
can point me to? Is there a distutils hack that helps facilitate
installing things in the right place?

I did examine site-pacakges (on my freshly installed from scratch
Panther) before installing for the first time and I'm fairly certain I
would have noticed that it was a symlink... Oh well.

Here's a link to the discussion on PythonMac:

http://mail.python.org/pipermail/pythonmac-sig/2003-November/009412.html

Unfortunately, I haven't seen anything yet about a distutils hack for this.

However, when I just checked site-packages inside of /System/Library/Frameworks/Python.Framework, it is no longer a
symlink

Yep I've heard that the Installer program will do that, if it has a
directory in it's file list then it will blow away symlinks that are in
the way.

and contains only two extension modules: wx and wxPython. So that is very likely the cause of your problems here.

But it should be mentioned that putting the packages there does allow them to work okay. It's just not the "right" place, and if there were any other packages already installed in the right place then blowing away the symlink will cause you to not be able to access them since /library/Python/2.3 is not on the sys.path. (You'd think that if Apple wanted things done this way they would have installed a site.py that put that dir on the sys.path, and also patched distutils to install stuff there. <grumble> )

Yeah, it does seem they took the lazy way out, and this 'modification' isn't really documented anywhere. *Especially* since their installer whacks symlinks they should have thought twice about doing this!

My Mac OS X Panther installation of wxPython appears to be all
screwed up and I'm getting segmentation faults among other things.
I thought I had 2.4.x working after upgrading to Panther last week,
but now I'm not so sure, I might be remembering some Jaguar tests.
I tried renaming the 2.4 libs before installing the 2.5.1.0p7
(apple) build and since then I haven't been able to get 2.4 or 2.5
to run. Before I go any further, could someone list the paths of
Jaguar and Panther installations of wxPython so I can clean everything out including symlinks and then try doing a clean
install of 2.4 to make sure that is working before attempting 2.5
again.

Jaguar wxPython 2.4:
* some scripts in /usr/local/bin
* wxMac libs in /usr/local/lib
* other wxMac stuff under /usr/local/share/wx
* Python packages in /Library/Frameworks/.../site-packages

Panther wxPython 2.4:
* same as above except /System/Library/Frameworks/.../site-packages
(Kevin O: is that where the installer you built will put them or did the
final one put them in /Library/Python/2.3 ?)

The final one put them in /Library/Python/2.3.

Kevin

···

On Jan 20, 2004, at 10:34 PM, Robin Dunn wrote:

From: Robin Dunn

"Apple" wxPython 2.5 :
* scripts in /usr/bin
* wxMac libs, headers, share, etc in /usr/lib/wxPython-2.5.1.0p7
* Python packages in /Library/Frameworks/.../site-packages
* Don't forget to redo the symlink

Most of my Unix braincells are dead (same as the ones for Calculus) so
remind me again the actual commands to redo the symlink with correct
permission flags, not destroying subdirs, or whatever else is relevant.
Anything else that needs to be done to return to a "virgin" Panther state
should also be mentioned.

BTW, I learned today that you can jump to any normally invisible dir in the
Finder by typing Command-Shift-G and then typing the dir you are interested
in or simply typing

open dirname

in the Terminal. This makes navigating, renaming and deleting stuff in dirs
like /usr much simpler if your command-line skills have atrophied or just
hate mistyping \ instead of / for paths all the time because your main box
is Win2K :wink:

ka

Kevin Altis wrote:

From: Robin Dunn

"Apple" wxPython 2.5 :
* scripts in /usr/bin
* wxMac libs, headers, share, etc in /usr/lib/wxPython-2.5.1.0p7
* Python packages in /Library/Frameworks/.../site-packages
* Don't forget to redo the symlink

Most of my Unix braincells are dead (same as the ones for Calculus) so
remind me again the actual commands to redo the symlink with correct
permission flags, not destroying subdirs, or whatever else is relevant.
Anything else that needs to be done to return to a "virgin" Panther state
should also be mentioned.

PYSP=/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-packages
sudo rm -rf $PYSP
sudo ln -s /Library/Python/2.3 $PYSP

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

From: Robin Dunn

PYSP=/System/Library/Frameworks/Python.framework/Versions/2.3/lib/
python2.3/site-packages
sudo rm -rf $PYSP
sudo ln -s /Library/Python/2.3 $PYSP

My memory is foggy, but I think the first line should be

setenv PYSP /System/Library/Frameworks/Python.framework/Versions/2.3/lib/

since the default Mac shell is tcsh, but maybe you changed your shell to
bash or something else. Anyway, thanks for the reminder.

<whine> :slight_smile:
So, the final question is whether you're going to do a "fixed" set of
Panther 2.4.x and 2.5.x installers now that I have everything wx obliterated
they exist?! :wink: I'm not in a super hurry, but obviously won't be doing any
Mac testing... until wx 2.4.x and 2.5.x are running on my Panther box. I do
have the dev tools, but wouldn't trust myself to do a proper compile, link,
and install since that skill set disappeared years ago.
</whine>

ka

···

from my system or should I coerce Kevin to provide some disk images assuming

Kevin Altis wrote:

From: Robin Dunn

PYSP=/System/Library/Frameworks/Python.framework/Versions/2.3/lib/
python2.3/site-packages
sudo rm -rf $PYSP
sudo ln -s /Library/Python/2.3 $PYSP

My memory is foggy, but I think the first line should be

setenv PYSP /System/Library/Frameworks/Python.framework/Versions/2.3/lib/

since the default Mac shell is tcsh, but maybe you changed your shell to
bash or something else. Anyway, thanks for the reminder.

Yes, I use bash.

Also, I indended to mention before that you can get a list of files from the installer packages to help you know what to remove. Just start the installer and then after you accept the license you can go to the file menu and select Show Files.

<whine> :slight_smile:
So, the final question is whether you're going to do a "fixed" set of
Panther 2.4.x and 2.5.x installers now that I have everything wx obliterated
from my system or should I coerce Kevin to provide some disk images assuming
they exist?! :wink:

I'm redoing the 2.5 apple package right now. It sounds like Kevin's last 2.4 panther build (the one on SF) should already do the right thing.

I'm not in a super hurry, but obviously won't be doing any
Mac testing... until wx 2.4.x and 2.5.x are running on my Panther box. I do
have the dev tools, but wouldn't trust myself to do a proper compile, link,
and install since that skill set disappeared years ago.

Although it wouldn't hurt to have a skill-less person go through the BUILD.txt and INSTALL.txt instructions as a test. OTOH, they do state that I expect the person using them knows what they are doing, so maybe they are already good enough :wink:

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Robin Dunn wrote:

I'm redoing the 2.5 apple package right now. It sounds like Kevin's last 2.4 panther build (the one on SF) should already do the right thing.

One more thing... Does my use of "apple" and "local" make sense in the names or would it be better to use "panther" and "jaguar"? I chose the former because you can do your own builds of MacPython on Panther and they should end up being installed just like MacPython on jaguar, and theoretically the "local" build of wxPython would work with them too. Any better ideas?

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Hi Robin,

Robin Dunn wrote:

I'm redoing the 2.5 apple package right now. It sounds like Kevin's last 2.4 panther build (the one on SF) should already do the right thing.

One more thing... Does my use of "apple" and "local" make sense in the names or would it be better to use "panther" and "jaguar"? I chose the former because you can do your own builds of MacPython on Panther and they should end up being installed just like MacPython on jaguar, and theoretically the "local" build of wxPython would work with them too. Any better ideas?

I'd just use Panther and Jaguar, as anyone who's building and installing MacPython from source should know enough about MacPython and Unix to know either to try the Jaguar installer or just build wxPython themselves. =) In any case, they've probably got more serious problems to worry about, because I believe Apple Python does keep the Jaguar Python site-packages folder on its path, meaning that modules from the two installations could easily get jumbled together... :wink:

Thanks,

Kevin

···

On Jan 21, 2004, at 11:05 AM, Robin Dunn wrote:

Hi,

Kevin Altis wrote:

From: Robin Dunn

PYSP=/System/Library/Frameworks/Python.framework/Versions/2.3/lib/
python2.3/site-packages
sudo rm -rf $PYSP
sudo ln -s /Library/Python/2.3 $PYSP

My memory is foggy, but I think the first line should be
setenv PYSP /System/Library/Frameworks/Python.framework/Versions/2.3/lib/
since the default Mac shell is tcsh, but maybe you changed your shell to
bash or something else. Anyway, thanks for the reminder.

Yes, I use bash.

Also, I indended to mention before that you can get a list of files from the installer packages to help you know what to remove. Just start the installer and then after you accept the license you can go to the file menu and select Show Files.

BTW, bash is the default shell in Panther, but if you upgraded from Jaguar, you keep tcsh as your default shell. (I upgraded and so am also using tcsh.)

<whine> :slight_smile:
So, the final question is whether you're going to do a "fixed" set of
Panther 2.4.x and 2.5.x installers now that I have everything wx obliterated
from my system or should I coerce Kevin to provide some disk images assuming
they exist?! :wink:

I'm redoing the 2.5 apple package right now. It sounds like Kevin's last 2.4 panther build (the one on SF) should already do the right thing.

I'm not in a super hurry, but obviously won't be doing any
Mac testing... until wx 2.4.x and 2.5.x are running on my Panther box. I do
have the dev tools, but wouldn't trust myself to do a proper compile, link,
and install since that skill set disappeared years ago.

Although it wouldn't hurt to have a skill-less person go through the BUILD.txt and INSTALL.txt instructions as a test. OTOH, they do state that I expect the person using them knows what they are doing, so maybe they are already good enough :wink:

Well, I can say that I was able to follow the instructions, and with regards to this stuff, I'm as close to skill-less as they come. :slight_smile: Seriously, they are well-written instructions, and the instructions about creating a separate location for 2.5 builds and how to switch/manage builds was really good for people who are not too used to the Unix way of doing things. It was a real life-saver in terms of letting me test the new builds! =)

Thanks,

Kevin

···

On Jan 21, 2004, at 10:57 AM, Robin Dunn wrote:

From: Robin Dunn

Robin Dunn wrote:
>
> I'm redoing the 2.5 apple package right now. It sounds like Kevin's
> last 2.4 panther build (the one on SF) should already do the
right thing.

One more thing... Does my use of "apple" and "local" make sense in the
names or would it be better to use "panther" and "jaguar"? I chose the
former because you can do your own builds of MacPython on Panther and
they should end up being installed just like MacPython on jaguar, and
theoretically the "local" build of wxPython would work with them too.
Any better ideas?

I would use jaguar and panther. Also, it is unclear whether Apple will
update the build of Python (unlikely), so I'm wondering how a build by Jack
say for 2.3.3 that replaces Apple's 2.3 or installs into a different dir and
changes the /usr/bin symlinks will impact this discussion?! Guess I need to
pay more attention to pythonmac-sig. As a side note, I just noticed there is
a /usr/bin/pydoc dir on my box; argh, wonder where that came from since it
has a different date than other 2.3 files. Sigh, Windows continues to be the
simpler platform to install and use Python and wxPython.

Anyway, for completeness sake I wanted to echo the file list for Kevin's
2.4.2.4 jaguar build... This is copied verbatim from the installer, I just
edited out the redundant sub-dirs and files.

I'm assuming .DS_Store files should not be deleted.

Listing files for wxPythonOSX (wxPythonOSX-2.4.2.4-panther)

./.DS_Store
./Applications/wxPythonOSX-2.4.2.4-panther/
  ALL FILES AND DIRS UNDER wxPythonOSX-2.4.2.4-panther
./Library/.DS_Store
./Library/Python/.DS_Store
./Library/Python/2.3/wx/
  ALL FILES AND DIRS UNDER wx
./Library/Python/2.3/wxPython/
  ALL FILES AND DIRS UNDER wxPython
./usr/local/bin/helpviewer
./usr/local/bin/helpviewer.py
./usr/local/bin/img2png
./usr/local/bin/img2py
./usr/local/bin/img2xpm
./usr/local/bin/pyalacarte
./usr/local/bin/pyalacarte.py
./usr/local/bin/pyalamode
./usr/local/bin/pyalamode.py
./usr/local/bin/pycrust
./usr/local/bin/pycrust.py
./usr/local/bin/pyshell
./usr/local/bin/pyshell.py
./usr/local/bin/pywrap
./usr/local/bin/pywrap.py
./usr/local/bin/xrced
./usr/local/bin/xrced.py
./usr/local/lib/libwx_mac-2.4.0.1.1.dylib
./usr/local/lib/libwx_mac-2.4.0.dylib
./usr/local/lib/libwx_mac-2.4.0.r
./usr/local/lib/libwx_mac-2.4.0.rsrc
./usr/local/lib/libwx_mac-2.4.dylib
./usr/local/lib/libwx_mac_gl-2.4.0.1.1.dylib
./usr/local/lib/libwx_mac_gl-2.4.0.dylib
./usr/local/lib/libwx_mac_gl-2.4.dylib
./usr/local/share/aclocal/wxwin.m4

ka

Kevin Ollivier wrote:

Hi Robin,

Robin Dunn wrote:

I'm redoing the 2.5 apple package right now. It sounds like Kevin's last 2.4 panther build (the one on SF) should already do the right thing.

One more thing... Does my use of "apple" and "local" make sense in the names or would it be better to use "panther" and "jaguar"? I chose the former because you can do your own builds of MacPython on Panther and they should end up being installed just like MacPython on jaguar, and theoretically the "local" build of wxPython would work with them too. Any better ideas?

I'd just use Panther and Jaguar, as anyone who's building and installing MacPython from source should know enough about MacPython and Unix to know either to try the Jaguar installer or just build wxPython themselves. =)

Good point. Okay, I'll switch.

In any case, they've probably got more serious problems to worry about, because I believe Apple Python does keep the Jaguar Python site-packages folder on its path, meaning that modules from the two installations could easily get jumbled together... :wink:

No, my Apple Python only has /System/Library/... dirs in the sys.path by default. I do remember now some messages about the order that frameworks are searched that caused problems with binary extension modules if both were installed. Maybe that is what you are thinking about.

···

On Jan 21, 2004, at 11:05 AM, Robin Dunn wrote:

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Hi Kevin,

From: Robin Dunn

Robin Dunn wrote:

I'm redoing the 2.5 apple package right now. It sounds like Kevin's
last 2.4 panther build (the one on SF) should already do the

right thing.

One more thing... Does my use of "apple" and "local" make sense in the
names or would it be better to use "panther" and "jaguar"? I chose the
former because you can do your own builds of MacPython on Panther and
they should end up being installed just like MacPython on jaguar, and
theoretically the "local" build of wxPython would work with them too.
Any better ideas?

I would use jaguar and panther. Also, it is unclear whether Apple will
update the build of Python (unlikely), so I'm wondering how a build by Jack
say for 2.3.3 that replaces Apple's 2.3 or installs into a different dir and
changes the /usr/bin symlinks will impact this discussion?!

They won't be able to do this, because it is a system component and Apple did do some extra things, like write a core-graphics wrapper, which could potentially break if people start throwing their own builds inside of /System. And truth to tell, we don't even know where all Apple is using Python scripts for things... If they've written a CoreGraphics wrapper, we could see some apps now or in the future that are dependent on this. =)

I think there have been discussions on how to update Python without mucking with Apple's version, but I'm not sure how far they got with this.

Guess I need to
pay more attention to pythonmac-sig. As a side note, I just noticed there is
a /usr/bin/pydoc dir on my box; argh, wonder where that came from since it
has a different date than other 2.3 files. Sigh, Windows continues to be the
simpler platform to install and use Python and wxPython.

Yeah, although if Apple doesn't rock the boat from here on in, Mac having a system-installed Python will make it the easiest platform to get up and running on. =) I do think Apple will continue to update Python, at least whenever a new OS X comes out, which is almost too often in my book. :wink: There's also wxPackageManager, which should simplify package installation and updates on all platforms, but I haven't had much time to further work on this. (In it's defense though, it's quite useful as is on Mac!)

Kevin

···

On Jan 21, 2004, at 11:39 AM, Kevin Altis wrote:

Robin Dunn wrote:

PYSP=/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-packages

sudo rm -rf $PYSP
sudo ln -s /Library/Python/2.3 $PYSP

shouldn't this be:

sudo ln -s /Library/Python/2.3/site-packages $PYSP

I don't think we should assume everything in /Library/Python/2.3/ is site-packages, wouldn't you put include files, etc in there?

Kevin Ollivier wrote:
There's also wxPackageManager, which should

simplify package installation and updates on all platforms, but I haven't had much time to further work on this. (In it's defense though, it's quite useful as is on Mac!)

well, yes, but you need wxPython installed first :-(.

-Chris

···

--
Christopher Barker, Ph.D.
Oceanographer
                                         
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

Chris.Barker@noaa.gov

Chris Barker wrote:

Robin Dunn wrote:

PYSP=/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-packages

sudo rm -rf $PYSP
sudo ln -s /Library/Python/2.3 $PYSP

shouldn't this be:

sudo ln -s /Library/Python/2.3/site-packages $PYSP

I don't think we should assume everything in /Library/Python/2.3/ is site-packages, wouldn't you put include files, etc in there?

There are a few clues that lead me to beleive that what I had above is correct. There is no site-packages in /Library/Python/2.3, and also the README that is normally in site-packages is installed in /L/P/2.3, as well as when you install the MacPython-OSX apps it puts the waste.so module in /L/P/2.3.

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Kevin Ollivier wrote:

Hi,

[...]

Although it wouldn't hurt to have a skill-less person go through the BUILD.txt and INSTALL.txt instructions as a test. OTOH, they do state that I expect the person using them knows what they are doing, so maybe they are already good enough :wink:

Well, I can say that I was able to follow the instructions, and with regards to this stuff, I'm as close to skill-less as they come. :slight_smile:

Well, if you can manage building Mozilla on three platforms then I certainly wouldn't say you're skill-less!

Seriously, they are well-written instructions, and the instructions about creating a separate location for 2.5 builds and how to switch/manage builds was really good for people who are not too used to the Unix way of doing things. It was a real life-saver in terms of letting me test the new builds! =)

Have you had a chance to read the new versions from a week or two ago? I've done away with the old separate BUILD.* docs for each platform, and also made the README.1st.txt be just an intro and then refer to these other docs.

  wxPython/docs/BUILD.txt
  wxPython/docs/INSTALL.txt

···

On Jan 21, 2004, at 10:57 AM, Robin Dunn wrote:

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Hi Robin,

Kevin Ollivier wrote:

Hi,

[...]

Although it wouldn't hurt to have a skill-less person go through the BUILD.txt and INSTALL.txt instructions as a test. OTOH, they do state that I expect the person using them knows what they are doing, so maybe they are already good enough :wink:

Well, I can say that I was able to follow the instructions, and with regards to this stuff, I'm as close to skill-less as they come. :slight_smile:

Well, if you can manage building Mozilla on three platforms then I certainly wouldn't say you're skill-less!

Thanks, although stubborn might be a better word... :slight_smile:

Seriously, they are well-written instructions, and the instructions about creating a separate location for 2.5 builds and how to switch/manage builds was really good for people who are not too used to the Unix way of doing things. It was a real life-saver in terms of letting me test the new builds! =)

Have you had a chance to read the new versions from a week or two ago? I've done away with the old separate BUILD.* docs for each platform, and also made the README.1st.txt be just an intro and then refer to these other docs.

  wxPython/docs/BUILD.txt
  wxPython/docs/INSTALL.txt

I just went ahead and took a look at them. They both look good, though I've never followed the Windows build instructions so all I can say is that the instructions were clear. =) There's a small typo in the last paragraph of step 8 in BUILD.txt where "setup.py" is listed as "setuyp.py".

Also, in light of our discussion here, in INSTALL.txt there should probably be a note that Apple Python extensions should be installed in /Library/Python/2.3. <G>

Thanks,

Kevin

···

On Jan 21, 2004, at 1:19 PM, Robin Dunn wrote:

On Jan 21, 2004, at 10:57 AM, Robin Dunn wrote: