A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2006-April/064428.html below:

[Python-Dev] Dropping __init__.py requirement for subpackages

[Python-Dev] Dropping __init__.py requirement for subpackages [Python-Dev] Dropping __init__.py requirement for subpackagesWolfgang Langner tds333+pydev at gmail.com
Wed Apr 26 21:57:45 CEST 2006
On 4/26/06, Guido van Rossum <guido at python.org> wrote:

> So I have a very simple proposal: keep the __init__.py requirement for
> top-level pacakages, but drop it for subpackages. This should be a
> small change. I'm hesitant to propose *anything* new for Python 2.5,
> so I'm proposing it for 2.6; if Neal and Anthony think this would be
> okay to add to 2.5, they can do so.

-1 from me.

I had never a problem with __init__.py to mark a package or subpackage.
Better add __namespace__.py to state a package dir as namespace package.
And support multiple occurrences of "on_python_path/namespace_name/package".

--
bye by Wolfgang
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4