Re: [GRASS-dev] wxGUI import chain
On Tue, Oct 7, 2014 at 2:24 AM, Pietro wrote: > > On Mon, Oct 6, 2014 at 9:15 PM, Markus Metz > wrote: > > Is there any reason why gui/wxpython/gis_set.py imports (eventually) > > etc/python/grass/pygrass/raster/buffer.py? > > > > Anyway, r62196 fails to start the GUI in trunk because of broken > > pygrass. I doubt if it is a good idea to make pygrass a dependency of > > the GUI. > > I'm not able to reproduce the problem, what kind of error did you get? > > Any way I will work in the __init__ file to isolate the ctypes stuff. So, now I have seen it at someones computer. It was something about np.float* in buffer.py. The problem was in yesterday's build of 7.0 for MS Windows, it is fixed in today's one. ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] wxGUI import chain
Hi Markus, On Mon, Oct 6, 2014 at 9:15 PM, Markus Metz wrote: > Is there any reason why gui/wxpython/gis_set.py imports (eventually) > etc/python/grass/pygrass/raster/buffer.py? > > Anyway, r62196 fails to start the GUI in trunk because of broken > pygrass. I doubt if it is a good idea to make pygrass a dependency of > the GUI. I'm not able to reproduce the problem, what kind of error did you get? Any way I will work in the __init__ file to isolate the ctypes stuff. All the best Pietro ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] wxGUI import chain
On Mon, Oct 6, 2014 at 3:15 PM, Markus Metz wrote: > Is there any reason why gui/wxpython/gis_set.py imports (eventually) > etc/python/grass/pygrass/raster/buffer.py? > > Can you provide a traceback? I cannot reproduce. > Anyway, r62196 fails to start the GUI in trunk because of broken > pygrass. I doubt if it is a good idea to make pygrass a dependency of > the GUI. > Perhaps this is another motivation to separate modules from PyGRASS and empty __init__.py files (#2424). PyGRASS is currently (directly used) used in gui/wxpython/gui_core/gselect.py:56:from grass.pygrass import messages gui/wxpython/tplot/frame.py:44:from grass.pygrass.vector.geometry import Point gui/wxpython/tplot/frame.py:45:from grass.pygrass.raster import RasterRow In tplot is probably can be imported on demand. I'm not sure about gselect, maybe it relates to temporal framework. Temporal framework is used in the GUI and is using PyGRASS. Vaclav http://trac.osgeo.org/grass/ticket/2424 > Markus M > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev > ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev