[Import-SIG] PEP 420 issue: extend_path

[martin at v.loewis.de]

>> 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'll work on such an example. But I think Nick's example of a config
> file that has the configuration for multiple portions of a single
> namespace package is more compelling. I don't see where returning a list
> for the common case of a single portion is a large burden.

Unfortunately, I still can't locate the message where he explains the
example. This sounds like a bit like .pth files, where the file contains
the list of locations to be added to the path. It was supported in an
early version of PEP 382, when the community declared YAGNI.

> As Nick said, you'd return a loader, a list of portions, or neither. it
> would be an error to return both.

Ah, ok. This is fine, then (except that I still think that returning multiple
portions needs to be supported).

Regards,
Martin