[Greg]
> > > hehe... adding __exports__ to your module is fine. Adding more crud to
> > > Python, in opposition to the "we're all adults" motto, doesn't seem Right.
> > >
> > > Somebody wants to use "from foo import *" on a module not designed for it?
> > > Too bad for them. If you're suggesting __exports__ is to patch over problems
> > > caused by "from foo import *", then I think you're barking up the wrong tree
> > > :-)
[Guido]
> > You haven't been answering many newbie questions lately, have you? :-)
[Moshe]
> Well, I have.
> And frankly, I think having "from foo import *" issue a warning at 2.1
> a *much* better solution.
(1) For what problem?
(2) Under exactly what circumstances do you want from foo import *
issue a warning?
--Guido van Rossum (home page: http://www.python.org/~guido/)
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