Re: [GRASS-dev] [GRASS GIS] #2047: GRASS doesn't build on FreeBSD

2014-04-28 Thread GRASS GIS
#2047: GRASS doesn't build on FreeBSD --+- Reporter: lbartoletti | Owner: grass-dev@… Type: defect | Status: closed Priority: critical | Milestone: 6.4.4

Re: [GRASS-dev] GRASS 7 Coverity Scan enabled

2014-04-28 Thread Markus Neteler
On Mon, Apr 28, 2014 at 9:54 PM, Martin Landa wrote: > Hi, > > 2014-04-28 21:51 GMT+02:00 Markus Neteler : >> Pietro originally registered GRASS in Coverity Scan end of last year, >> today I uploaded a Linux 64bit built of GRASS 7.trunk to the system. > > great, just a small note, would be possibl

Re: [GRASS-dev] GRASS 7 Coverity Scan enabled

2014-04-28 Thread Martin Landa
Hi, 2014-04-28 21:51 GMT+02:00 Markus Neteler : > Pietro originally registered GRASS in Coverity Scan end of last year, > today I uploaded a Linux 64bit built of GRASS 7.trunk to the system. great, just a small note, would be possible to change Project name from 'grass' to 'GRASS GIS'? Martin ___

Re: [GRASS-dev] Handling of Python scripts on MS Windows

2014-04-28 Thread Helmut Kudrnovsky
Hamish wrote: >I think that's more a reflection on the way things are done in the MS >Windows world: the last program to install itself wins. yes >Which leads to >the usual 1st trouble shooting step on Windows after seeing if a >rebooting helps: try uninstalling then reinstalling the program. Th

Re: [GRASS-dev] pygrass documentation

2014-04-28 Thread Vaclav Petras
On Mon, Apr 28, 2014 at 9:23 AM, Pietro wrote: > On Mon, Apr 28, 2014 at 2:57 PM, Vaclav Petras > wrote: > > [cut] I'm also afraid of introducing another markup (we have now HTML > > for doc and HTML+Markdown+Doxygen+Doxygen-LaTeX-like for programming), > > although reStructuredText is almost Py

Re: [GRASS-dev] pygrass documentation

2014-04-28 Thread Pietro
On Mon, Apr 28, 2014 at 2:57 PM, Vaclav Petras wrote: > [cut] I'm also afraid of introducing another markup (we have now HTML > for doc and HTML+Markdown+Doxygen+Doxygen-LaTeX-like for programming), > although reStructuredText is almost Python standard. But anyway, I think > that using Sphinx and

Re: [GRASS-dev] pygrass documentation

2014-04-28 Thread Pietro
Hi Markus and Martin, sorry for the late reply but I'm without connection on these days... On Mon, Apr 28, 2014 at 7:39 AM, Markus Neteler wrote: > ... Sphinx issue solved on server (it was an issue in the cronjob > script). Now available: > > The PyGRASS manual (Sphinx based), updated weekly:

Re: [GRASS-dev] pygrass documentation

2014-04-28 Thread Vaclav Petras
On Mon, Apr 28, 2014 at 1:39 AM, Markus Neteler wrote: > At this point we may consider to document all Python API in reST > (rather than using doxygen for > http://grass.osgeo.org/programming7/pygrasslib.html ) > +1 Doxygen does not work well for Python and from what I understood on their maili

[GRASS-dev] [GRASS GIS] #2265: lib/rst/qtree.c compilation error

2014-04-28 Thread GRASS GIS
#2265: lib/rst/qtree.c compilation error ---+ Reporter: neteler| Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.0.0

Re: [GRASS-dev] Handling of Python scripts on MS Windows

2014-04-28 Thread Markus Neteler
On Mon, Apr 28, 2014 at 9:37 AM, Moritz Lennert wrote: ... > From the current discussion I take that the .bat file solution is one that > will satisfy those who want GRASS to "just work" on MS Windows without > putting any burden on the user. In order to not dissatisfy those who do not > want GRAS

Re: [GRASS-dev] Handling of Python scripts on MS Windows

2014-04-28 Thread Moritz Lennert
On 27/04/14 22:52, Markus Metz wrote: I do not understand this ongoing discussion on WinGRASS7+Python. My proposed solution caters for all possibilities, in particular: - an existing incompatible .py file assocation [add your workaround here] - changes in any existing .py file association after