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 effbot, flox, georg.brandl, pitrou, r.david.murray, scoder
Date 2010-03-11.21:14:39
SpamBayes Score 8.45282e-11
Marked as misclassified No
Message-id <1268342080.98.0.253844931674.issue8047@psf.upfronthosting.co.za>
In-reply-to
Content
You may well be correct.  But just because no one reported a bug does not mean that no one is using the API.  The person using it may find it perfectly logical (and may be writing py3 only code, not porting py2 code).

However, regardless of whether we decide it is acceptable to change the behavior, it seems to me that having an interface named 'tostring' that returns bytes by default in Python3 would be a broken API.  I don't see any way around that terminology problem.
History
Date User Action Args
2010-03-11 21:14:41r.david.murraysetrecipients: + r.david.murray, effbot, georg.brandl, pitrou, scoder, flox
2010-03-11 21:14:40r.david.murraysetmessageid: <1268342080.98.0.253844931674.issue8047@psf.upfronthosting.co.za>
2010-03-11 21:14:39r.david.murraylinkissue8047 messages
2010-03-11 21:14:39r.david.murraycreate