Tim Peters wrote: > Note that it's very common in older modules (which keyword.py is) to > define the newer __all__ rather than risk breaking code by massive > renaming of variables to stick an underscore in front of them. Fair enough. For a long time I'd gotten used to assuming that the lack of a leading _ was a safe sign of 'publicness' (that's probably not a word :), and didn't really rely too much on __all__. Lesson learned... (I wouldn't be surprised to find I'm not the only one with this bad habit) Thanks, I already committed a patch for my stuff anyway, since there's no point in making my users unhappy. Best regards, f
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