Message 302167 - Python tracker

➜

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	poojariravi
Recipients	eli.bendersky, poojariravi, scoder, serhiy.storchaka
Date	2017-09-14.11:32:54
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1505388775.09.0.221868509513.issue31467@psf.upfronthosting.co.za>
In-reply-to

Content
Just now I have figured out that , in the documentation it was mentioned that cElementTree module is deprecated in Python 3.3 version. "The xml.etree.ElementTree module implements a simple and efficient API for parsing and creating XML data. Changed in version 3.3: This module will use a fast implementation whenever available. The xml.etree.cElementTree module is deprecated." https://docs.python.org/3/library/xml.etree.elementtree.html In that case, will your resolution comment still holds valid ?? If so then, how to use cElementTree in my usecase

Just now I have figured out that , in the documentation it was mentioned that cElementTree module is deprecated in Python 3.3 version. 

"The xml.etree.ElementTree module implements a simple and efficient API for parsing and creating XML data.

Changed in version 3.3: This module will use a fast implementation whenever available. The xml.etree.cElementTree module is deprecated."

https://docs.python.org/3/library/xml.etree.elementtree.html


In that case, will your resolution comment still holds valid ??
If so then, how to use cElementTree in my usecase

History
Date	User	Action	Args
2017-09-14 11:32:55	poojariravi	set	recipients: + poojariravi, scoder, eli.bendersky, serhiy.storchaka
2017-09-14 11:32:55	poojariravi	set	messageid: <1505388775.09.0.221868509513.issue31467@psf.upfronthosting.co.za>
2017-09-14 11:32:55	poojariravi	link	issue31467 messages
2017-09-14 11:32:54	poojariravi	create