This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author cool-RR
Recipients cool-RR
Date 2011-07-18.20:45:32
SpamBayes Score 6.248586e-06
Marked as misclassified No
Message-id <1311021933.2.0.965547827718.issue12583@psf.upfronthosting.co.za>
In-reply-to
Content
I've been frustrated so many times by `ImportError: cannot import name foo`. Right now I'm debugging some problem on a PAAS server (with no SSH access), and the server returns a traceback of `cannot import name foo`, and I don't have any idea what it means. It could mean that the file isn't there. It could mean that there's a circular import problem. Sometimes it happens when you go over Windows XP's path length limit!

Please provide a useful explanation, like this:

    ImportError: Cannot import `foo` because no file foo.py* or folder foo exists.
    ImportError: Cannot import foo module because no __init__.py* file exists in the foo folder.
    ImportError: Cannot import foo because of a circular import problem with bar.
    ImportError: Cannot import foo because the foo module file's path is bigger than Windows XP's path length limit.

Etcetera for any other reason that might cause an `ImportError`.
History
Date User Action Args
2011-07-18 20:45:33cool-RRsetrecipients: + cool-RR
2011-07-18 20:45:33cool-RRsetmessageid: <1311021933.2.0.965547827718.issue12583@psf.upfronthosting.co.za>
2011-07-18 20:45:32cool-RRlinkissue12583 messages
2011-07-18 20:45:32cool-RRcreate