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.

Author vinay.sajip
Recipients donovick, vinay.sajip
Date 2019-06-20.17:58:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1561053511.33.0.31513784709.issue37349@roundup.psfhosted.org>
In-reply-to
Content
> Common python libraries that make use of environmental variables

I didn't say environment variables weren't commonly used. I'm talking about the specific functionality this issue is about.

> Overriding setup scripts is hardly a trivial task. One has to completely recreate the activate script to achieve the desired behavior.

Not trivial, but not overly onerous either, e.g. just point to your own scripts subtree in the overridden method. Isn't your proposal to submit a different activate script?

> the functionality I am requesting already exists across all shells

I'm talking about the code to set, reset your custom environment variables - where is that already existent across all shells?

I'm not saying what you want is unreasonable - it's just putting it into the stdlib this way that I'm not sure about.
History
Date User Action Args
2019-06-20 17:58:31vinay.sajipsetrecipients: + vinay.sajip, donovick
2019-06-20 17:58:31vinay.sajipsetmessageid: <1561053511.33.0.31513784709.issue37349@roundup.psfhosted.org>
2019-06-20 17:58:31vinay.sajiplinkissue37349 messages
2019-06-20 17:58:31vinay.sajipcreate