[issue12314] regrtest checks (os.environ, sys.path, etc.) are hard to use

Changes by STINNER Victor : -- resolution: -> out of date status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing

[issue12314] regrtest checks (os.environ, sys.path, etc.) are hard to use

Mark Lawrence added the comment: @Éric do you intend following up on this? -- nosy: +BreamoreBoy ___ Python tracker ___ ___ Python-bug

[issue12314] regrtest checks (os.environ, sys.path, etc.) are hard to use

Éric Araujo added the comment: Idea: when a regrtest check fails, the test is run again but a WatchfulMixin is injected into the test case’s bases, so that setUp and tearDown call the right methods. This would be more efficient than always running with a watchful test runner. -- __

[issue12314] regrtest checks (os.environ, sys.path, etc.) are hard to use

Roundup Robot added the comment: New changeset 9c61f46ea6b4 by Éric Araujo in branch 'default': Make regrtest look at internal dicts in sysconfig. http://hg.python.org/cpython/rev/9c61f46ea6b4 -- nosy: +python-dev ___ Python tracker

[issue12314] regrtest checks (os.environ, sys.path, etc.) are hard to use

STINNER Victor added the comment: > I’d like regrtest to tell me what exactly was changed, and where. regrtests has many tests (you give some examples: os.environ, sys.path), run all tests after calling a single test function would make regrtest slower. We can add an option (e.g. --strict?) t

[issue12314] regrtest checks (os.environ, sys.path, etc.) are hard to use

R. David Murray added the comment: Sounds like a plan. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue12314] regrtest checks (os.environ, sys.path, etc.) are hard to use

Michael Foord added the comment: I don't think this is something that belongs in unittest - it's not something particularly useful (or at least particularly requested) outside of the python test suite. No reason that a WatchfulTestRunner couldn't live in regrtest. --

[issue12314] regrtest checks (os.environ, sys.path, etc.) are hard to use

Éric Araujo added the comment: > maybe there's some way to reuse unittest's assertEqual machinery? Hum, I think the diff functionality is cleanly separated in a (private) method, so we could get diff for free. > I also wonder if the whole environment-changed thing should be moved > into unitte

[issue12314] regrtest checks (os.environ, sys.path, etc.) are hard to use

Changes by R. David Murray : -- stage: -> needs patch type: -> feature request ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue12314] regrtest checks (os.environ, sys.path, etc.) are hard to use

R. David Murray added the comment: Improvements are welcome, the whole thing was a QnD hack that has been evolving over time...maybe there's some way to reuse unittest's assertEqual machinery? I also wonder if the whole environment-changed thing should be moved into unittest so it could wrap

[issue12314] regrtest checks (os.environ, sys.path, etc.) are hard to use

New submission from Éric Araujo : When regrtest tells me that os.environ was modified by test_packaging, it’s very hard to find which test is responsible. The -vv output is hard to read: it prints four dictionaries, which I have to visually delineate, copy, paste, pretty-print and diff to fin