I was watching Pablo Galindo Salgados's last talk in #PyConUS and he jokes "... because we like to add all these underscores that are possible, we get more money the more underscores we put in our environment variables..." (he's talking about `PYTHON_PERF_JIT_SUPPORT`; compare to `PYTHONPROFILEIMPORTTIME`) and it hit me:
`PYTHONPROFILEIMPORTTIME` is really not very #acessibility/#a11y friendly, because screen readers can't pronounce it; same reason we tell people to #CamelCase tags.
@mdione Exactly, accessibility for screen readers is one of the reasons for requiring underscores in new env vars, in addition to improving readability for all:
https://discuss.python.org/t/change-environment-variable-style/35180
Here's the resulting policy in the devguide:
https://devguide.python.org/developer-workflow/stdlib/#adding-a-new-environment-variable
#Python #accessibility #a11y
@mdione I asked to add underscores when PYTHONCPUCOUNT was added. I made a typo at the very first usage. The name became PYTHON_CPU_COUNT. Donghee did the hard work on convincing the community: https://discuss.python.org/t/change-environment-variable-style/35180
@hugovk a pity Salgado didn't say just that instead of cracking a joke :-|
