Message368105
Christian, I understand your complaint, but I've actually never seen code in the wild that didn't provide a fallback for the import, usually something like what Serhiy spelled out and explained above:
try:
import xml.etree.cElementTree as ET
except ImportError:
import xml.etree.ElementTree as ET
This makes it inconvenient for users to emit a deprecation warning for the import, because it would impact perfectly future proof code like the above, without a good way for users to work around it by adapting their code, because the above import order is actually what they want. And there's a lot of such code.
I personally believe that the breakage will be quite limited. But that's a belief, not a fact. I don't have numbers to back it. |
|
Date |
User |
Action |
Args |
2020-05-05 05:55:13 | scoder | set | recipients:
+ scoder, christian.heimes, eli.bendersky, serhiy.storchaka, hroncok, rahul-kumi |
2020-05-05 05:55:13 | scoder | set | messageid: <1588658113.34.0.9737605411.issue36543@roundup.psfhosted.org> |
2020-05-05 05:55:13 | scoder | link | issue36543 messages |
2020-05-05 05:55:13 | scoder | create | |
|