On 07.03.2012 08:08, Stefan Behnel wrote:
Jim J. Jewett, 06.03.2012 20:43:
Hash Randomization (issue 13703) is now on by default. Unfortunately,
this does break some tests; it can be temporarily turned off by setting
the environment variable PYTHONHASHSEED to "0" before launching python.
I
Jim J. Jewett, 06.03.2012 20:43:
> Hash Randomization (issue 13703) is now on by default. Unfortunately,
> this does break some tests; it can be temporarily turned off by setting
> the environment variable PYTHONHASHSEED to "0" before launching python.
I don't think that makes it clear enough tha
On Wed, Mar 7, 2012 at 4:15 AM, Stefan Krah wrote:
> Victor Stinner wrote:
>> A Unicode string is an array of code point. Another approach is to
>> expose such string as an array of uint8/uint16/uint32 integers. I
>> don't know if you expect to get a character / a substring when you
>> read the b
Martin v. Löwis v.loewis.de> writes:
> It most likely is a misconfiguration of your system. I guess that the
> registry key for the DLL has a non-zero refcount before you started the
> installation, so that the refcount didn't drop to zero when you uninstalled.
That must have been it - thanks. I
Am 06.03.2012 15:35, schrieb Vinay Sajip:
> I've built an MSI with 3.3 on Windows 7 and installed it - it seems to work OK
> in that it passes all tests except test_tcl (intermittent failure). However,
> when I uninstall, python33.dll is left behind in System32. If I rebuild the
> MSI
> after some
> I think it would be nice for Python3.3 to implement the PEP-3118
> suggestion:
>
> 'c' -> UCS1
>
> 'u' -> UCS2
>
> 'w' -> UCS4
What is the use case for these format codes?
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mai
Il 06 marzo 2012 20:43, Jim J. Jewett ha scritto:
>
>
> In http://mail.python.org/pipermail/python-dev/2012-March/117348.html
> Georg Brandl posted:
>
>> Python 3.3 includes a range of improvements of the 3.x series, as well as
>> easier
>> porting between 2.x and 3.x. Major new features in th
In http://mail.python.org/pipermail/python-dev/2012-March/117348.html
Georg Brandl posted:
> Python 3.3 includes a range of improvements of the 3.x series, as well as
> easier
> porting between 2.x and 3.x. Major new features in the 3.3 release series
> are:
As much as it is nice to just c
On 05.03.2012 14:27, Ned Batchelder wrote:
For a more extensive list of changes in 3.3.0, see
http://docs.python.org/3.3/whatsnew/3.3.html
The 3.3 whatsnews page doesn't seem to mention PEP 414 or Unicode
literals at all.
Indeed. Thanks to Nick, this is now fixed.
Georg
___
Victor Stinner wrote:
> > 'c' -> UCS1
> > 'u' -> UCS2
> > 'w' -> UCS4
>
> A Unicode string is an array of code point. Another approach is to
> expose such string as an array of uint8/uint16/uint32 integers. I
> don't know if you expect to get a character / a substring when you
> read the buffer o
> In the array module the 'u' specifier previously meant "2-bytes, on wide
> builds 4-bytes". Currently in 3.3 the 'u' specifier is mapped to UCS4.
>
> I think it would be nice for Python3.3 to implement the PEP-3118
> suggestion:
>
> 'c' -> UCS1
>
> 'u' -> UCS2
>
> 'w' -> UCS4
A Unicode string is
Hello,
In the array module the 'u' specifier previously meant "2-bytes, on wide
builds 4-bytes". Currently in 3.3 the 'u' specifier is mapped to UCS4.
I think it would be nice for Python3.3 to implement the PEP-3118
suggestion:
'c' -> UCS1
'u' -> UCS2
'w' -> UCS4
Actually we could even add '
Nick Coghlan wrote:
> On Tue, Mar 6, 2012 at 8:34 PM, Stefan Krah wrote:
> > The obvious question is: Will anyone need view==NULL in the future or
> > can we remove the special case?
>
> The public API will still need a guard (to report an error), but +1
> for otherwise eliminating the undocumen
I've built an MSI with 3.3 on Windows 7 and installed it - it seems to work OK
in that it passes all tests except test_tcl (intermittent failure). However,
when I uninstall, python33.dll is left behind in System32. If I rebuild the MSI
after some changes and reinstall, the old python33.dll is not o
Nick Coghlan, 06.03.2012 12:19:
> On Tue, Mar 6, 2012 at 8:34 PM, Stefan Krah wrote:
>> The obvious question is: Will anyone need view==NULL in the future or
>> can we remove the special case?
>
> The public API will still need a guard (to report an error), but +1
> for otherwise eliminating the u
On Tue, Mar 6, 2012 at 8:34 PM, Stefan Krah wrote:
> The obvious question is: Will anyone need view==NULL in the future or
> can we remove the special case?
The public API will still need a guard (to report an error), but +1
for otherwise eliminating the undocumented special case.
Cheers,
Nick.
Hello,
PyObject_GetBuffer() had an undocumented variant that was used internally:
PyObject_GetBuffer(obj, NULL, flags)
view==NULL has never been allowed by either PEP-3118 or the documentation:
PEP: "The first variable is the "exporting" object. The second argument
is the address to
17 matches
Mail list logo
