[issue26859] unittest fails with "Start directory is not importable" when trying to run sourceless tests

Change by Xavier de Gaye : -- nosy: -xdegaye ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.py

[issue26859] unittest fails with "Start directory is not importable" when trying to run sourceless tests

Changes by Xavier de Gaye : -- stage: test needed -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe

[issue26859] unittest fails with "Start directory is not importable" when trying to run sourceless tests

Xavier de Gaye added the comment: > the list_dir() nested function is never called Verifying that load_tests is called is the purpose of this test. In this case should_recurse is false in _find_tests() and os.listdir() is not invoked by this method. This new patch does not use vfs and list_dir

[issue26859] unittest fails with "Start directory is not importable" when trying to run sourceless tests

Xavier de Gaye added the comment: Thanks for the review Pamela, indeed self.vfs is not defined. The patched test_unittest runs without failure because the list_dir() nested function is never called. It is also never called in the un-patched version. Actually the un-patched test_discover_start

[issue26859] unittest fails with "Start directory is not importable" when trying to run sourceless tests

Changes by Pam McA'Nulty : -- nosy: +Pam.McANulty ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue26859] unittest fails with "Start directory is not importable" when trying to run sourceless tests

Changes by ppperry : -- title: unittest fails with "Start directory is not importable" -> unittest fails with "Start directory is not importable" when trying to run sourceless tests ___ Python tracker ___

[issue26859] unittest fails with "Start directory is not importable"

Xavier de Gaye added the comment: Here is the patch with a test case. I have checked that the new test case fails with 'Start directory is not importable"' when loader.py is not patched. -- Added file: http://bugs.python.org/file42646/unittest_2.patch __

[issue26859] unittest fails with "Start directory is not importable"

Robert Collins added the comment: Could you please add a test case. -- nosy: +rbcollins stage: patch review -> test needed ___ Python tracker ___

[issue26859] unittest fails with "Start directory is not importable"

Xavier de Gaye added the comment: It seems to be the same bug. Source-less distributions are useful on mobile devices where space is sparse. -- ___ Python tracker ___ __

[issue26859] unittest fails with "Start directory is not importable"

Martin Panter added the comment: Is this the same bug as Issue 26481? I.e. is it the unittest dicovery mode that is affected? Maybe close the other bug as a duplicate, since Xavier has provided a patch here. -- components: +Tests nosy: +martin.panter stage: -> patch review __

[issue26859] unittest fails with "Start directory is not importable"

Changes by Roman Evstifeev : -- nosy: +Roman.Evstifeev ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue26859] unittest fails with "Start directory is not importable"

New submission from Xavier de Gaye: unittest fails to load tests when the tests are in a package that has an __init__.pyc file and no __init__.py file. Patch attached. -- components: Library (Lib) files: unittest.patch keywords: patch messages: 264283 nosy: xdegaye priority: normal sev