==
PyPy 1.7 - widening the sweet spot
==
We're pleased to announce the 1.7 release of PyPy. As became a habit, this
release brings a lot of bugfixes and performance improvements over the 1.6
release. However, unlike the previous
Hi,
With the PEP 393, the Py_UNICODE is now deprecated and scheduled for removal
in Python 4. PyUnicode_AsUnicode() and PyUnicode_AsUnicodeAndSize() functions
are still commonly used on Windows to get the string as wchar_t* without
having to care of freeing the memory: it's a borrowed
On Mon, 21 Nov 2011 12:53:17 +0100
Victor Stinner victor.stin...@haypocalc.com wrote:
I would like to add a new PyUnicode_AsWideChar() function which would return
the borrowed reference, exactly as PyUnicode_AsUnicode(). The problem is that
PyUnicode_AsWideChar already exists in Python 3.2,
Le Lundi 21 Novembre 2011 16:04:06 Antoine Pitrou a écrit :
On Mon, 21 Nov 2011 12:53:17 +0100
Victor Stinner victor.stin...@haypocalc.com wrote:
I would like to add a new PyUnicode_AsWideChar() function which would
return the borrowed reference, exactly as PyUnicode_AsUnicode(). The
On Mon, 21 Nov 2011 16:53:10 +0100
Victor Stinner victor.stin...@haypocalc.com wrote:
Le Lundi 21 Novembre 2011 16:04:06 Antoine Pitrou a écrit :
On Mon, 21 Nov 2011 12:53:17 +0100
Victor Stinner victor.stin...@haypocalc.com wrote:
I would like to add a new PyUnicode_AsWideChar()
Hi,
I recently got some patches accepted for inclusion in 3.3, and each time,
the patch metadata (such as my name and my commit comment) were stripped by
applying the patch manually, instead of hg importing it. This makes it
clear in the history who eventually reviewed and applied the
Le Lundi 21 Novembre 2011 16:55:05 Antoine Pitrou a écrit :
I want to rename PyUnicode_AsUnicode() and change its result type
(Py_UNICODE* = wchar_t*). The result will be a borrowed reference,
ie. you don't have to free the memory, it will be done when the Unicode
string will be destroyed
On Mon, 21 Nov 2011 18:02:36 +0100
Victor Stinner victor.stin...@haypocalc.com wrote:
Le Lundi 21 Novembre 2011 16:55:05 Antoine Pitrou a écrit :
I want to rename PyUnicode_AsUnicode() and change its result type
(Py_UNICODE* = wchar_t*). The result will be a borrowed reference,
ie. you
On 20/11/2011 21:41, Guido van Rossum wrote:
On Sun, Nov 20, 2011 at 10:44 AM, Michael Foord
fuzzy...@voidspace.org.uk wrote:
On 20 Nov 2011, at 16:35, Guido van Rossum wrote:
Um, what?! __class__ *already* has a special meaning. Those examples
violate that meaning. No wonder they get
On Mon, Nov 21, 2011 at 9:22 AM, Michael Foord
fuzzy...@voidspace.org.uk wrote:
On 20/11/2011 21:41, Guido van Rossum wrote:
On Sun, Nov 20, 2011 at 10:44 AM, Michael Foord
fuzzy...@voidspace.org.uk wrote:
On 20 Nov 2011, at 16:35, Guido van Rossum wrote:
Um, what?! __class__ *already*
I've approved the latest version of this PEP. Congrats, Antoine!
--Guido
On Fri, Nov 18, 2011 at 12:14 PM, Antoine Pitrou solip...@pitrou.net wrote:
Hello,
I haven't seen any strong objections, so I would like to go ahead and
commit PEP 3155 (*) soon. Is anyone against it?
(*) Qualified
Hi,
I'm trying to rewrite PyUnicode_EncodeDecimal() to upgrade it to the new
Unicode API. The problem is that the function is not accessible in Python nor
tested. Should we document and test it, leave it unchanged and deprecate it,
or simply remove it?
--
Python has a
On 11/21/2011 5:36 AM, Maciej Fijalkowski wrote:
==
PyPy 1.7 - widening the sweet spot
==
We're pleased to announce the 1.7 release of PyPy. As became a habit, this
release brings a lot of bugfixes and performance improvements over
2011/11/21 Terry Reedy tjre...@udel.edu
I strongly recommend that where it makes a difference, the pypy python3
project target 3.3. In particular, don't reproduce the buggy narrow-build
behavior of 3.2 and before (perhaps pypy avoids this already). Do include
the new unicode capi in cpyext. I
Le lundi 21 novembre 2011 21:39:53, Victor Stinner a écrit :
I'm trying to rewrite PyUnicode_EncodeDecimal() to upgrade it to the new
Unicode API. The problem is that the function is not accessible in Python
nor tested.
I added tests for this function in Python 2.7, 3.2 and 3.3.
Hi,
In Python 3.2, PyUnicode_Resize() expects a number of Py_UNICODE units,
whereas Python 3.3 expects a number of characters.
It is tricky to convert a number of Py_UNICODE units to a number of
characters, so it is diffcult to provide a backward compatibility
PyUnicode_Resize() function
16 matches
Mail list logo
