On 2019-07-26 11:10, Anders Hovmöller wrote:
This doesn't really solve the problem imo. Imported symbols shouldn't be i
portable elsewhere. Not by import * or explicitly. That's the problem.
I see a fair number of questions about this on StackOverflow and I just
don't understand why people feel it's a problem. Who cares what names
are accessible in an imported module's namespace? If you do `import
foo` and then `foo.blah` happens to be some oddball name you didn't
expect to be in there, so what? Just don't use it and it doesn't matter.
As for star-import, it should NEVER be used except in cases where the
module you're star-importing explicitly defines an __all__ and documents
that it's okay to star-import it, in which case the issue is moot since
the __all__ will prevent any unexpected names from being imported.
The actual problem is that people use star-importing when they
shouldn't. I don't think there's any need to change the language to
make star imports easier or more convenient; if anything we should be
trying to move away from their use.
--
Brendan Barnwell
"Do not follow where the path may lead. Go, instead, where there is no
path, and leave a trail."
--author unknown
_______________________________________________
Python-ideas mailing list -- python-ideas@python.org
To unsubscribe send an email to python-ideas-le...@python.org
https://mail.python.org/mailman3/lists/python-ideas.python.org/
Message archived at
https://mail.python.org/archives/list/python-ideas@python.org/message/5L32UECKDWZ4JSUGA62GXN2CZQ7NDC6Q/
Code of Conduct: http://python.org/psf/codeofconduct/
