> My specific issue is with get_data, which is totally unneeded > for the import protocol itself (although it does solve real, > related issues). I don't think it should be a requirement of > the import hook API. Documenting it as an optional interface > which hooks may choose to support may be reasonable, though. I like get_data(). The caller should always be prepared for it to return an error (how does it do that? raise what? or return None? that should be specified!). An importer that can't do this should implement a version that always reports an error. This is much easier on the client than calling hasattr(importer, 'get_data') first or catching AttributeError. --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