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/2002-December/031087.html below:

[Python-Dev] new import hooks & zip import

[Python-Dev] new import hooks & zip import [Python-Dev] new import hooks & zip importSkip Montanaro skip@pobox.com
Thu, 12 Dec 2002 08:40:58 -0600
    Just> Thorough review would be very welcome.

Scanning the patch summary I see:

    sys.path_hooks is a list of callable objects that take 
    a string as their only argument. A hook will be called 
    with a sys.path or pkg.__path__ item. It should return 
    an "importer" object (see below), or raise ImportError 
    or return None if it can't deal with the path item. By 
    default, sys.path_hooks only contains the zipimporter 
    type, if the zipimport module is available. 

Why have it raise ImportError or return None if it can't deal with the path
item?  Shouldn't there be only one way to report failure?  (Or do I misread
your explanation?)

Skip



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