CEnvironmentVariableTests and PyEnvironmentVariableTests test the same implementation

[serhiy-storchaka]

BPO	23028
Nosy	@serhiy-storchaka

^{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 = None
created_at = <Date 2014-12-10.21:58:49.161>
labels = ['type-bug', 'tests']
title = 'CEnvironmentVariableTests and PyEnvironmentVariableTests test the same implementation'
updated_at = <Date 2014-12-10.21:58:49.161>
user = 'https://github.com/serhiy-storchaka'

bugs.python.org fields:

activity = <Date 2014-12-10.21:58:49.161>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Tests']
creation = <Date 2014-12-10.21:58:49.161>
creator = 'serhiy.storchaka'
dependencies = []
files = []
hgrepos = []
issue_num = 23028
keywords = []
message_count = 1.0
messages = ['232447']
nosy_count = 1.0
nosy_names = ['serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue23028'
versions = ['Python 2.7', 'Python 3.4', 'Python 3.5']

Linked PRs

• gh-67217: Test both warnings implementations in environment variable tests #155234

[serhiy-storchaka]

CEnvironmentVariableTests and PyEnvironmentVariableTests are purposed to test C and Python implementations. But they are test the same implementation because execute test code in a subprocess and changes of sys.modules in current process don't affect a subprocess.

[devdanzin]

The rationale makes sense and it seems to still be the case in main (3.15).