[issue40203] Warn about invalid PYTHONUSERBASE

Volker Weißmann added the comment: "there is no good reason to do so" meant that there is no good reason to set PYTHONUSERBASE to non existing path or a path that is not a directory. The history behind this bug report is that I used a program that, because of a bug in this program, set PYTHON

[issue40203] Warn about invalid PYTHONUSERBASE

Terry J. Reedy added the comment: I marked this for 'interpreter Core' because it affects imports and nothing else seemed better. I marked this for 3.9 because it is too late to change 2.7. But I don't know whether PYTHONUSERBASE is still treated (or not treated) the same. Volker, I assume

[issue40203] Warn about invalid PYTHONUSERBASE

Volker Weißmann added the comment: Forget the thing I said about "invalid//path", but my argument still stands for non existing paths or paths to something else than a directory. -- ___ Python tracker __

[issue40203] Warn about invalid PYTHONUSERBASE

New submission from Volker Weißmann : https://docs.python.org/2/using/cmdline.html says that PYTHONUSERBASE defines the user base directory. If I understand this correctly, this implies that PYTHONUSERBASE should be a path a directory. I therefore think that python should print a warning if PY