#2333: choose python interpreter during the GRASS installation on windows
-------------------------+-------------------------------------------------
Reporter: zarch | Owner: grass-dev@…
Type: | Status: new
enhancement |
Priority: normal | Milestone: 7.1.0
Component: Python | Version: svn-trunk
Resolution: | Keywords: windows installer python
| interpreter
CPU: All | Platform: MSWindows 8
-------------------------+-------------------------------------------------
Comment (by wenzeslaus):
Replying to [comment:27 hellik]:
> as mentioned at other places, there is no system wide python in windows
at all. users has to do the install for themself, also all the packages
Right. Python installed ahead which is on path, registry or whatever is
appropriate - that's what I mean by system Python.
> > It would have to be implemented for the whole OSGeo4W I suppose. The
reason for doing it there is the same as for the standalone version.
OSGeo4W doesn't contain all the packages available through pip and it
doesn't contain pip.
> >
>
> what about to improve the situation in the underlying Osgeo4w?
Good approach. I guess this ticket would still apply standalone installer?
> There are already some starting efforts regarding pip etc.
Do you have some more info about it? Only thing I know is not really
encouraging: [https://lists.osgeo.org/pipermail/osgeo4w-
dev/2015-November/002965.html my question regarding pip from September
2015] and [https://lists.osgeo.org/pipermail/osgeo4w-
dev/2015-September/002957.html answer to it from November].
Even if we ignore the issue that user have to remember to install every
package twice (I guess common on MS Windows), this still doesn't solve the
issue of using the same Python from a Python editor and GRASS or using
GRASS and ArcGIS together (both being a common request).
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/2333#comment:28>
GRASS GIS <https://grass.osgeo.org>