Author ncoghlan
Recipients barry, brett.cannon, carljm, eric.snow, lukasz.langa, ncoghlan, rhettinger
Date 2018-05-17.12:14:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1526559244.63.0.682650639539.issue33499@psf.upfronthosting.co.za>
In-reply-to
Content
Regarding environment variables, note that they get used in two *very* different ways:

1. The "persistent shell setting" case that Raymond describes. While setting PYTHONBYTECODEPATH to always point to a RAM disk could make quite a bit of sense for some developers, it's more likely that this case would be associated with tools like `pipenv shell`.

2. The "inheritable process setting" case, where you prepend the environment variable setting to a shell command, or add it to the env dict in a Python subprocess call.

Anywhere that I used this setting, I'd want it to be passed along to child processes, so an environment variable would be a lot more useful than a command line option.

If we did add an option, then a named -X option would probably make the most sense.

Regarding the state caching: having this be read once at startup would help avoid a lot of potential for weird state inconsistencies where some modules were loaded from one cache directory, while later modules were loaded from a different one.
History
Date User Action Args
2018-05-17 12:14:04ncoghlansetrecipients: + ncoghlan, barry, brett.cannon, rhettinger, carljm, lukasz.langa, eric.snow
2018-05-17 12:14:04ncoghlansetmessageid: <1526559244.63.0.682650639539.issue33499@psf.upfronthosting.co.za>
2018-05-17 12:14:04ncoghlanlinkissue33499 messages
2018-05-17 12:14:04ncoghlancreate