[issue21784] __init__.py can be a directory

Georg Brandl added the comment: I agree, closing. -- nosy: +georg.brandl resolution: -> wont fix status: open -> closed ___ Python tracker ___ __

[issue21784] __init__.py can be a directory

Raymond Hettinger added the comment: > So maybe a check was dropped by mistake? Why do we care? For the most part, Linux treats directories as files (if I do a mkdir twice, the error is "mkdir: tmp: File exists". We don't care about the other flags rwx so why should we care about d? Python

[issue21784] __init__.py can be a directory

Changes by Terry J. Reedy : -- versions: -Python 3.1, Python 3.2, Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue21784] __init__.py can be a directory

STINNER Victor added the comment: I remember that I added an check in Python 3.2 on the file type to explicitly reject directories: http://hg.python.org/cpython/rev/125887a41a6f +if (stat(buf, &statbuf) == 0 && S_ISDIR(statbuf.st_mode)) +/* it's a directory */ +

[issue21784] __init__.py can be a directory

STINNER Victor added the comment: See also the issue #7732. -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue21784] __init__.py can be a directory

abraithwaite added the comment: Interesting. I saw the same behavior on 2.7.7 as well: $ python2 Python 2.7.7 (default, Jun 3 2014, 01:46:20) [GCC 4.9.0 20140521 (prerelease)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from pkg import foobar >>> fooba

[issue21784] __init__.py can be a directory

Berker Peksag added the comment: I think this is related to PEP 420. $ tree pkg/ pkg/ ├── foobar.py $ python3.2 -c "from pkg import foobar" Traceback (most recent call last): File "", line 1, in ImportError: No module named pkg But, with Python 3.3 and newer:

[issue21784] __init__.py can be a directory

Raymond Hettinger added the comment: > Is this expected? It is a little weird but usually problematic. The cause that import checks for the existence of '__init__.py' but doesn't then add isfile() or isdir() check which would be unnecessary 99.9% of the time. I classify this a harmless odd

[issue21784] __init__.py can be a directory

abraithwaite added the comment: > but of course git doesn't track files, only directories. but of course git doesn't track *directories*, only *files*. -- ___ Python tracker ___

[issue21784] __init__.py can be a directory

New submission from abraithwaite: Is this expected? It was very confusing when I cloned a repo that didn't have the __init__.py there when I had just made it, but of course git doesn't track files, only directories. I had accidentaly done mkdir instead of touch. $ mkdir pkg/__init__.py $ tou