[GRASS-dev] python2/3 and GRASS build on Arch
wenzeslaus at gmail.com
Tue Oct 7 17:58:02 PDT 2014
I don't know much but I will try to tell what I know.
On Tue, Oct 7, 2014 at 4:57 PM, Maciej Sieczka <msieczka at sieczka.org> wrote:
> Per 2.8 wxWidgets specified, I don't get it why
> /usr/lib/python2.7/site-packages/wx-3.0-gtk2/ gets
> involved in iclass build. I would rather expect it to
> pick /usr/lib/python2.7/site-packages/wx-2.8-gtk2-unicode/.
As far as I know, this does not select the Python packages but C++ library
to link to for the C++ things which are using wxWidgets (no Python things
which are using wxPython).
> What do you make of this? Like I said, all the other Python bits seem to
build fine. Only iclass doesn't.
I think it is only g.gui.iclass because just this module is importing
something from wx which fails. The other g.gui.* modules (and a toolbox
script) also import wx during compilation but this does not fail.
> This is an Arch box. I do have all the NumPy stuff installed. There is a
problem on Arch that wx-3.0-gtk2/wx/lib/plot.py fails to import
numpy.oldnumeric  leading to those "NumPy not found" errors,
I hope that the upstream error gets fixed because the GRASS one is more
> but that would not happen if iclass build referred to
wx-2.8-gtk2-unicode/wx/lib/plot.py instead - like I guess all the other
GRASS 7 Python modules do.
Yes, there is this mysterious issue where wrong versions of wxPython or
perhaps other things are used during compilation when something runs in
fake GRASS session. The things usually run in the real GRASS session, you
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the grass-dev