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 eric.smith
Recipients eric.smith, flox, georg.brandl, lemburg, mark.dickinson, terry.reedy
Date 2010-09-24.14:27:06
SpamBayes Score 3.4425378e-09
Marked as misclassified No
Message-id <1285338428.17.0.782249826895.issue9418@psf.upfronthosting.co.za>
In-reply-to
Content
Now that I start this, I see that it's complicated by the fact that the functions actually being wrapped are in stringlib/string_format.h. That's because in 2.x they compile as both unicode and str. Before the _string module is created, the code should really be moved out of stringlib (possibly into _string). But that's a much more involved task.

I guess it depends if we want to have a bytes version of format(). If we do, it's best to leave the code in stringlib so it can be shared between the implementations. If we never want that, it can be removed from stringlib and put somewhere else, removing the ability to call it both ways. I'll have to give that some thought.
History
Date User Action Args
2010-09-24 14:27:08eric.smithsetrecipients: + eric.smith, lemburg, georg.brandl, terry.reedy, mark.dickinson, flox
2010-09-24 14:27:08eric.smithsetmessageid: <1285338428.17.0.782249826895.issue9418@psf.upfronthosting.co.za>
2010-09-24 14:27:06eric.smithlinkissue9418 messages
2010-09-24 14:27:06eric.smithcreate