Movatterモバイル変換

[Python-Dev] folding cElementTree behind ElementTree in 3.3

• Previous message:[Python-Dev] folding cElementTree behind ElementTree in 3.3
• Next message:[Python-Dev] folding cElementTree behind ElementTree in 3.3
• Messages sorted by:[ date ][ thread ][ subject ][ author ]

On Tue, Feb 21, 2012 at 11:39 AM, Eli Bendersky <eliben at gmail.com> wrote:> So the two choices here are either change the documentation or the C> implementation to actually make Element a class. The first is of course> simpler. However, someone somewhere may have written code that knowingly> forces the Python implementation to be used and subclasses Element. Such> code will break in 3.3, so it probably makes sense to invest in making> Element a class in the C implementation as well.Yeah, that's my take as well (especially since, in 3.2 and earlier,"forcing" use of the pure Python version was just a matter ofimporting ElementTree instead of cElementTree).While Xavier's point about lxml following cElementTree's lead andusing a factory function is an interesting one, I think in this casethe documented behaviour + pure Python implementation win out over theC accelerator behaviour.Cheers,Nick.-- Nick Coghlan   |  ncoghlan at gmail.com   |   Brisbane, Australia

• Previous message:[Python-Dev] folding cElementTree behind ElementTree in 3.3
• Next message:[Python-Dev] folding cElementTree behind ElementTree in 3.3
• Messages sorted by:[ date ][ thread ][ subject ][ author ]