Barry Warsaw wrote: > Good enough reason for me, although my one (minor) concern is the > consumption of that name in the top-level package namespace for > something that isn't Python code. Indeed. If you can propose a different location in the source tree, and in the installed tree (for both Windows and Unix), I could do that as well. > That makes me feel better about dropping it in Lib, even if the use case > is a little questionable. I'm uncomfortable about having things other > than packages or modules in that namespace. There are already a lot of lib- directories, which aren't package names. If a different directory name would make you feel more comfortable, please suggest one. I had precisely the same concerns myself, that's why I asked. Regards, Martin
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