Moritz Lennert wrote: > So what does that mean in practice: just leave everything as is, but > improve the documentation to explain the needed Python > installation/configuration ?
Ideally, as much as possible should be taken care of by the installer. If there's no Python installed, the installer can install it. If Python is installed and the version is compatible, the installer can install any required packages. Otherwise, it can at least inform the user of the situation and enumerate the options. The one thing it can't reasonably do is to replace any existing association for the .py extension. So if the .py extension is already associated with an incompatible version, the user will have to be involved. -- Glynn Clements <gl...@gclements.plus.com> _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
