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 pitrou
Recipients effbot, flox, georg.brandl, pitrou, r.david.murray, scoder
Date 2010-03-11.14:45:48
SpamBayes Score 0.000264508
Marked as misclassified No
Message-id <20100311094522.2a2103e4@msiwind>
In-reply-to <1268311036.36.0.423782371787.issue8047@psf.upfronthosting.co.za>
Content
> The "no header" thing is very much done on purpose, and it's
> documented in the upstream ElementTree documentation.

I'm sorry, where is that?
I can't find it either at
http://effbot.org/zone/pythondoc-elementtree-ElementTree.htm#elementtree.ElementTree.tostring-function
or
http://effbot.org/zone/pythondoc-elementtree-ElementTree.htm#elementtree.ElementTree.ElementTree.write-method

> I suggest dropping this "Python 3 exists in its own universe"
> nonsense; it's not very professional, and it's hurting Python, its
> users, and all third party developers.

Ha. There has been a very long temporal window (until 3.1, probably)
during which things were very much in flux and anyone with a
professional knowledge of elementtree and XML APIs could chime in and
point out any nonsense in py3k.

Now Python 3.1 is out and as a result py3k also has to ensure upwards
compatibility for its own APIs. Of course we can still make exceptions
if the alleged breakage is truly major. To me, it doesn't /seem/ to be
the case here.
History
Date User Action Args
2010-03-11 14:45:50pitrousetrecipients: + pitrou, effbot, georg.brandl, scoder, r.david.murray, flox
2010-03-11 14:45:49pitroulinkissue8047 messages
2010-03-11 14:45:48pitroucreate