Message 299707 - Python tracker

➜

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	steven.daprano
Recipients	Guillaume Sanchez, Socob, benjamin.peterson, ezio.melotti, lemburg, loewis, mrabarnett, r.david.murray, serhiy.storchaka, steven.daprano, terry.reedy, vstinner
Date	2017年08月03日.13:30:55
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<20170803133049.GQ3149@ando.pearwood.info>
In-reply-to	<1501759297.91.0.0682923592822.issue30717@psf.upfronthosting.co.za>

Content
On Thu, Aug 03, 2017 at 11:21:38AM +0000, Serhiy Storchaka wrote: > Should iterators provide just substrings or their positions? [...] I think we're breaking new ground here and I'm not sure what the right API should be. Should we follow Perl 6? https://docs.perl6.org/type/Str Go has a "norm" package for dealing with normalised "characters" (graphemes). https://blog.golang.org/normalization http://godoc.org/golang.org/x/text/unicode/norm Are my comments unacceptible scope-creep? We've gone from talking about a grapheme cluster break algorithm to me talking about Perl6 and Go which have rich string APIs based on graphemes. I'm not even sure of the best place for this: - unicodedata - string - a new module? I don't think unicodedata is the right place -- that should be for data and processing of individual unicode code points, not string handling, and it shouldn't become a grab-bag of random unrelated functions just because they have something to do with Unicode. Can we mark this as having a Provisional API to give us time to decide on the best API before locking it in permanently? https://www.python.org/dev/peps/pep-0411/ I'm reluctant to say this, because it's a lot more work, but maybe this is complicated enough that we should go through a PEP.

Content

On Thu, Aug 03, 2017 at 11:21:38AM +0000, Serhiy Storchaka wrote:
> Should iterators provide just substrings or their positions?
[...]
I think we're breaking new ground here and I'm not sure what the right 
API should be. Should we follow Perl 6?
https://docs.perl6.org/type/Str
Go has a "norm" package for dealing with normalised "characters" 
(graphemes).
https://blog.golang.org/normalization
http://godoc.org/golang.org/x/text/unicode/norm
Are my comments unacceptible scope-creep? We've gone from talking about 
a grapheme cluster break algorithm to me talking about Perl6 and Go 
which have rich string APIs based on graphemes.
I'm not even sure of the best place for this:
- unicodedata
- string
- a new module?
I don't think unicodedata is the right place -- that should be for data 
and processing of individual unicode code points, not string handling, 
and it shouldn't become a grab-bag of random unrelated functions just 
because they have something to do with Unicode.
Can we mark this as having a Provisional API to give us time to decide on the 
best API before locking it in permanently?
https://www.python.org/dev/peps/pep-0411/
I'm reluctant to say this, because it's a lot more work, but maybe this 
is complicated enough that we should go through a PEP.

History
Date	User	Action	Args
2017年08月03日 13:30:56	steven.daprano	set	recipients: + steven.daprano, lemburg, loewis, terry.reedy, vstinner, benjamin.peterson, ezio.melotti, mrabarnett, r.david.murray, serhiy.storchaka, Socob, Guillaume Sanchez
2017年08月03日 13:30:56	steven.daprano	link	issue30717 messages
2017年08月03日 13:30:55	steven.daprano	create

homepage