#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:6 wenzeslaus]:
> If I understand #2138 correctly, this would mean that we would have to
create a BAT file for every Python script and also user would have to do
the same for his or her own GRASS Python scripts. For sure this is better
than nothing but it seems to me that it resembles r57910 in the way that
it forces the right Python manually.
My opinion is that requiring BAT file for Python scripts is much more
worse solution that r57910.
> If r58680 (fix for #2138) and r57910 do the same thing I would say that
r57910 is easier to implement and creates less noise. Anyway, can r58680
be ported to trunk in some way? Or is somebody preparing some other patch
for this issue (#2150)?
I guess nobody is really working on this issue. And if so his work can be
reverted again without providing any better solution;-)
> By the way, when we can expect Python version 2.7.6 (which will probably
hide this issue) to be packaged in GRASS for MS Windows?
Please ask on osgeo4w mailing list.
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2150#comment:7>
GRASS GIS <http://grass.osgeo.org>
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
