It removes the whole code to set PYTHONPATH (it was not required in MSYS2 builds anymore).
Can anybody experiencing issues with Inkscape's previous behavior retest if this is still an issue?
We keep adding Inkscape to PATH, but I think this should be fine in most (hopefully all) situations.
Also note that a different Python executable can be selected using the "python-interpreter" preference as explained at [1].
I also confirmed previously that if Inkscape's bundled Python is not installed but a different Python is available on the search path it will be used, too (without modifying "python-interpreter", which defaults to "pythonw" on Windows).
I just committed /gitlab. com/inkscape/ inkscape/ commit/ b1d63f1a3bed6ab e4b74f232172137 d5f48232dd
https:/
It removes the whole code to set PYTHONPATH (it was not required in MSYS2 builds anymore).
Can anybody experiencing issues with Inkscape's previous behavior retest if this is still an issue?
We keep adding Inkscape to PATH, but I think this should be fine in most (hopefully all) situations.
Also note that a different Python executable can be selected using the "python- interpreter" preference as explained at [1].
I also confirmed previously that if Inkscape's bundled Python is not installed but a different Python is available on the search path it will be used, too (without modifying "python- interpreter" , which defaults to "pythonw" on Windows).
[1] http:// wiki.inkscape. org/wiki/ index.php/ Extension_ Interpreters