[issue13604] update PEP 393 (match implementation)

2013-03-14 Thread Ezio Melotti
Ezio Melotti added the comment: What's the status of this? -- nosy: +ezio.melotti ___ Python tracker ___ ___ Python-bugs-list mailing

[issue13604] update PEP 393 (match implementation)

2011-12-16 Thread Jesús Cea Avión
Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue13604] update PEP 393 (match implementation)

2011-12-16 Thread Jim Jewett
Changes by Jim Jewett : Added file: http://bugs.python.org/file23980/pep-0393_20111216.txt.patch ___ Python tracker ___ ___ Python-bugs-list m

[issue13604] update PEP 393 (match implementation)

2011-12-16 Thread Jim Jewett
Jim Jewett added the comment: >> Why is the utf-8 representation not cached when it is generated for >> ParseTuple et alia? My error -- I read something backwards. >> When a string is created from a wchar_t array, who is responsible for >> releasing the original wchar_t array? > The caller.

[issue13604] update PEP 393 (match implementation)

2011-12-15 Thread Martin v . Löwis
Martin v. Löwis added the comment: > Why is the utf-8 representation not cached when it is generated for > ParseTuple et alia? It is. > When a string is created from a wchar_t array, who is responsible for > releasing the original wchar_t array? The caller. > As I read it now, Python > doesn

[issue13604] update PEP 393 (match implementation)

2011-12-15 Thread Jim Jewett
Changes by Jim Jewett : Added file: http://bugs.python.org/file23971/pep-0393v20111215.patch ___ Python tracker ___ ___ Python-bugs-list maili

[issue13604] update PEP 393 (match implementation)

2011-12-15 Thread Jim Jewett
Jim Jewett added the comment: >> So even if a third party module uses the legagy Unicode API, the PEP >> 393 will still optimize the memory usage thanks to implicit calls to >> PyUnicode_READY() (done everywhere in Python source code). > ... unless they inspect a given Unicode string, in which

[issue13604] update PEP 393 (match implementation)

2011-12-15 Thread Martin v . Löwis
Martin v. Löwis added the comment: > (1) Upon string creation, do we want to *promise* to discard the UTF-8 and > wstr, so that the caller can memory manage? I don't understand the question. Assuming "discards" means "releases" here, then there is no API which releases memory during creation

[issue13604] update PEP 393 (match implementation)

2011-12-15 Thread Martin v . Löwis
Martin v. Löwis added the comment: > PyUnicode_AsUnicode(), PyUnicode_AS_UNICODE(), PyUnicode_GET_SIZE(), > ... do reallocate a Py_UNICODE* string for a ready string, but I > don't think that it is a usual use case. Define "usual". There were certainly plenty of occurrences of that in the Pytho

[issue13604] update PEP 393 (match implementation)

2011-12-15 Thread Jim Jewett
Jim Jewett added the comment: Updated to resolve most of Victor's concerns, but this meant enough changes that I'm not sure it quite counts as editorial only. A few questions that I couldn't answer: (1) Upon string creation, do we want to *promise* to discard the UTF-8 and wstr, so that the

[issue13604] update PEP 393 (match implementation)

2011-12-15 Thread Jim Jewett
Changes by Jim Jewett : Added file: http://bugs.python.org/file23968/pep-0393.txt ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue13604] update PEP 393 (match implementation)

2011-12-15 Thread STINNER Victor
STINNER Victor added the comment: Various comments of the PEP 393 and your patch. "For compatibility with existing APIs, several representations may exist in parallel; over time, this compatibility should be phased out." and "For compatibility, redundant representations may be computed." I nev

[issue13604] update PEP 393 (match implementation)

2011-12-15 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +haypo, loewis stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue13604] update PEP 393 (match implementation)

2011-12-14 Thread Jim Jewett
Changes by Jim Jewett : -- assignee: -> docs@python components: +Documentation nosy: +docs@python versions: +Python 3.3 Added file: http://bugs.python.org/file23961/pep-0393.txt ___ Python tracker

[issue13604] update PEP 393 (match implementation)

2011-12-14 Thread Jim Jewett
New submission from Jim Jewett : The implementation has a larger state.kind Clarified wording on wstr_length and surrogate pairs. Clarified that the canonical "data" format doesn't always have a data pointer. Mentioned that calling PyUnicode_READY would finalize a string, so that it couldn't be