Andrew Kuchling wrote: > > ... > > Could we then simply adopt __exports__ as a convention for such > browsers, but with no changes to core Python to support it? Browsers > would then follow the algorithm "Use __exports__ if present, dir() if > not." dir() is one of the "interactive tools" I'd like to work better in the presence of __exports__. On the other hand, dir() works pretty poorly for object instances today so maybe we need something new anyhow. Perhaps attrs()? If there were an "attrs()" and it basically returned __exports__ if it existed and dir() if it didn't, then I would buy it. Graphical apps would just build on attrs(). Paul
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