This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2022年02月26日 03:44 by benrg, last changed 2022年04月11日 14:59 by admin. This issue is now closed.
| Messages (1) | |||
|---|---|---|---|
| msg414064 - (view) | Author: (benrg) | Date: 2022年02月26日 03:44 | |
The Windows functions that deal with environment variables are case-insensitive and case-preserving, like most Windows file systems. Many environment variables are conventionally written in all caps, but others aren't, such as `ProgramData`, `PSModulePath`, and `windows_tracing_logfile`. os.environ forces all environment variable names to upper case when it's constructed. One consequence is that if you pass a modified environment to subprocess.Popen, you end up with variables named `PROGRAMDATA`, etc., even if you didn't modify their values. While this is unlikely to break things since other software normally ignores the case, it's nonstandard behavior, and disconcerting when the affected variable names are shown to human beings. Here's an example of someone being confused by this: https://stackoverflow.com/questions/19023238/why-python-uppercases-all-environment-variables-in-windows |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022年04月11日 14:59:56 | admin | set | github: 91017 |
| 2022年02月26日 07:16:55 | eryksun | set | status: open -> closed superseder: os.environ should preserve the case of the OS keys ? resolution: duplicate stage: resolved |
| 2022年02月26日 03:44:08 | benrg | create | |