Hi,
currently we have Python version of g.extension script in GRASS 7 and
Bash version in GRASS 6.5. It's pain to maintain the both version. I
would suggest to replace Bash version with Python in GRASS 6.5. It's
new module, so no backwards compatibility will be broken. Only one
drawback is that g.extension will requires Python to be available.
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa
Martin wrote:
currently we have Python version of g.extension script in GRASS 7 and
Bash version in GRASS 6.5. It's pain to maintain the both version. I
would suggest to replace Bash version with Python in GRASS 6.5. It's
new module, so no backwards compatibility will be broken. Only one
drawback is that g.extension will requires Python to be available.
AFAIU the shell script version of g.extension is slated to be backported
to the release branch for 6.4.1. it's there, it works (AFAIK), so leave
it alone and focus our attention on new devel for grass 7. See also
Michael's post about the ongoing problem of getting python scripts to
work with GRASS 6, & it's all platforms:
https://trac.osgeo.org/grass/ticket/928
we need to get that 100% solid before even thinking about doing much
else in the way of python + grass6.
talking generally-
Please leave 6.5 as a test-bed for backporting things to 6.4, otherwise
we never seriously work on stabilizing 6.4 and we never fully commit to
working on grass7.
my humble 2c,
Hamish
On Thu, May 6, 2010 at 1:02 PM, Hamish <hamish_b@yahoo.com> wrote:
Martin wrote:
currently we have Python version of g.extension script in GRASS 7 and
Bash version in GRASS 6.5. It's pain to maintain the both version. I
would suggest to replace Bash version with Python in GRASS 6.5. It's
new module, so no backwards compatibility will be broken. Only one
drawback is that g.extension will requires Python to be available.AFAIU the shell script version of g.extension is slated to be backported
to the release branch for 6.4.1. it's there, it works (AFAIK),
I don't think so - there are lots of problems reported in the list.
Are you sure? I would rather make it a python script since the shell
version is a pain.
Markus
Hi,
2010/5/6 Markus Neteler <neteler@osgeo.org>:
On Thu, May 6, 2010 at 1:02 PM, Hamish <hamish_b@yahoo.com> wrote:
Martin wrote:
currently we have Python version of g.extension script in GRASS 7 and
Bash version in GRASS 6.5. It's pain to maintain the both version. I
would suggest to replace Bash version with Python in GRASS 6.5. It's
new module, so no backwards compatibility will be broken. Only one
drawback is that g.extension will requires Python to be available.AFAIU the shell script version of g.extension is slated to be backported
to the release branch for 6.4.1. it's there, it works (AFAIK),I don't think so - there are lots of problems reported in the list.
Are you sure? I would rather make it a python script since the shell
version is a pain.
g.extension script is quite new, hypothetically if MarkusN started to
write this script in Python would it be included also in GRASS 6.5?
Keeping two versions of relatively new script is really a pain. I am
working on some improvements in g.extension which would be quite
complicated to implement in Bash. The result will be g.extension
(still Bash) with very limited functionality in GRASS 6.
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa
On Thu, May 6, 2010 at 7:11 PM, Michael Barton <michael.barton@asu.edu> wrote:
Unless something has changed in the past couple weeks, Python scripts do not run
in Windows (although Python does run from within the wxGUI environment).
OK, so they partially run.
This seems to indicate that not the scripts are broken but the calling
mechanism?
Anyway, the related trac ticket will discuss this...
That is,
g.extension won't run from the MSys or Windows command window. I'm not sure
if it will run even from the wxGUI menu. IMHO, it is very important that we solve this issue.
In the first place g.extension could be added to the wxGUI menu (as
Windows users
know it for the R-GUI in R-stats) to get this functionality in.
Markus
Hi,
2010/5/6 Markus Neteler <neteler@osgeo.org>:
[...]
That is,
g.extension won't run from the MSys or Windows command window. I'm not sure
if it will run even from the wxGUI menu. IMHO, it is very important that we solve this issue.In the first place g.extension could be added to the wxGUI menu (as
Windows users
know it for the R-GUI in R-stats) to get this functionality in.
done, see also an experimental prototype of the extension manager in GRASS 7
http://gama.fsv.cvut.cz/~landa/grass/swf/install-addons.html
I still incline to replace g.extension Bash script by Python version.
There is small probability that the new features (-f/-g flags) from
Python script will be implemented also in Bash.
Martin
--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa