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 pitrou
Recipients Arfrever, barry, christian.heimes, eric.snow, larry, pitrou, python-dev, r.david.murray, rhettinger, serhiy.storchaka, vstinner
Date 2014-02-26.20:56:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1393448198.2292.16.camel@fsol>
In-reply-to <>
> > So, it's a very common idiom.
> "Common" doesn't imply "correct" or "supported".  There are plenty of
> other packages/modules who don't import their subpackages/submodules
> during initialization.  Unless explicitly supported by the module,
> using a submodule without explicitly importing it is relying on
> undefined behavior.

Yes, you are technically right. But this is an idealized view of what
backwards compatibility means in the real world.

Well, let's see if people complain after 3.4 is released, anyway.
Date User Action Args
2014-02-26 20:56:41pitrousetrecipients: + pitrou, barry, rhettinger, vstinner, larry, christian.heimes, Arfrever, r.david.murray, python-dev, eric.snow, serhiy.storchaka
2014-02-26 20:56:40pitroulinkissue20784 messages
2014-02-26 20:56:40pitroucreate