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 lemburg
Recipients berker.peksag, eric.smith, ezio.melotti, lemburg, mahmoud, martin.panter, r.david.murray, serhiy.storchaka, vstinner
Date 2015-04-22.13:08:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1429708127.25.0.185336687328.issue24019@psf.upfronthosting.co.za>
In-reply-to
Content
I agree with closing this as "won't fix".

It is true that the encoding keyword argument is only useful when passing in byte strings or (and that's also where it originated in Python 2: the default string type is a byte string), but even in Python 3, this is still one of the main uses of the str() constructor.

Note that it's not uncommon to have arguments only be useful for certain types of input objects. See e.g. the int() constructor base argument for similar example.
History
Date User Action Args
2015-04-22 13:08:47lemburgsetrecipients: + lemburg, vstinner, eric.smith, ezio.melotti, r.david.murray, berker.peksag, martin.panter, mahmoud, serhiy.storchaka
2015-04-22 13:08:47lemburgsetmessageid: <1429708127.25.0.185336687328.issue24019@psf.upfronthosting.co.za>
2015-04-22 13:08:47lemburglinkissue24019 messages
2015-04-22 13:08:47lemburgcreate