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

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

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

• Previous message: [Python-Dev] Dropping __init__.py requirement for subpackages
• Next message: [Python-Dev] Dropping __init__.py requirement for subpackages
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

* Guido van Rossum 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.

Not that it would count in any way, but I'd prefer to keep it. How would I 
mark a subdirectory as "not-a-package" otherwise?

echo "raise ImportError" >__init__.py

?

nd
-- 
Das, was ich nicht kenne, spielt stückzahlmäßig *keine* Rolle.

                                   -- Helmut Schellong in dclc

• Previous message: [Python-Dev] Dropping __init__.py requirement for subpackages
• Next message: [Python-Dev] Dropping __init__.py requirement for subpackages
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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