Message81056
| Author |
vstinner |
| Recipients |
ezio.melotti, giampaolo.rodola, loewis, vstinner |
| Date |
2009年02月03日.13:48:13 |
| SpamBayes Score |
2.7085556e-12 |
| Marked as misclassified |
No |
| Message-id |
<200902031448.06254.victor.stinner@haypocalc.com> |
| In-reply-to |
<1233363452.0.0.292344060049.issue5110@psf.upfronthosting.co.za> |
| Content |
> Victor, I'm not sure whether you are proposing that
> display_hook_ascii.patch is included into Python. IIUC, this patch
> breaks PEP3138, so it clearly must be rejected.
>
> Overall, I fail to see the bug in this report. Python 3.0 works as
> designed as shown here.
The idea is to avoid unicode error (by replacing not printable characters by
their code in hexadecimal) when the display hook tries to display a message
which is not printable in the terminal charset.
It's just to make Python3 interpreter a little bit more "user friendly" on
Windows.
Problem: use different (encoding) rule for the display hook and for print()
may disturb new users (Why does ">>> chr(...)" work whereas ">>>
print(chr(...))" fails?). |
|