Opened 10 years ago
Closed 9 years ago
#2599 closed defect (fixed)
PyGRASS Raster execution error
Reported by: | aandre | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 7.0.2 |
Component: | Python | Version: | svn-releasebranch70 |
Keywords: | raster | Cc: | |
CPU: | All | Platform: | All |
Description
Hello,
creating my first ticket, i hope it's relevant and the way to do it.
I get 2 errors while executing Python scripts.
source:/branches/releasebranch_7_0/lib/python/pygrass/raster/__init__.py#L415
source:/branches/releasebranch_7_0/lib/python/pygrass/raster/__init__.py#L416
I attached a diff file.
Regards,
Adrien
Attachments (3)
Change History (10)
by , 10 years ago
Attachment: | pygrass_rast_init.diff added |
---|
comment:1 by , 10 years ago
follow-up: 4 comment:2 by , 10 years ago
Thank you for your guidance,
i attached a Python script that generates the error and the error log.
The script is launched with python /path/to/r.test.py elevation=elev
.
elev
can be any raster map.
comment:3 by , 9 years ago
Milestone: | → 6.4.6 |
---|
follow-up: 6 comment:4 by , 9 years ago
Milestone: | 6.4.6 → 7.0.1 |
---|
Replying to aandre:
Thank you for your guidance,
i attached a Python script that generates the error and the error log.
The script is launched with
python /path/to/r.test.py elevation=elev
.
elev
can be any raster map.
I commit (r65714) your patch in GRASS 7.1 (trunk), please try it.
After some tests should be backported.
comment:6 by , 9 years ago
Replying to lucadelu:
Replying to aandre:
Thank you for your guidance,
i attached a Python script that generates the error and the error log.
The script is launched with
python /path/to/r.test.py elevation=elev
.
elev
can be any raster map.I commit (r65714) your patch in GRASS 7.1 (trunk), please try it.
After some tests should be backported.
I tried and no error is reported, it seems to work now!
Thank you
comment:7 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Closing the ticket, It was already backported with r65723
Replying to aandre:
This is definitively the way. Tickets with patch attached are greatly appreciated. There is few things you can improve.
It would be good if you can post what are the steps to reproduce the error you got. In your case probably your Python code but not the whole thing, just minimal piece of code which produces the error (e.g. taken from interactive command line). Use data from GRASS GIS NC sample dataset to help others easily reproduce the problem you have. In ideal case, your code can be used to create a test case which would now expose the error and later serve as a failsafe that the error won't happen again.