[issue26481] unittest discovery process not working without .py source files

Martin Panter added the comment: Please see Issue 26859; I think it is describing the same problem, and a fix is proposed (although no regression test) -- nosy: +martin.panter resolution: -> duplicate status: open -> closed superseder: -> unittest fails with "Start directory is not

[issue26481] unittest discovery process not working without .py source files

Robert Collins added the comment: Sorry, I missed the little footnote on case 4 about still supporting source-less distributions. I guess in that context we do still need to support this. However - please check that this does indeed happen on Python master - 3.6. unittest does evolve and if

[issue26481] unittest discovery process not working without .py source files

Robert Collins added the comment: Python has stopped supporting .pyc-only distributions - see https://www.python.org/dev/peps/pep-3147/#case-3-pycache-foo-magic-pyc-with-no-source - and so, while what you are seeing is inconsistent with import in some older python's, it is not a bug in newer

[issue26481] unittest discovery process not working without .py source files

Changes by Ned Deily : -- nosy: +ezio.melotti, michael.foord, rbcollins ___ Python tracker ___

[issue26481] unittest discovery process not working without .py source files

New submission from Stefan Seefeld: The unittest test discovery right now only looks into sub-packages if they contain a `__init__.py` file. That's an unnecessary requirement, as packages are also importable if only `__init__.pyc` is present. -- components: Library (Lib) messages: