python-ldap-dev

PEP 353 - preparation for Python 2.5

[<mi...@st...>]

HI!

I'm very short on spare time at the moment.

Could someone please check python-ldap to support PEP 353 (see
http://www.python.org/dev/peps/pep-0353/) and create a patch for the
changes required?

See also:

http://groups.google.com/group/comp.lang.python/tree/browse_frm/thread/7e55ac8f0ca175a0/69951264453fdfb2?rnum=1&_done=%2Fgroup%2Fcomp.lang.python%2Fbrowse_frm%2Fthread%2F7e55ac8f0ca175a0%2F69951264453fdfb2%3F#doc_69951264453fdfb2

http://svn.effbot.python-hosting.com/stuff/sandbox/python/ssizecheck.py

Many thanks in advance.

Ciao, Michael.

Re: PEP 353 - preparation for Python 2.5

[<mi...@st...>]

Michael Str=F6der wrote:
>=20
> Could someone please check python-ldap to support PEP 353 (see
> http://www.python.org/dev/peps/pep-0353/) and create a patch for the
> changes required?

I've committed some changes regarding PEP 353. I'd be glad if someone
could test python-ldap pulled from CVS on a 64-bit platform.

Ciao, Michael.

Re: PEP 353 - preparation for Python 2.5

[Matej V. <ve...@de...>]

Michael Str=F6der <mi...@st...> writes:

> Michael Str=F6der wrote:
>>=20
>> Could someone please check python-ldap to support PEP 353 (see
>> http://www.python.org/dev/peps/pep-0353/) and create a patch for the
>> changes required?
>
> I've committed some changes regarding PEP 353. I'd be glad if someone
> could test python-ldap pulled from CVS on a 64-bit platform.

A couple of fixes attached:

  * More instances of s/int/Py_ssize_t/ (some of these are unlikely to
    matter in practice, but might make automated testing easier).

  * Define PY_SSIZE_T_CLEAN before including <Python.h> to get the new
    semantics for 's#' and 't#'.  I've put this in Modules/common.h, and
    included that instead of <Python.h> from the rest of the code.

Other than that, seems to work fine on IA64.

Cheers,

Matej

Re: PEP 353 - preparation for Python 2.5

[<mi...@st...>]

Matej Vela wrote:
> Michael Str=F6der <mi...@st...> writes:
>=20
>>Michael Str=F6der wrote:
>>
>>>Could someone please check python-ldap to support PEP 353 (see
>>>http://www.python.org/dev/peps/pep-0353/) and create a patch for the
>>>changes required?
>>
>>I've committed some changes regarding PEP 353. I'd be glad if someone
>>could test python-ldap pulled from CVS on a 64-bit platform.
>=20
> A couple of fixes attached:

Is the patch against CVS HEAD?

Ciao, Michael.

Re: PEP 353 - preparation for Python 2.5

[<mi...@st...>]

Matej Vela wrote:
> Michael Str=F6der <mi...@st...> writes:
>=20
>=20
>>Matej Vela wrote:
>>
>>>Michael Str=F6der <mi...@st...> writes:
>>>
>>>>I've committed some changes regarding PEP 353. I'd be glad if someone
>>>>could test python-ldap pulled from CVS on a 64-bit platform.
>>>
>>>A couple of fixes attached:
>>
>>Is the patch against CVS HEAD?
>=20
> Yup.

Many thanks for contributing. I've committed it.
Do you think we're through with this issue?

Ciao, Michael.

Re: PEP 353 - preparation for Python 2.5

[Matej V. <ve...@de...>]

Michael Str=F6der <mi...@st...> writes:

> Many thanks for contributing. I've committed it.
> Do you think we're through with this issue?

I've checked all instances of 'int' and 's#'/'z#', so I think this is it.

Thanks!

Matej

Re: PEP 353 - preparation for Python 2.5

[Matej V. <ve...@de...>]

Michael Str=F6der <mi...@st...> writes:

> Matej Vela wrote:
>> Michael Str=F6der <mi...@st...> writes:
>>>I've committed some changes regarding PEP 353. I'd be glad if someone
>>>could test python-ldap pulled from CVS on a 64-bit platform.
>>=20
>> A couple of fixes attached:
>
> Is the patch against CVS HEAD?

Yup.

Cheers,

Matej