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 benjamin.peterson
Recipients arjennienhuis, benjamin.peterson, christian.heimes, eric.smith, exarkun, ezio.melotti, gvanrossum, loewis, martin.panter, serhiy.storchaka, terry.reedy, uau, vstinner
Date 2013-01-22.18:48:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1358880501.52.0.962770332106.issue3982@psf.upfronthosting.co.za>
In-reply-to
Content
The problem is not so much the types allowed the code for dealing with the format string. The parsing code for format specificers is pretty unicode specific now. If that was to be made generic again, it's worth considering exactly what features belong in a bytes format method.
History
Date User Action Args
2013-01-22 18:48:21benjamin.petersonsetrecipients: + benjamin.peterson, gvanrossum, loewis, terry.reedy, exarkun, vstinner, eric.smith, christian.heimes, ezio.melotti, arjennienhuis, uau, martin.panter, serhiy.storchaka
2013-01-22 18:48:21benjamin.petersonsetmessageid: <1358880501.52.0.962770332106.issue3982@psf.upfronthosting.co.za>
2013-01-22 18:48:21benjamin.petersonlinkissue3982 messages
2013-01-22 18:48:21benjamin.petersoncreate