> Documentation: Ok, that'll need to been done. > > Regarding the print statements: most are in ModuleFinder.msg() and > ModuleFinder.report(), and then there are two in > _try_registry(). Apart from the latter, if msg() and reprot() are > not appropriate for an application, they can easily be overridden. > > But: by default, self.debug is set to zero, which means that no > msg's are ever printed. I think the module as is is just fine (apart > perhaps from the _try_registry print statements), it's a meta tool > after all. If you don't agree: how should it be changed > specifically? Ok, make it so! --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