Baffled continuous newbie install question

1. So the fact that what I cobbled together to get the two (Python 2.4.1 and wxPython 2.5.4.1 from the .dmg) working together is more or less an accident? Meaning I guess that if I had happened to be calling on certain parts of wx it wouldn't have worked?

2. I got wxPython/wxWidgets built from source, as far as I can tell. I haven't yet *quite* figured out how to get Python (2.4.1) to find wx, but if I keep fiddling around I'll probably get there. Is there someplace where the whole tangle of paths and PATHs and .pths, as they work on OSX, is laid out? I think this is one of those things that are easy if you start from Unix, baffling if you start from Python.

Charles Hartman

Charles Hartman wrote:

1. So the fact that what I cobbled together to get the two (Python 2.4.1 and wxPython 2.5.4.1 from the .dmg) working together is more or less an accident? Meaning I guess that if I had happened to be calling on certain parts of wx it wouldn't have worked?

Well since the Python API version numbers are the same then it is probably safer than I had originally thought. The potential issue here is that if wxPython is compiled with the headers from Python 2.3 then the code that calls the Python API functions will be compiled a certain way. If any of those interfaces has changed or been extended in some way then the 2.3 code that tries to call a 2.4 function could do something wrong with respect to the new function.

2. I got wxPython/wxWidgets built from source, as far as I can tell. I haven't yet *quite* figured out how to get Python (2.4.1) to find wx, but if I keep fiddling around I'll probably get there.

Did you do the install step so that the wxPython modules would be installed to /Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages ?

ยทยทยท

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