On Wed, Jul 19, 2017 at 1:42 AM, Pietro wrote:
> On Mon, Jul 17, 2017 at 5:36 PM, Vaclav Petras
> wrote:
>
>>
>> On Mon, Jul 17, 2017 at 12:36 AM, Pietro wrote:
>>
>>>
>>> On Fri, Jul 14, 2017 at 6:00 PM, Vaclav Petras
Hi Vaclav,
sorry for the delay but in the last day I was off-line.
On Mon, Jul 17, 2017 at 5:36 PM, Vaclav Petras wrote:
>
> On Mon, Jul 17, 2017 at 12:36 AM, Pietro wrote:
>
>>
>> On Fri, Jul 14, 2017 at 6:00 PM, Vaclav Petras
On Mon, Jul 17, 2017 at 12:36 AM, Pietro wrote:
>
> On Fri, Jul 14, 2017 at 6:00 PM, Vaclav Petras
> wrote:
>
>> This is exactly what I had in my mind when doing the last major changes
>> in the grass.py file.
>>
> I generally like the layout you
Hi Vaclav,
On Fri, Jul 14, 2017 at 6:00 PM, Vaclav Petras wrote:
> This is exactly what I had in my mind when doing the last major changes in
> the grass.py file.
>
I generally like the layout you suggested. It seems to me that choosing a
> good name for the whole module
2017-07-14 19:00 GMT+03:00 Vaclav Petras :
> Also I think one reason for having
> them there was that grass.py works without a he G Python lib found. Vaclav
This! Although having a module would be fine, we must take extra care
to put warnings in all files to not depend on
Hi, Pietro. Just a short answer for now. This is exactly what I had in my
mind when doing the last major changes in the grass.py file. I generally
like the layout you suggested. It seems to me that choosing a good name for
the whole module will be a bit tricky. Also I think one reason for having
Dear devs,
What do you think if we move all the function that at the moment are
contained in `/lib/init/grass.py` into a new subfolder under `/lib/python`?
The main advantages that I see are:
- start a python script in GRASS just setting the the python path and then
I can use the same functions