You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Python defines a number of environment variables which we currently ignore. This is a placeholder issue for any tests failing because of this.
My initial thought is that ignoring the environment variables is probably fine when embedding in .NET but that we should probably handle the ones that make sense when running ipy.
We currently handle some of the variables with a prefix "IRON" (e.g. IRONPYTHONPATH) where it makes sense, but it's probably not necessary to have a prefix all the time (e.g. PYTHONVERBOSE).
Specific examples which I've run into recently:
PYTHONVERBOSE: this is ignored even though it's listed in the cli help (I'll file a PR to remove it from the help).
PYTHONUTF8: I'm currently adding utf8 mode (new in 3.7) which can be enabled via a cli argument or an option, however I will probably not add support for the environment variable in the initial implementation.
PYTHONIOENCODING: not implemented...
The text was updated successfully, but these errors were encountered:
Python defines a number of environment variables which we currently ignore. This is a placeholder issue for any tests failing because of this.
My initial thought is that ignoring the environment variables is probably fine when embedding in .NET but that we should probably handle the ones that make sense when running
ipy
.We currently handle some of the variables with a prefix "IRON" (e.g. IRONPYTHONPATH) where it makes sense, but it's probably not necessary to have a prefix all the time (e.g. PYTHONVERBOSE).
Specific examples which I've run into recently:
The text was updated successfully, but these errors were encountered: