winGRASS 7: solve python distribution

[martinl]

Before releasing GRASS 7 we need urgently solve Python distribution issues on MS Windows for

• standalone installer
• osgeo4w installer

See ​http://osgeo-org.1560.n6.nabble.com/r54612-grass-trunk-mswindows-wingrass-attempt-to-define-python-file-association-td5027314.html

[hellik]

Replying to martinl:

Before releasing GRASS 7 we need urgently solve Python distribution issues on MS Windows for

• standalone installer
• osgeo4w installer

IMHO also relevant for winGRASS6.4.3svn, because there are some nice grass6-addons written in python, but actually not usable in winGRASS6.4.3svn.

Helmut

[hellik]

Replying to martinl:

Before releasing GRASS 7 we need urgently solve Python distribution issues on MS Windows for

• standalone installer

related to the standalone installer:

​http://trac.osgeo.org/grass/ticket/1282

[hellik]

Replying to hellik:

IMHO also relevant for winGRASS6.4.3svn, because there are some nice grass6-addons written in python, but actually not usable in winGRASS6.4.3svn.

related to the python-grass6-addons, see

​http://trac.osgeo.org/grass/ticket/1555

[wenzeslaus]

See also:

• #580 WinGRASS: $GISBASE/etc/gui/scripts/ require something like $(EXE) to run (possible duplicate)
• #2150 Cannot call Python scripts from Python on MS Windows (possible duplicate)
• #2138 winGRASS6.4.svn - addon python script status?
• ​Handling of Python scripts on MS Windows
• ​Handling of Python scripts on MS Windows (question how QGIS and OSGeo4W works)
• r54612 - source:grass/trunk/mswindows - ​wingrass: attempt to define python file association (the original email thread for this ticket)
• ​last message of the original email thread

[martinl]

The most of issues have been already solved, see #2150. Is there any particular reason why this ticket is still open?

[hellik]

Replying to martinl:

The most of issues have been already solved, see #2150. Is there any particular reason why this ticket is still open?

suggest to close.