Message124914
| Author |
georg.brandl |
| Recipients |
Rhamphoryncus, amaury.forgeotdarc, belopolsky, doerwalter, eric.smith, ezio.melotti, georg.brandl, lemburg, loewis, pitrou, rhettinger, stutzbach, vstinner |
| Date |
2010年12月30日.11:14:44 |
| SpamBayes Score |
4.6147616e-07 |
| Marked as misclassified |
No |
| Message-id |
<1293707693.19.0.833293133625.issue10542@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> I think the proposal is that fixing this minefield can wait until
> Python 3.3 (or even 3.4, or later).
That is what I was thinking. (Alex: You might not know that Martin
was the main proponent of non-ASCII identifiers, so this assessment
should have some weight.)
> I'm thinking about an approach of a variable representation:
> one, two, or four bytes, depending on the widest character that
> appears in the string. I think it can be arranged to make this mostly
> backwards-compatible with existing APIs, so it doesn't need to wait
> for py4k, IMO. OTOH, I'm not sure I'll make it for 3.3.
That is an interesting idea. I would be interested in helping out
when you'll implement it. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2010年12月30日 11:14:53 | georg.brandl | set | recipients:
+ georg.brandl, lemburg, loewis, doerwalter, rhettinger, amaury.forgeotdarc, belopolsky, Rhamphoryncus, pitrou, vstinner, eric.smith, stutzbach, ezio.melotti |
| 2010年12月30日 11:14:53 | georg.brandl | set | messageid: <1293707693.19.0.833293133625.issue10542@psf.upfronthosting.co.za> |
| 2010年12月30日 11:14:45 | georg.brandl | link | issue10542 messages |
| 2010年12月30日 11:14:44 | georg.brandl | create |
|