test_pydoc has no way to regenerate pristine data

[brettcannon]

BPO	3170
Nosy	@birkenfeld, @benjaminp, @merwok

^{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 = 'https://github.com/benjaminp'
closed_at = None
created_at = <Date 2008-06-22.03:47:06.310>
labels = ['type-bug', 'tests']
title = 'test_pydoc has no way to regenerate pristine data'
updated_at = <Date 2019-03-16.00:06:00.099>
user = 'https://github.com/brettcannon'

bugs.python.org fields:

activity = <Date 2019-03-16.00:06:00.099>
actor = 'BreamoreBoy'
assignee = 'benjamin.peterson'
closed = False
closed_date = None
closer = None
components = ['Tests']
creation = <Date 2008-06-22.03:47:06.310>
creator = 'brett.cannon'
dependencies = []
files = []
hgrepos = []
issue_num = 3170
keywords = []
message_count = 4.0
messages = ['68556', '68649', '114595', '221852']
nosy_count = 3.0
nosy_names = ['georg.brandl', 'benjamin.peterson', 'eric.araujo']
pr_nums = []
priority = 'low'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue3170'
versions = ['Python 3.4', 'Python 3.5']

[brettcannon]

test_pydoc relies on pristine data to verify that the tests pass.
Unfortunately there is no automated way to regenerate that pristine
data, making the test easily fail if something global (e.g., __loader__
attributes on all modules) is introduced.

This was seen on Python 3.0 but might also be an issue in 2.6.

[benjaminp]

Actually, I was wondering if the comparison testing is even worthwhile.
All it's really going to tell is if something has changed, not if it's
broken.

[birkenfeld]

Ping?

[BreamoreBoy]

Is this still an issue? I'd try to reproduce it myself but there is very little data in the original report.

[iritkatriel]

Closing because I doubt anyone remembers now what this was about.