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 arjennienhuis, benjamin.peterson, christian.heimes, eric.smith, exarkun, ezio.melotti, glyph, gvanrossum, loewis, martin.panter, pitrou, serhiy.storchaka, terry.reedy, uau, vstinner
Date 2013-01-22.19:39:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1358883598.21.0.954277658398.issue3982@psf.upfronthosting.co.za>
In-reply-to
Content
Right, but we're not writing builtin type methods specifically for Twisted. I agree with the idea that the feature set should very limited, actually perhaps more limited than what you just said. For example, I think any kind of implicit str->bytes conversion is a no-no (including the "r" and "a" format codes).

Still, IMO even a simple feature set warrants a PEP, because we want to devise something that's generally useful, not just something which makes porting easier for Twisted.

I also kind of expect Twisted to have worked around the issue before 3.4 is out, anyway.
History
Date User Action Args
2013-01-22 19:39:58pitrousetrecipients: + pitrou, gvanrossum, loewis, terry.reedy, exarkun, vstinner, eric.smith, christian.heimes, benjamin.peterson, glyph, ezio.melotti, arjennienhuis, uau, martin.panter, serhiy.storchaka
2013-01-22 19:39:58pitrousetmessageid: <1358883598.21.0.954277658398.issue3982@psf.upfronthosting.co.za>
2013-01-22 19:39:58pitroulinkissue3982 messages
2013-01-22 19:39:57pitroucreate