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 pje
Recipients Pascal.Chambon, barry, brett.cannon, eric.snow, isoschiz, kristjan.jonsson, methane, ncoghlan, pconnell, pje
Date 2013-12-17.17:34:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1387301694.16.0.889709811297.issue17636@psf.upfronthosting.co.za>
In-reply-to
Content
Unfortunately, this is not quite true: the weird edge cases for that approach are simply *different*, and harder to diagnose.  ;-)

The approach here can only affect execution paths that would currently raise ImportError; that one can break execution paths that are *currently working*.

As Brett said above, "By declaring what the semantics will be to make the case even possible we are not breaking anything but making something possible."  That is not the case for the approach proposed in the other issue.
History
Date User Action Args
2013-12-17 17:34:54pjesetrecipients: + pje, barry, brett.cannon, ncoghlan, kristjan.jonsson, methane, eric.snow, pconnell, isoschiz, Pascal.Chambon
2013-12-17 17:34:54pjesetmessageid: <1387301694.16.0.889709811297.issue17636@psf.upfronthosting.co.za>
2013-12-17 17:34:54pjelinkissue17636 messages
2013-12-17 17:34:53pjecreate