[GRASS-dev] Re: bundling wxpython - solves 6.4 digitizer problem

Michael Barton Michael.Barton at asu.edu
Mon Sep 21 14:47:53 EDT 2009

On Sep 21, 2009, at 11:32 AM, William Kyngesburye wrote:

> On Sep 21, 2009, at 1:09 PM, Michael Barton wrote:
>>> The site-packages python path will have whichever wx path that was
>>> loaded last at the top of the path list, which may or may not be the
>>> one you want. (if there are multiple wxpythons installed, and
>>> assuming
>>> that they were installed such that earlier installations aren't
>>> trashed by later installations, which is what the official  
>>> installers
>>> do)
>> Where can I check this?
> There would be other versioned wx folders in /usr/local, with partial
> contents (stuff not directly installed by the installer will be left,
> like script-installed stuff).

Only one version

> Also, make sure there is only one wx path file in your site-packages,
> that points to your only installed wx.

How can I check this path?

>> This fixes the 6.5 map element freezing bug too.
>> This suggests that it is definitely something in the compiling bug.
>> Any chance it could be something introduced with the architecture
>> arguments (which don't seem to be working correctly anyway) or with
>> any additions/updates to the bundling stuff?
> All these new optios do is automate what you've done in the past with
> CFLAGS and LDFLAGS, and make sure that architectures are not compiled
> for wx stuff that are not available (ie when you build a 64bit GRASS).

Something somehow has changed in the Mac compiling. That was the easy  
thing to check. I'm lost as to a suggestion beyond that.


C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Arizona State University
Tempe, AZ  85287-2402

voice: 	480-965-6262; fax: 480-965-7671
www: 	http://csdc.asu.edu, http://shesc.asu.edu

More information about the grass-dev mailing list