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 r.david.murray
Recipients Brendan.OConnor, r.david.murray
Date 2013-06-20.04:38:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1371703116.26.0.327062391311.issue18268@psf.upfronthosting.co.za>
In-reply-to
Content
This kind of thing is why python3 exists.  Presumably some bit of the elementree code is successfully converting non-ascii into unicode, and then when that is mixed with the result it is returning, you end up with unicode.  But that is just a guess; you'll have to dig into a specific example to figure out why it is happening.

Or when you say non-deterministically, do you mean that you have tried to reproduce it with a specific entry that returns unicode in the full run and it does not reproduce?  Although even in that case it might be due to some complex interaction in the non-reduced code...

It might be interesting to run it under python3 and see if anything odd happens there...but it will probably just work.
History
Date User Action Args
2013-06-20 04:38:36r.david.murraysetrecipients: + r.david.murray, Brendan.OConnor
2013-06-20 04:38:36r.david.murraysetmessageid: <1371703116.26.0.327062391311.issue18268@psf.upfronthosting.co.za>
2013-06-20 04:38:36r.david.murraylinkissue18268 messages
2013-06-20 04:38:35r.david.murraycreate