provide a way to access the unmodified environment (variables) of a Python script

未关闭

#93,446 创建于 2022年6月3日 0 条评论 0 个 reaction 已指派 0 人在 GitHub 查看

还没有人认领这个 Issue。

评估

难度: 5/5
预计耗时: 一周以上
新手友好度: 25/100

Issue 类型: 功能
描述清晰度: 需要澄清
活跃度: 停滞
技术栈: python
领域: operating-systems

调研方向

未指定实现文件或测试。首先查看 PEP 538 以及 issue 72367 中链接的讨论，以了解环境变更和提议的 API；当具体设计及相应的覆盖率达成一致时，工作即告完成。

由索引模型根据 Issue 内容生成。

描述

interpreter-core type-feature

Feature or enhancement

As described in https://github.com/python/cpython/issues/72367#issuecomment-1140355246 and the following comments, the implementation of PEP 538 makes it impossible to access the original unmodified environment (variables) with which a process have been invoked.

I have no problem with the goal of PEP 538 itself or the locale coercion, but this is a problem for any use-case the wants to act on the original locale.

Using PYTHONCOERCECLOCALE=0 is no solution either, as then this modifies the original locale and one couldn't decide whether it's just there to prevent Python's setting of LC_CTYPE=C or whether it was really intended to be in the environment suo jure.

Neither is it obviously a solution to use build-time options.

A solution could be to add another os.original_environment or something like that, which gives the true original environment, without any changes that Python itself may have made.

If Python would ever only modify (by itself) the environment with respect to LC_CTYPE and locale coercion, it could also be enough to simply give the program a way to find out whether that was done, and what the original value (or unset) of LC_CTYPE was.

Pitch

Example use cases are given in the previous discussion mentioned below.

In short, pretty much anything that is intended to serve as a wrapper could require the true original environment.
Imagine one would want to implement the POSIX env utility in Python.

Previous discussion

See https://github.com/python/cpython/issues/72367#issuecomment-1140355246 .