Hi Richard, On Tue, 08. Sep 2020 at 09:05:05 +0200, Richard Duivenvoorde wrote: > If you start the osgeo4w command prompt, both in standalone and osgeo4w > version, you have to run py3_env before being able to use (the QGIS used) > python there (or am I wrong. I tested by running osgeo4w.bat within a 3.14 > standalone install)
> I know this was to be able to handle both py2 and py3, but I do not think we > need to use python2 anymore is it? py2 is still available in osgeo4w - although we don't use it anymore for QGIS. > In that case I would propose to make py3_env part of the osgeo4w.bat file so > we can instruct people to just go to the osgeo4w bat file to eventually pip > install modules usable in QGIS? You could also just move py3_env.bat to etc\ini\python3-core.bat and create an empty py3_env.bat. Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden https://www.norbit.de QGIS release manager (PSC) Germany IRC: jef on FreeNode
signature.asc
Description: PGP signature
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH Rheinstrasse 13, 26506 Norden GF: Juergen Fischer, Nils Kutscher HR: Amtsgericht Aurich HRB 100827 Datenschutzerklaerung: https://www.norbit.de/83/
_______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
