No regression tests for -E and individual environment vars

[ncoghlan]

BPO	16961
Nosy	@ncoghlan, @vstinner

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2019-05-15.02:02:13.365>
created_at = <Date 2013-01-14.12:03:14.086>
labels = []
title = 'No regression tests for -E and individual environment vars'
updated_at = <Date 2019-05-15.02:02:13.357>
user = 'https://github.com/ncoghlan'

bugs.python.org fields:

activity = <Date 2019-05-15.02:02:13.357>
actor = 'vstinner'
assignee = 'none'
closed = True
closed_date = <Date 2019-05-15.02:02:13.365>
closer = 'vstinner'
components = []
creation = <Date 2013-01-14.12:03:14.086>
creator = 'ncoghlan'
dependencies = []
files = []
hgrepos = []
issue_num = 16961
keywords = []
message_count = 5.0
messages = ['179934', '223221', '338072', '339193', '342528']
nosy_count = 3.0
nosy_names = ['ncoghlan', 'vstinner', 'SilentGhost']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue16961'
versions = ['Python 3.4', 'Python 3.5']

[ncoghlan]

Accessing an environment variable without Py_GETENV (or breaking Py_IgnoreEnvironmentFlag configuration *cough*) may lead to environment variables being accessed even if -E is passed on the command line.

As part of the PEP-432 implementation, I'm adding appropriate regression tests for affected environment variables as I go.

Creating this as a reminder to look into backporting the relevant regression tests at least to 3.3

[BreamoreBoy]

Consider yourself reminded :)

[SilentGhost]

Nick, please re-open if you feel this issue is still relevant.

[ncoghlan]

Victor Stinner added a great many regression tests in this area for Python 3.7+

[vstinner]

I added a lot of tests on environment variables and -I/-E options in test_embed. I consider that this issue is now fixed.