On 19.06.15 07:56, Serhiy Storchaka wrote:
May be private table for case-insensitive matching in the re module
should be updated too.
Confirm that the re module doesn't need the update to Unicode 8.0.
___
Python-Dev mailing list
Python-Dev@python.org
On 6/27/2015 4:57 PM, Benjamin Peterson wrote:
On Thu, Jun 18, 2015, at 13:27, Terry Reedy wrote:
Unicode 8.0 was just released. Can we have unicodedata updated to match
in 3.5?
3.5 now has Unicode 8.0.0.
Great. Does the release PEP or something else have instructions on how
to do this?
On Thu, Jun 18, 2015, at 13:27, Terry Reedy wrote:
> Unicode 8.0 was just released. Can we have unicodedata updated to match
> in 3.5?
3.5 now has Unicode 8.0.0.
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listin
On Thu Jun 18 20:33:13 CEST 2015, Larry Hastings asked:
> On 06/18/2015 11:27 AM, Terry Reedy wrote:
>> Unicode 8.0 was just released. Can we have unicodedata updated to
>> match in 3.5?
> What does this entail? Data changes, code changes, both?
Note that the unicode 7 changes also need to
On 18.06.15 22:34, MRAB wrote:
On 2015-06-18 19:33, Larry Hastings wrote:
On 06/18/2015 11:27 AM, Terry Reedy wrote:
Unicode 8.0 was just released. Can we have unicodedata updated to
match in 3.5?
What does this entail? Data changes, code changes, both?
It looks like just data changes.
On Fri, Jun 19, 2015 at 01:55:07AM +0100, MRAB wrote:
> On 2015-06-19 00:56, Steven D'Aprano wrote:
> >At the very least, there is a change to the casefolding algorithm.
> >Cherokee was classified as unicameral but is now considered bicameral
> >(two cases, like English). Unusually, case-folding C
On 06/18/2015 11:27 AM, Terry Reedy wrote:
Unicode 8.0 was just released. Can we have unicodedata updated to
match in 3.5?
What do the Python unicodedata Experts say? That'd be "loewis",
"lemburg", and "ezio.melotti".
According to the Dev Guide,
//arry/
_
On 2015-06-19 00:56, Steven D'Aprano wrote:
On Thu, Jun 18, 2015 at 08:34:14PM +0100, MRAB wrote:
On 2015-06-18 19:33, Larry Hastings wrote:
>On 06/18/2015 11:27 AM, Terry Reedy wrote:
>>Unicode 8.0 was just released. Can we have unicodedata updated to
>>match in 3.5?
>>
>
>What does this entai
On Thu, Jun 18, 2015 at 08:34:14PM +0100, MRAB wrote:
> On 2015-06-18 19:33, Larry Hastings wrote:
> >On 06/18/2015 11:27 AM, Terry Reedy wrote:
> >>Unicode 8.0 was just released. Can we have unicodedata updated to
> >>match in 3.5?
> >>
> >
> >What does this entail? Data changes, code changes, b
On 2015-06-18 19:33, Larry Hastings wrote:
On 06/18/2015 11:27 AM, Terry Reedy wrote:
Unicode 8.0 was just released. Can we have unicodedata updated to
match in 3.5?
What does this entail? Data changes, code changes, both?
It looks like just data changes.
There are additional codepoints
On 06/18/2015 11:27 AM, Terry Reedy wrote:
Unicode 8.0 was just released. Can we have unicodedata updated to
match in 3.5?
What does this entail? Data changes, code changes, both?
//arry/
___
Python-Dev mailing list
Python-Dev@python.org
https:/
Unicode 8.0 was just released. Can we have unicodedata updated to match
in 3.5?
--
Terry Jan Reedy
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/opt
12 matches
Mail list logo
