Message312930
I'm trying to understand why ModuleNotFoundError was added to 3.6. The "what's new" entry links to this page.
Looking at the discussion, Guido said in 2013: "Right. Outside importlib there shouldn't be a need to distinguish between the cases (especially given that the exception works differently than its name suggests).". Then, three years later, he supports the inclusion of the patch, without that any new arguments had been given.
Could someone explain (or link to) what happened inbetween? |
|
Date |
User |
Action |
Args |
2018-02-26 15:14:24 | cwg | set | recipients:
+ cwg, gvanrossum, barry, brett.cannon, theller, jcea, pitrou, ezio.melotti, Arfrever, cvrebert, asvetlov, chris.jerdonek, python-dev, eric.snow, serhiy.storchaka, Guido.van.Rossum |
2018-02-26 15:14:24 | cwg | set | messageid: <1519658064.19.0.467229070634.issue15767@psf.upfronthosting.co.za> |
2018-02-26 15:14:24 | cwg | link | issue15767 messages |
2018-02-26 15:14:24 | cwg | create | |
|