[issue3170] test_pydoc has no way to regenerate pristine data

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue3170] test_pydoc has no way to regenerate pristine data

Mark Lawrence added the comment: Is this still an issue? I'd try to reproduce it myself but there is very little data in the original report. -- nosy: +BreamoreBoy versions: +Python 3.4, Python 3.5 -Python 3.0 ___ Python tracker

[issue3170] test_pydoc has no way to regenerate pristine data

Changes by Brett Cannon br...@python.org: -- nosy: -brett.cannon ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3170 ___ ___ Python-bugs-list

[issue3170] test_pydoc has no way to regenerate pristine data

Georg Brandl ge...@python.org added the comment: Ping? -- nosy: +georg.brandl ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3170 ___ ___

[issue3170] test_pydoc has no way to regenerate pristine data

Changes by Éric Araujo mer...@netwok.org: -- nosy: +eric.araujo ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3170 ___ ___ Python-bugs-list

[issue3170] test_pydoc has no way to regenerate pristine data

Benjamin Peterson [EMAIL PROTECTED] added the comment: 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. ___ Python tracker [EMAIL PROTECTED]

[issue3170] test_pydoc has no way to regenerate pristine data

New submission from Brett Cannon [EMAIL PROTECTED]: 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