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 ncoghlan
Recipients J Richard Snape, Patrick Maupin, brett.cannon, docs@python, eric.snow, flatsieve, ncoghlan
Date 2015-10-03.12:54:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1443876878.67.0.147066133898.issue25294@psf.upfronthosting.co.za>
In-reply-to
Content
Issue 992389 is the previous incarnation of this bug report, while issue 17636 made the change so that from imports will resolve in some situations where this error will occur.

That fact that "from x.y.b import foo" may now resolve in cases where "import x.y.b; foo = x.y.b.foo" will fail should indeed be covered in the documentation.

If PEP 8 were to be updated at all, it should just say "Don't use circular imports. If you can't refactor your design to move the common components out to a shared helper module, then move everything into the same module - the irremovable circular dependency indicates the code is too tightly coupled to live in different modules".
History
Date User Action Args
2015-10-03 12:54:38ncoghlansetrecipients: + ncoghlan, brett.cannon, docs@python, eric.snow, Patrick Maupin, flatsieve, J Richard Snape
2015-10-03 12:54:38ncoghlansetmessageid: <1443876878.67.0.147066133898.issue25294@psf.upfronthosting.co.za>
2015-10-03 12:54:38ncoghlanlinkissue25294 messages
2015-10-03 12:54:37ncoghlancreate