[GRASS-dev] [GRASS GIS] #2150: Cannot call Python scripts from Python on MS Windows

[Vaclav Petras]

Hi Martin, bat files could be handled by g.extension. See also ticket to
support compiling C modules on unix. (I cannot search it now.) Python
modules on MS Windows are in the same situation as C modules on unix. Vaclav
On Aug 22, 2014 12:01 AM, "GRASS GIS" <trac at osgeo.org> wrote:

> #2150: Cannot call Python scripts from Python on MS Windows
>
> -------------------------------------------+--------------------------------
>  Reporter:  wenzeslaus                     |       Owner:  grass-dev@…
>      Type:  defect                         |      Status:  new
>  Priority:  blocker                        |   Milestone:  7.0.0
> Component:  Python                         |     Version:
> svn-releasebranch64
>  Keywords:  packaging, MAXREPEAT, scripts  |    Platform:  MSWindows 7
>       Cpu:  Unspecified                    |
>
> -------------------------------------------+--------------------------------
>
> Comment(by martinl):
>
>  Replying to [comment:8 glynn]:
>
>  > > My opinion is that requiring BAT file for Python scripts is much more
>  worse solution that r57910.
>  >
>  > Also, note that there's nothing special about .bat (or .cmd). The
>  mechanism used for "executing" anything other than binary executables is
>  the same, whether it's .bat or .py. If .bat works when .py doesn't, that
>  indicates a fault in the Python installation.
>
>  Update: as a result of never ending discussion I took liberty to add
>  generation of bat files in r61136. The missing part is how to solve user
>  python scripts.
>
> --
> Ticket URL: <http://trac.osgeo.org/grass/ticket/2150#comment:10>
> GRASS GIS <http://grass.osgeo.org>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20140822/638cfa0d/attachment.html>