wenzeslaus wrote
> Please consider this scenario:
>
> 1. user installs ArcGIS which installs Python system-wide
> 2. user installs GRASS GIS which will use system-wide Python
2. may or may not work out of the box ... there are a lot of uncertain
issues to consider (version, dependencies, etc. etc
On Fri, Mar 1, 2013 at 6:50 PM, Vaclav Petras wrote:
...
> For now, I would leave pygrass doc in the ReST (both the py and rst files).
That's fine. Martin and me have fixed the sphinx compilation, this now
works on more recent systems:
cd lib/python/pygrass/docs/
make html
It generates the nice
#2261: failed pygrass doctest
-+--
Reporter: lucadelu | Owner: grass-dev@…
Type: defect | Status: new
Priority: major| Milestone: 7.1.0
On Sat, Apr 26, 2014 at 6:42 AM, Glynn Clements wrote:
> > >> It's easier to check if the file is a python script and if so than
> > >> to force to use bundled version of Python.
> > >
> > > So long as I have commit access, GRASS isn't going to be "forcing" the
> > > use of a non-system Python.
>
2014-04-26 13:16 GMT+02:00 Glynn Clements :
> At least I'm not saying "you ARE going to use our version of Python,
> whether you like it or not".
please ask the Windows users, 99.9% they don't care or they will not
understand your question. The question is completely pointless. The
most of users
Martin Landa wrote:
> > By all means provide fall-backs, workarounds, alternatives, or
> > whatever, but anything which tries to make such things mandatory is
> > going to get reverted. Again.
>
> really nice attitude ;-) Martin
At least I'm not saying "you ARE going to use our version of Pytho
Markus Metz wrote:
> >> It's easier to check if the file is a python script and if so than
> >> to force to use bundled version of Python.
> >
> > So long as I have commit access, GRASS isn't going to be "forcing" the
> > use of a non-system Python.
>
> But an existing system Python on MS Window
