Re: [GRASS-dev] [GRASS GIS] #3790: Cleanup gettext usage for python code

2019-03-16 Thread Markus Neteler
Hi devs,

GRASS GIS  schrieb am Di., 12. März 2019, 08:45:

> #3790: Cleanup gettext usage for python code
> --+-
>   Reporter:  pmav99   |  Owner:  grass-dev@…
>   Type:  enhancement  | Status:  new
>   Priority:  normal   |  Milestone:
>  Component:  Python   |Version:  svn-trunk
> Resolution:   |   Keywords:
>CPU:  Unspecified  |   Platform:  Unspecified
> --+-
> Changes (by pmav99):
>
>  * Attachment "gettext_cleanup.diff" added.
>


Are there any objections to apply the changes proposed by pmav99?

Thanks,
Markus


-- 
> Ticket URL: 
> GRASS GIS 
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Question about *.mapcalc_start in Python scripting library

2019-03-16 Thread Michael Barton
OK. That is how I've been using it. Wanted to make sure.

Thanks
Michael

C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu















On Mar 16, 2019, at 11:58 AM, Moritz Lennert 
mailto:mlenn...@club.worldonline.be>> wrote:

Le Fri, 15 Mar 2019 13:15:16 +,
Michael Barton mailto:michael.bar...@asu.edu>> a écrit :

I've been using *.mapcalc_start to do some simple parallel processing
in the i.pansharpen module and in r.landscape.evol. My understanding
previously has been that *.mapcalc_start returns a Popen object that
can be directed to wait to finish (like *.start_command), allowing
multiple mapcalc operations to be initiated on multiple cores.

But when running r.landscape.evol on another computer, it is acting
like mapcalc is not waiting to finish in spite of the *.wait()
commands.

The description in the programmer's manual is not clear to me on this
(see below). In one place, it says it does not wait to finish and in
the example it says it does wait.


AFAIU, the function mapcalc_start() does not wait, i.e. you can go on
with your program while the mapcalc call is still ongoing. If you want
to wait, you have to explicitely call the function wait() of the Popen
object as is done in the example.

Moritz


Can anyone clarify this?

Thanks
Michael

 from programmer's manual 

script.raster.mapcalc_start(exp, quiet=False, verbose=False,
overwrite=False, seed=None, env=None, **kwargs)[source] Interface to
r.mapcalc, doesn’t wait for it to finish, returns Popen object.

output = 'newele'
input = 'elevation'
expr1 = '"%s" = "%s" * 10' % (output, input)
expr2 = '...'   # etc.
# launch the jobs:
p1 = mapcalc_start(expr1)
p2 = mapcalc_start(expr2)
...
# wait for them to finish:
p1.wait()
0
p2.wait()
1

C. Michael Barton
Director, Center for Social Dynamics & Complexity
Professor of Anthropology, School of Human Evolution & Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University

voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
www: 
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.public.asu.edu_-7Ecmbarton=DwIFaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=SMauS2VJMEiccsq53CfPMfOU38B8lsDVCAd7oYqvLoc=eKrRsY0uJUc5RU5WldLfYR1EFjS1oSvI46U21M3qS4U=,
 
https://urldefense.proofpoint.com/v2/url?u=http-3A__csdc.asu.edu=DwIFaQ=l45AxH-kUV29SRQusp9vYR0n1GycN4_2jInuKy6zbqQ=lk-7X7CEOMDN8GaGVhiDsuO6gEp1wbG6nfT1XEEEtR0=SMauS2VJMEiccsq53CfPMfOU38B8lsDVCAd7oYqvLoc=lOB9PM_7bO9sn7VRqX3ZH1gFKM7lufgKzh50Yo2au7M=

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Question about *.mapcalc_start in Python scripting library

2019-03-16 Thread Moritz Lennert
Le Fri, 15 Mar 2019 13:15:16 +,
Michael Barton  a écrit :

> I've been using *.mapcalc_start to do some simple parallel processing
> in the i.pansharpen module and in r.landscape.evol. My understanding
> previously has been that *.mapcalc_start returns a Popen object that
> can be directed to wait to finish (like *.start_command), allowing
> multiple mapcalc operations to be initiated on multiple cores.
> 
> But when running r.landscape.evol on another computer, it is acting
> like mapcalc is not waiting to finish in spite of the *.wait()
> commands.
> 
> The description in the programmer's manual is not clear to me on this
> (see below). In one place, it says it does not wait to finish and in
> the example it says it does wait.


AFAIU, the function mapcalc_start() does not wait, i.e. you can go on
with your program while the mapcalc call is still ongoing. If you want
to wait, you have to explicitely call the function wait() of the Popen
object as is done in the example.

Moritz

> 
> Can anyone clarify this?
> 
> Thanks
> Michael
> 
>  from programmer's manual 
> 
> script.raster.mapcalc_start(exp, quiet=False, verbose=False,
> overwrite=False, seed=None, env=None, **kwargs)[source] Interface to
> r.mapcalc, doesn’t wait for it to finish, returns Popen object.
> 
> >>> output = 'newele'
> >>> input = 'elevation'
> >>> expr1 = '"%s" = "%s" * 10' % (output, input)
> >>> expr2 = '...'   # etc.
> >>> # launch the jobs:
> >>> p1 = mapcalc_start(expr1)
> >>> p2 = mapcalc_start(expr2)  
> ...
> >>> # wait for them to finish:
> >>> p1.wait()  
> 0
> >>> p2.wait()  
> 1
> 
> C. Michael Barton
> Director, Center for Social Dynamics & Complexity
> Professor of Anthropology, School of Human Evolution & Social Change
> Head, Graduate Faculty in Complex Adaptive Systems Science
> Arizona State University
> 
> voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
> fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
> www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 

___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [release] 7.6.1

2019-03-16 Thread Martin Landa
Hi,

ne 10. 3. 2019 v 21:30 odesílatel Martin Landa  napsal:
> wingrass packages available for testing (OSGeo4W Expr and standalone
> [0]). Please note that this release includes two important changes
> [1,2]. Testing is very welcome :-) Thanks, Martin

Ubuntu packages available in UbuntuGIS-Expr PPA for testing. I have
tested both Windows and Ubuntu packages. No (unknown) problems found.
Since this version changes target directory on OSGeo4W it's important
to time it with QGIS release. The next QGIS is scheduled in few days
(22/3).

I would suggest to skip RC2 and release 7.6.1 ASAP. Any objections?

Ma

[1] https://qgis.org/en/site/getinvolved/development/roadmap.html

-- 
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev