On Jun 8, 2013, at 7:18 PM, Michael Barton wrote: > I've been staying with wxPython 2.8.x Perhaps some of the new code only works > correctly in 2.9?
that is the message I have been getting, Helena > > Michael > ____________________ > C. Michael Barton > Director, Center for Social Dynamics & Complexity > Professor of Anthropology, School of Human Evolution & Social Change > Arizona State University > > voice: 480-965-6262 (SHESC), 480-727-9746 (CSDC) > fax: 480-965-7671 (SHESC), 480-727-0709 (CSDC) > www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu > > > > > > > > > > > > On Jun 7, 2013, at 8:39 PM, William Kyngesburye <[email protected]> wrote: > >> I just compiled trunk, no compile errors, and GUI runs fine. >> >> OSX 10.7 Lion, Xcode 4.6.2 command line tools, wxPython 2.9.4 >> >> I'm a bit lost now - what is the status of this, what is the current problem? >> >> On Jun 7, 2013, at 10:28 AM, Michael Barton wrote: >> >>> Maybe it is PYTHONPATH >>> >>> BUT... >>> >>> Python and the GUI is compiling and working just fine otherwise. And Python >>> runs with no problem in the terminal. >>> >>> The bogus errors for compiling mapswipe, composer, etc first appeared with >>> what I think was the introduction of a new window class for these modules. >>> I have not seen the toolbox, but it may reuse the same code. If I knew what >>> this new code is, I might be able to troubleshoot it. But I don't have time >>> to try to reverse engineer it without guidance as to where to look. The >>> error on importing wx is misleading as to what the real error is. >>> >>> I can't say for sure that these are all related (and the error is indeed >>> somewhat different for the toolbox compilation). But it seems a reasonable >>> place to start. >>> >>> If it IS a PYTHONPATH problem, then the code for building the toolbox is >>> somehow ignoring PYTHONPATH because this is set properly otherwise. >>> >> >>>> On Thu, Jun 6, 2013 at 7:16 PM, Michael Barton <[email protected]> >>>> wrote: >>>> Anna, >>>> >>>> This is from the log. It looks to me like a path problem during compilation >>>> >>>> Traceback (most recent call last): >>>> File "tools/build_modules_xml.py", line 85, in <module> >>>> sys.exit(main()) >>>> File "tools/build_modules_xml.py", line 77, in main >>>> header(fh) >>>> File "tools/build_modules_xml.py", line 58, in header >>>> import grass.script.core as grass >>>> ImportError: No module named grass.script.core >>>> make[1]: *** >>>> [/Users/Shared/grass_dev/grass7_dev/dist.x86_64-apple-darwin12.3.0/etc/gui/wxpython/xml/module_items.xml] >>>> Error 1 >>>> make: [default] Error 2 (ignored) >>>> make xml/menudata.xml >>>> make[1]: `xml/menudata.xml' is up to date. >>>> make menustrings.py >>>> >>>> The other bogus errors on "No module named wx" also seems like a path >>>> problem. >>>> >>>> yes, problem might be in PYTHONPATH. Could you ask about this William? I >>>> have currently no time and I am probably not able to solve this. >>>> >>>> Regards, >>>> >>>> Anna >> >>>> On Jun 6, 2013, at 2:39 AM, Anna Petrášová <[email protected]> wrote: >>>> >>>>> Hi, Michael, >>>>> >>>>> >>>>> On Wed, Jun 5, 2013 at 11:45 PM, Michael Barton <[email protected]> >>>>> wrote: >>>>> OK. I did this remotely but hopefully it is what you need. >>>>> >>>>> yes, perfect, thanks. Could you try the compilation again with the change >>>>> William did recently (demolocation probem, [1])? It might be related >>>>> because from the errors in the log it seems that the virtual grass >>>>> session is not there. If the problem is still there, please send me >>>>> updated compilation log. >>>>> >>>>> Thanks, >>>>> Anna >>>>> >>>>> >>>>> [1] https://trac.osgeo.org/grass/changeset/56621 >>>>> >> >> ----- >> William Kyngesburye <kyngchaos*at*kyngchaos*dot*com> >> http://www.kyngchaos.com/ >> >> "The beast is actively interested only in now, and, as it is always now and >> always shall be, there is an eternity of time for the accomplishment of >> objects." >> >> - the wisdom of Tarzan >> >> >> >> >> > > _______________________________________________ > grass-dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-dev _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
