Message151600
| Author |
Jim.Jewett |
| Recipients |
Jim.Jewett, benjamin.peterson, ezio.melotti |
| Date |
2012年01月19日.01:05:12 |
| SpamBayes Score |
5.9997983e-05 |
| Marked as misclassified |
No |
| Message-id |
<1326935113.08.0.846670743641.issue13821@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
My preference would be for non_NFKC.isidentifier() to return False, but that may be a problem for backwards compatibility.
It *may* be worth adding an asidentifier() method that returns either False or the canonicalized string that should be used instead.
At a minimum, the documentation (including docstring) should warn that the method doesn't check for NFKC form, and that if the input is not ASCII, the caller should first ensure this by calling str1=unicodedata.normalize("NFKC", str1) |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年01月19日 01:05:13 | Jim.Jewett | set | recipients:
+ Jim.Jewett, benjamin.peterson, ezio.melotti |
| 2012年01月19日 01:05:13 | Jim.Jewett | set | messageid: <1326935113.08.0.846670743641.issue13821@psf.upfronthosting.co.za> |
| 2012年01月19日 01:05:12 | Jim.Jewett | link | issue13821 messages |
| 2012年01月19日 01:05:12 | Jim.Jewett | create |
|