INADA Naoki added the comment: namespace package is very advanced topic. I don't think tutorial should mention it. Putting __init__.py always in normal package is highly recommended. Otherwise, many tools can't distinguish normal directory and python package.
2017/03/04 午前6:26 "James O" <rep...@bugs.python.org>: New submission from James O: PEP 420 says "Allowing implicit namespace packages means that the requirement to provide an __init__.py file can be dropped completely..." (as described here: http://stackoverflow.com/questions/37139786/is-init-py- not-required-for-packages-in-python-3) The documentation for modules <https://docs.python.org/3/ tutorial/modules.html> doesn't seem to reflect this change. My "enhancement suggestion" is that a sentence (and perhaps an example) be added that explicitly states or shows an import from another directory. (P.S. This is my first Python bug submission, so if it's silly, let me know. Thanks!) ---------- assignee: docs@python components: Documentation messages: 288932 nosy: James O, docs@python priority: normal severity: normal status: open title: Python 3 Module doc still sounds like __init__.py is required type: enhancement versions: Python 3.3, Python 3.4, Python 3.5, Python 3.6, Python 3.7 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29716> _______________________________________ _______________________________________________ docs mailing list d...@python.org https://mail.python.org/mailman/listinfo/docs ---------- nosy: +inada.naoki _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue29716> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
