I guess technically it could use the system wxpython. But I can think of a few reasons to still bundle wxpython:
- bug fixes in later versions than the system version that greatly affect use in GRASS (I don't remember, but I think there were some?) - consistency of behavior across system versions from having the same wxpython - 64bit support in wxpython 2.9 when GRASS is happy with 2.9 (or whatever the release version is, 2.10?) - simply that wxpython is not included in the system starting with OS X 10.7 On Jun 30, 2012, at 10:28 PM, Michael Barton wrote: > Does this mean that we no longer *have* to bundle wxPython with the Mac > binaries? That they will work with whatever wxPython is installed (assuming > it is within the range of supported versions, of course) regardless of what > it was compiled with? > > Michael > > On Jun 30, 2012, at 4:32 PM, Glynn Clements wrote: > >> >> Michael Barton wrote: >> >>> Don't you need to have the wxPython that GRASS was compiled with? >>> And doesn't this wxPython have to match the Python version? >> >> GRASS isn't "compiled" with any version of Python, i.e. it doesn't >> have any binaries which link against the Python DLL/DSO. >> >> At one time there were binary modules for the wx GUI's nviz and vdigit >> components, and the SWIG wrappers, but those have all since been >> eliminated. >> ----- William Kyngesburye <kyngchaos*at*kyngchaos*dot*com> http://www.kyngchaos.com/ "This is a question about the past, is it? ... How can I tell that the past isn't a fiction designed to account for the discrepancy between my immediate physical sensations and my state of mind?" - The Ruler of the Universe _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
