[Import-SIG] PEP 420 issue: extend_path

[martin at v.loewis.de]

>> I'm not sure why we *need* a list of portions, but if we do, simple
>> return values seem like the way to go.  But the 2-element tuple wins
>> even in the single path portion case, and the tuple-return protoocol is
>> extensible if we need more data returned in future anyway.
>
> Nick laid out a use case in a previous email. It makes sense to me. For
> example, a zip file could contain multiple portions from the same
> namespace package. You'd need a new path hook or mods to zipimport, but
> it's conceivable.

I must have missed Nick's message where he explained it, so I still need
to ask again: how exactly would such a zip file be structured?

I fail to see the need to ever report both a loader and a portion,
as well as the need to report multiple portions, for a single sys.path
item. That sounds like an unnecessary complication.

Regards,
Martin