New submission from R. David Murray <rdmur...@bitdance.com>: During the execution of the load tests protocol, the loader instance will set its _top_level_dir attribute, and this will persist if the loader is passed on to another load_tests method. If that method does not specify a top_level_dir in a discovery call, the wrong top_level_dir may be used, and loading will fail.
You can reproduce this by having two test *packages* with a load_tests method that calls discover in their __init__.py, and specify both package names to the unittest CLI. ---------- components: Library (Lib) keywords: easy messages: 162387 nosy: michael.foord, r.david.murray priority: normal severity: normal stage: needs patch status: open title: unittest: _top_level_dir is incorrectly persisted between calls to different load_test methods type: behavior versions: Python 2.7, Python 3.2, Python 3.3 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue15010> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
