Joe Smith wrote: > It seems to me that the right way to fix this is to simply make a small > change to the error message. > On a failed import, have the code check if there is a directory that would > have been the requested package if > it had contained an __init__ module. If there is then append a message like > "You might be missing an __init__.py file". +1. It's not that putting an __init__.py file in is hard, it's that people have a hard time realizing when they've forgotten to do it. -- Ian Bicking / ianb at colorstudy.com / http://blog.ianbicking.org
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