Message213642
| Author | serhiy.storchaka |
|---|---|
| Recipients | eric.araujo, georg.brandl, kunkku, pitrou, serhiy.storchaka |
| Date | 2014-03-15.06:16:34 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1394864195.25.0.696967720133.issue20491@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
What about other spaces: '\N{OGHAM SPACE MARK}', '\N{EN QUAD}', '\N{EM QUAD}', '\N{EN SPACE}', '\N{EM SPACE}', '\N{THREE-PER-EM SPACE}', '\N{FOUR-PER-EM SPACE}', '\N{SIX-PER-EM SPACE}', '\N{FIGURE SPACE}', '\N{PUNCTUATION SPACE}', '\N{THIN SPACE}', '\N{HAIR SPACE}', '\N{LINE SEPARATOR}', '\N{PARAGRAPH SEPARATOR}', '\N{NARROW NO-BREAK SPACE}', '\N{MEDIUM MATHEMATICAL SPACE}', '\N{IDEOGRAPHIC SPACE}'? In Python 2 textwrap supported only 8-bit spaces, but Python 3 should support full Unicode. And from this side of view the proposed patch is a regression. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-03-15 06:16:35 | serhiy.storchaka | set | recipients: + serhiy.storchaka, georg.brandl, pitrou, eric.araujo, kunkku |
| 2014-03-15 06:16:35 | serhiy.storchaka | set | messageid: <1394864195.25.0.696967720133.issue20491@psf.upfronthosting.co.za> |
| 2014-03-15 06:16:35 | serhiy.storchaka | link | issue20491 messages |
| 2014-03-15 06:16:34 | serhiy.storchaka | create | |