Message 333200 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	barry
Recipients	barry, brett.cannon, eric.smith, ronaldoussoren
Date	2019-01-08.01:59:55
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to	<[email protected]>

Content
On Jan 7, 2019, at 03:16, Ronald Oussoren <[email protected]> wrote: > > Do you know why the namespace package loader lies about the source and code? Both .get_source() and .get_code() return a value that isn't None. > And likewise: Why is the namespace package loader a private class, other loaders are exposed in importlib.machinery? This makes it hard to detect PEP420 style namespace packages without relying on private APIs, esp. combined with the behaviour of .get_source() and .get_code(). I don’t remember the history of this. I wonder if Brett or Eric have any additional insights.

On Jan 7, 2019, at 03:16, Ronald Oussoren <[email protected]> wrote:
> 
> Do you know why the namespace package loader lies about the source and code? Both .get_source() and .get_code() return a value that isn't None.

> And likewise: Why is the namespace package loader a private class, other loaders are exposed in importlib.machinery?  This makes it hard to detect PEP420 style namespace packages without relying on private APIs, esp. combined with the behaviour of .get_source() and .get_code().

I don’t remember the history of this.  I wonder if Brett or Eric have any additional insights.

History
Date	User	Action	Args
2019-01-08 01:59:56	barry	set	recipients: + barry, brett.cannon, ronaldoussoren, eric.smith
2019-01-08 01:59:55	barry	link	issue35673 messages
2019-01-08 01:59:55	barry	create