➜

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 hroncok
Recipients Ben Lewis2, brett.cannon, eric.snow, hroncok, miss-islington, ncoghlan, rhettinger, serhiy.storchaka
Date 2020-01-21.12:01:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1579608073.2.0.728054996681.issue37444@roundup.psfhosted.org>
In-reply-to
Content 
While raising ImportError certainly makes much more sense in this case, this change is backwards incompatible and there was no DeprecationWarning. I don't consider that fair.

As a certain compromise, we could maybe raise a custom ImportError+ValueError offspring (e.g. BeyondToplevelImportError)?

If feeling fancy, we could rise a DeprecationWarning when issublcass(BeyondToplevelImportError, ValueError) is used?
History
Date User Action Args
2020-01-21 12:01:13hroncoksetrecipients: + hroncok, brett.cannon, rhettinger, ncoghlan, eric.snow, serhiy.storchaka, miss-islington, Ben Lewis2
2020-01-21 12:01:13hroncoksetmessageid: <1579608073.2.0.728054996681.issue37444@roundup.psfhosted.org>
2020-01-21 12:01:13hroncoklinkissue37444 messages
2020-01-21 12:01:13hroncokcreate