➜

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 vstinner
Recipients BreamoreBoy, benjamin.peterson, doerwalter, eric.smith, ezio.melotti, francismb, jwilk, serhiy.storchaka, terry.reedy, vstinner
Date 2015-11-09.10:14:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1447064097.57.0.7582748763.issue7267@psf.upfronthosting.co.za>
In-reply-to
Content 
> Both ways, with OverflowError and Py3k DeprecationWarning, are good to me. What would you say about this Benjamin?

I prefer an OverflowError. I don't like having to enable a flag to fix a bug :-(

According to the issue title, it's really a bug: "format method: c presentation type *broken* in 2.7".

Note: The unit test may check the error message, currently the error message is irrevelant (it mentions unicode whereas bytes (str type) are used).

>>> format(-1, "c")
OverflowError: %c arg not in range(0x110000) (wide Python build)
History
Date User Action Args
2015-11-09 10:14:57vstinnersetrecipients: + vstinner, doerwalter, terry.reedy, eric.smith, benjamin.peterson, jwilk, ezio.melotti, BreamoreBoy, francismb, serhiy.storchaka
2015-11-09 10:14:57vstinnersetmessageid: <1447064097.57.0.7582748763.issue7267@psf.upfronthosting.co.za>
2015-11-09 10:14:57vstinnerlinkissue7267 messages
2015-11-09 10:14:57vstinnercreate