Showing content from https://mail.python.org/pipermail/python-dev/2001-January/011688.html below:
[Python-Dev] should we start instrumenting modules with __all__?
[Python-Dev] should we start instrumenting modules with __all__?Skip Montanaro skip@mojam.com (Skip Montanaro)
Mon, 15 Jan 2001 16:10:36 -0600 (CST)
- Previous message: [Python-Dev] Re: [Python-checkins] CVS: python/dist/src/Lib tabnanny.py,1.10,1.11 telnetlib.py,1.8,1.9 tempfile.py,1.26,1.27 threading.py,1.10,1.11 toaiff.py,1.8,1.9 tokenize.py,1.15,1.16 traceback.py,1.18,1.19 tty.py,1.2,1.3 tzparse.py,1.8,1.9
- Next message: [Python-Dev] Strings: '\012' -> '\n'
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I see the from-import-* patch for __all__ has been checked in. Should we
make an effort to add __all__ to at least some modules before 2.1a1?
Skip
- Previous message: [Python-Dev] Re: [Python-checkins] CVS: python/dist/src/Lib tabnanny.py,1.10,1.11 telnetlib.py,1.8,1.9 tempfile.py,1.26,1.27 threading.py,1.10,1.11 toaiff.py,1.8,1.9 tokenize.py,1.15,1.16 traceback.py,1.18,1.19 tty.py,1.2,1.3 tzparse.py,1.8,1.9
- Next message: [Python-Dev] Strings: '\012' -> '\n'
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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