Re: [GRASS-dev] temporal framework currently not working on windows

2014-12-04 Thread Sören Gebbert
Hi Glynn, thanks a lot for this excellent explanation. Best regards Soeren 2014-11-27 18:59 GMT+01:00 Glynn Clements gl...@gclements.plus.com: Sören Gebbert wrote: I would like to better understand, this point... Why the decorator must_be_open it seems to work so far? which is the

Re: [GRASS-dev] temporal framework currently not working on windows

2014-11-27 Thread Sören Gebbert
Hi, it looks like the problem is the function decorator @mdebug. I am not a Python expert, but IMHO this problem occurs because: 1.) Windows sucks ;) 2.) The function decorator code is analysed at import time, which is a bad idea, since the messaging server process get started at import time.

Re: [GRASS-dev] temporal framework currently not working on windows

2014-11-27 Thread Martin Landa
2014-11-26 21:15 GMT+01:00 Anna Petrášová kratocha...@gmail.com: I just realized temporal framework doesn't work with recent GRASS 70 version on Windows: t.list or t.create give me: [...] File C:\GRASS70\GRASS GIS 7.0.0svn\Python27\lib\multiprocessing\forking.py, line 258, in __init__

Re: [GRASS-dev] temporal framework currently not working on windows

2014-11-27 Thread Pietro
Hi Sören, On Thu, Nov 27, 2014 at 11:38 AM, Sören Gebbert soerengebb...@googlemail.com wrote: My solution would be to remove the function decorator code using the most simple approach to add debug messages to the module interface: Instead of a function decorator we place this code snippet in

Re: [GRASS-dev] temporal framework currently not working on windows

2014-11-27 Thread Pietro
On Thu, Nov 27, 2014 at 11:38 AM, Sören Gebbert soerengebb...@googlemail.com wrote: The function decorator code is analysed at import time, which is a bad idea, since the messaging server process get started at import time. This should be avoided on any OS. I would like to better understand,

Re: [GRASS-dev] temporal framework currently not working on windows

2014-11-27 Thread Sören Gebbert
Unfortunately i have no idea. I did not found good information about when and how exactly these decorators are processed. So my guess was that (because of the backtrace) the decorator function is somehow analyzed at import time and the messenger process gets started. So maybe the difference is

Re: [GRASS-dev] temporal framework currently not working on windows

2014-11-27 Thread Glynn Clements
Sören Gebbert wrote: I would like to better understand, this point... Why the decorator must_be_open it seems to work so far? which is the difference between @must_be_open[0] and @mdebug[1]? Any Ideas? Unfortunately i have no idea. I did not found good information about when and how

[GRASS-dev] temporal framework currently not working on windows

2014-11-26 Thread Anna Petrášová
I just realized temporal framework doesn't work with recent GRASS 70 version on Windows: t.list or t.create give me: Traceback (most recent call last): File string, line 1, in module File C:\GRASS70\GRASS GIS 7.0.0svn\Python27\lib\multiprocessing\forking.py, line 380, in main