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/2007-April/072719.html below:

[Python-Dev] Clarifications for import PEPs (302 and 328)

[Python-Dev] Clarifications for import PEPs (302 and 328) [Python-Dev] Clarifications for import PEPs (302 and 328)Paul Moore p.f.moore at gmail.com
Tue Apr 24 10:24:50 CEST 2007
On 24/04/07, Brett Cannon <brett at python.org> wrote:
> Not if you read the PEP.  It doesn't explicitly say what should happen.
>
> I want to standardize on raising ImportError.  The PEP itself has two
> ways of signaling an error; find_module() returns None instead of
> raising an error to signal it can't do something while path hooks
> raise ImportError.  I just want to be as explicit as possible.

I'm happy with that. As far as I remember, that was the original
intention - and you're right, it should be made explicit.

Paul.
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