Python modules without __init__.py failed to be parsed since 2.5.0

[nicocti]

Pylint 2.5 fails to parse modules without init.py while 2.4.4 works fine.
I found nothing in the changelog regarding this, so I guess it's a bug.

Steps to reproduce

1. create a python module without init.py
2. run pylint --disable=C,R ${MODULE_NAME}

Current behavior

raises:

************* Module ${MODULE_NAME}
${MODULE_NAME}/__init__.py:1:0: F0010: error while code parsing: Unable to load file ${MODULE_NAME}/__init__.py:
[Errno 2] No such file or directory: '${MODULE_NAME}/__init__.py' (parse-error)

Expected behavior

No error expected since init.py are optional since python 3.4+

pylint --version output

pylint==2.5.0
python==3.6.10

[Pierre-Sassoulas]

I saw that but thought this was "normal" and the same than #352

[Pierre-Sassoulas]

I've done a git bisect on this. Seem like the culprit is a6d7ffc. I guess we don't want to revert it entirely? What do you think @PCManticore ?

[PCManticore]

@Pierre-Sassoulas This is the exact same thing as #352. pylint never managed to analyze directories without __init__.py files.

I was able to reproduce it with the following version as well, which does not have the changes in the linked commit:

pylint 2.4.4
astroid 2.3.3
Python 3.8.1 (default, Feb 13 2020, 10:17:07)
[Clang 8.1.0 (clang-802.0.42)]

@nicocti Until we have a fix for #352, you'll need to either have a __init__.py in the directory that you are passing to pylint as an argument or you need to rely on shell expansion as in running pylint with pylint your_module/*.

[Pierre-Sassoulas]

Strange, I tested by creating a directory called module with a test.py inside it and no init.py. Then, the test was:

pip3 install .;python3 pylint/__main__.py module

This was clearly working for 2.4.4 and until the commit which I linked, or am I missing something?

[PCManticore]

No, you're right, for some reason my testing resulted in the same results on both versions.