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 brett.cannon
Recipients J Richard Snape, Patrick Maupin, brett.cannon, docs@python, eric.snow, flatsieve, ncoghlan
Date 2015-10-05.16:30:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1444062632.45.0.509504940006.issue25294@psf.upfronthosting.co.za>
In-reply-to
Content
I don't quite follow what you think is wrong with https://hg.python.org/cpython/file/tip/Lib/concurrent/futures/__init__.py . It looks totally fine to me.

And I should mention that you shouldn't follow PEP 8 like it's in stone and the only way to format code. The PEP is a set of guidelines only and not rules (this is a long-standing position of python-dev on PEP 8). For instance, I don't agree with the absolute import recommendation and do not follow it in my own code nor in importlib (it makes vendoring impossible without modifying the import statements).

I think the key thing to take away from this whole discussion is "don't have circular imports" is the key practice to follow. And if someone wants to propose a patch to update some documentation to point out that `from ... import ...` may work in some situations where `import ...; ... = ...` doesn't then I will personally review such a patch.
History
Date User Action Args
2015-10-05 16:30:32brett.cannonsetrecipients: + brett.cannon, ncoghlan, docs@python, eric.snow, Patrick Maupin, flatsieve, J Richard Snape
2015-10-05 16:30:32brett.cannonsetmessageid: <1444062632.45.0.509504940006.issue25294@psf.upfronthosting.co.za>
2015-10-05 16:30:32brett.cannonlinkissue25294 messages
2015-10-05 16:30:32brett.cannoncreate