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 benjamin.peterson, eric.smith, loewis, vstinner
Date 2009-03-24.23:37:05
SpamBayes Score 2.05517e-11
Marked as misclassified No
Message-id <>
> I also not fan on functions having different result type
> (format->bytes or str, it depends...).

In 3.x, str.format() and bytes.format() would be two different methods
on two different objects. I don't think there's any expectation that
they have the same return type. There's no such expectation for
str.strip() and bytes.strip() either.

Similarly, in 2.6, str.format() has a different return type than

Now the builtin format() function is another issue. In 2.6 the return
type does depend on the types of the arguments. In 3.x, I'd suggest
leaving it as unicode and you won't be allowed to pass in bytes.
Date User Action Args
2009-03-24 23:37:08eric.smithsetrecipients: + eric.smith, loewis, vstinner, benjamin.peterson
2009-03-24 23:37:08eric.smithsetmessageid: <>
2009-03-24 23:37:06eric.smithlinkissue3982 messages
2009-03-24 23:37:05eric.smithcreate