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 2014-02-02.19:04:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
If there's a circular import in my program, I don't want to see an error message, "Cannot import name 'foo'" and then say in my mind, "ah, I'm an experienced Python developer, I know that when Python says that it often means that there's a circular import problem." I want the error message to **say there's a circular import problem**, so (a) I won't have to remember this piece of trivia and (b) less experienced developers won't have to bang their heads on their desks trying to figure out why the import isn't working. 

Bonus points if the error message actually shows which module is trying to import a module that imports itself, so we'll know where to fix.
Date User Action Args
2014-02-02 19:04:48cool-RRsetrecipients: + cool-RR
2014-02-02 19:04:48cool-RRsetmessageid: <>
2014-02-02 19:04:48cool-RRlinkissue20490 messages
2014-02-02 19:04:48cool-RRcreate