See comments below.
Glynn Clements wrote:
GRASS 6.4.0svn (Morgan_Hill) assoc .py
.py=py_auto_file
GRASS 6.4.0svn (Morgan_Hill) ftype py_auto_file
py_auto_file=C:\OSGeo4W\bin\python.exe %1 %*
GRASS 6.4.0svn (Morgan_Hill) C:\Temp\printargs.py this is a test
C:\Temp\printargs.py
Moskovitz, Bob wrote:
Okay, so Python is working fine.
If python is working, can you explain why my first example
( C:\Temp\printargs.py this is a test ) only prints out sys.argv[0]
?
Sorry, I overlooked that one.
I believe that my problem has nothing to do with g.parser. I
believe
Okay, so Python is working fine.
Bob wrote:
If python is working, can you explain why my first example
( C:\Temp\printargs.py this is a test ) only prints out sys.argv[0]
?
Glynn:
Sorry, I overlooked that one.
I believe that my problem has nothing to do with g.parser. I
believe
Moskovitz, Bob wrote:
1. Ensure that .py files are configured to be run with the Python
interpreter. You should be able to double-click on a .py file in
Explorer and have it run. This should be done by the Python installer,
but I don't know if the OSGeo4W installer does this.
If it
Glynn Clements wrote:
1. Ensure that .py files are configured to be run with the Python
interpreter. You should be able to double-click on a .py file in
Explorer and have it run. This should be done by the Python installer,
but I don't know if the OSGeo4W installer does this.
If it isn't,
Bob Moskovitz:
I noticed that most of the *.bat files have forward slashes.
For example:
C:\OSGeo4W\apps\grass\bin\grass64.bat: set
WINGISBASE=/c/OSGeo4W/apps/grass/grass-6.4.0RC4
C:\OSGeo4W\apps\grass\grass-6.4.0svn\bin\d.correlate.bat:@%GRASS_SH% -c
dissemination, distribution, or copying of this communication is strictly
prohibited.
-Original Message-
From: Glynn Clements [mailto:gl...@gclements.plus.com]
Sent: Monday, June 22, 2009 7:22 PM
To: Moskovitz, Bob
Cc: Grass-User (E-mail)
Subject: RE: [GRASS-user] Problems with GRASS
Moskovitz, Bob wrote:
I noticed that most of the *.bat files have forward slashes. For example:
C:\OSGeo4W\apps\grass\bin\grass64.bat:set
WINGISBASE=/c/OSGeo4W/apps/grass/grass-6.4.0RC4
C:\OSGeo4W\apps\grass\grass-6.4.0svn\bin\d.correlate.bat:
.
-Original Message-
From: Glynn Clements [mailto:gl...@gclements.plus.com]
Sent: Friday, June 19, 2009 7:03 PM
To: Moskovitz, Bob
Cc: Grass-User (E-mail)
Subject: Re: [GRASS-user] Problems with GRASS python code in osgeo4w
Moskovitz, Bob wrote:
I'm trying to figure out how to write
Bob Moskovitz wrote:
So, I still don't know why the grass.parser() is not
working for me. I even modified my program to use pdb
to see what is happening. The debugger is aborted
right after I reach os.execvp(g.parser.exe, [name] + argv)
in grass.py. But if I use python
.
-Original Message-
From: Hamish [mailto:hamis...@yahoo.com]
Sent: Monday, June 22, 2009 10:42 AM
To: Glynn Clements; Moskovitz, Bob
Cc: Grass-User (E-mail)
Subject: RE: [GRASS-user] Problems with GRASS python code in osgeo4w
Bob Moskovitz wrote:
So, I still don't know why
Moskovitz, Bob wrote:
Thanks for the info. I didn't know about the assoc and ftype. Looking
at the output of these two commands, I see that my system is set up
correctly.
So, I still don't know why the grass.parser() is not working for me. I
even modified my program to use pdb to see
Hamish wrote:
So, I still don't know why the grass.parser() is not
working for me. I even modified my program to use pdb
to see what is happening. The debugger is aborted
right after I reach os.execvp(g.parser.exe, [name] + argv)
in grass.py. But if I use python
-
From: Glynn Clements [mailto:gl...@gclements.plus.com]
Sent: Monday, June 22, 2009 3:30 PM
To: Moskovitz, Bob
Cc: Grass-User (E-mail)
Subject: RE: [GRASS-user] Problems with GRASS python code in osgeo4w
Moskovitz, Bob wrote:
Thanks for the info. I didn't know about the assoc
4:07 PM
To: Glynn Clements
Cc: Grass-User (E-mail)
Subject: RE: [GRASS-user] Problems with GRASS python code in osgeo4w
There is no etc/python/grass/script/core.py. Just
etc\python\grass.py. Here is a part of a pdb debug session:
c:\osgeo4w\apps\grass\grass-~1.0sv\etc\python
, 2009 4:17 PM
To: Moskovitz, Bob; Glynn Clements
Cc: Grass-User (E-mail)
Subject: RE: [GRASS-user] Problems with GRASS python code in osgeo4w
I also wanted to add that I did run the program like this:
c:\osgeo4w\apps\grass\grass-6.4.0svn\scripts\m.dipslope.py --help
-Original
Moskovitz, Bob wrote:
There is no etc/python/grass/script/core.py. Just
etc\python\grass.py.
That changed in the last month or so, but I don't think that it has
any bearing on this.
Here is a part of a pdb debug session:
Moskovitz, Bob wrote:
I'm trying to figure out how to write python scripts using grass.py
under osgeo4w. I was hoping that python script (and the binary
commands) would behave similarly to the grass environment on my Ubuntu
box. You know...just type the command and the gui for that command
18 matches
Mail list logo
