Since xml.etree.cElementTree does not exist in Python 3.9, the statement that it's deprecated should be removed from the documentation.

I will clean this

This issue looks like the same with https://bugs.python.org/issue40064

Same core problem (module removed with insufficient document update), but a different action is needed for 3.8 and 3.9.

When I started testing an application with 3.9 and found one of the dependencies broken because it was relying directly on xml.etree.cElementTree, I had to dig into the history to determine that it was removed intentionally.  Updated documentation would have helped.

I did file an issue on the dependency as well:
https://github.com/boto/botocore/issues/2002

Thank you for catching this Fred. I am surprised that some code uses xml.etree.cElementTree without falling back to xml.etree.ElementTree. In Python 3 you can just use xml.etree.ElementTree, in Python 2 you have to fallback to the Python implementation because the C implementation was optional.

The common idiom is

try:
    import xml.etree.cElementTree as ET
except ImportError:
    import xml.etree.ElementTree as ET

The Python 2.7 documentation was not clear that xml.etree.cElementTree was optional, so users who didn't dive into the implementation or build process could easily not have known unless someone with a more limited installation used their code.

For the record, I submitted a fix to the dependent:

https://github.com/boto/botocore/pull/2015

Are you still working on this @Manjusaka?
If not, I would like to submit a patch for it.

Although the modules has been deprecated for a long time, the removal came as surprise. We are currently debating to bring the module back and warn users that it will be removed in 3.10.

I'm working on it. I will make a PR today.

Tal, is there a decision to this debate or can I just move the dep. warning?

AFAICT from following the discussion, the decision is to hold off on a few deprecations which were causing most of the breakage. However, this does not appear to include xml.etree.cElementTree. Since that has currently been removed in the 3.9 branch, we should indeed fix the docs accordingly.

(Note that previous versions' docs, especially 3.8, should also be updated in this regard, as per the other issue Fred opened about this, #40064.)

(Also, please note that the "master" branch is now for version 3.10; PRs for version 3.9 should be based on the "3.9" branch, and the pull request made for that branch too.)

(My mistake! This should be done from/against the master branch, and then back-ported to 3.9, as usual.)

No, please don't change the docs yet. I want to re-introduce the cElementTree and go through a proper deprecation phase.

Ah, thanks for the update Christian, I must have misunderstood your intentions.

So should the deprecation note be removed in the "master" branch for 3.10?

Thanks Tal.

Yes, I also got the impression we want to clean this, sorry Christian.

Please let me know how to follow up on this.

> We are currently debating to bring the module back and warn users that it will be removed in 3.10.


Doesn't look like it was removed in 3.10. Was this an oversight?