Josiah Carlson gmail.com> writes:
>
> From what I understand of the memoryview when I tried to do the same
> thing a few months ago (use memoryview to replace buffer in
> asyncore/asynchat), memoryview is incomplete. It didn't support
> character buffer slicing (you know, the 'offset' and 'size'
On Sat, Nov 22, 2008 at 06:29, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Nov 22, 2008, at 4:05 AM, Martin v. Löwis wrote:
>
>> I just noticed that the Python 3 C API still contains PY_SSIZE_T_CLEAN.
>>
>> This macro was a transition mechanism,
On Sat, Nov 22, 2008 at 1:06 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On behalf of the Python development team and the Python community, I am
> happy to announce the third and last planned release candidate for Python
> 3.0.
Whoohoo! :) Grea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 22, 2008, at 4:05 AM, Martin v. Löwis wrote:
I just noticed that the Python 3 C API still contains
PY_SSIZE_T_CLEAN.
This macro was a transition mechanism, to allow extensions to use
Py_ssize_t in PyArg_ParseTuple, while allowing other mod
I just noticed that the Python 3 C API still contains PY_SSIZE_T_CLEAN.
This macro was a transition mechanism, to allow extensions to use
Py_ssize_t in PyArg_ParseTuple, while allowing other module continue
to use int.
In Python 3, I would like the mechanism, making Py_ssize_t the only
valid data
