If you don't write or otherwise maintain Python Extension Modules
written in C (or C++) or embed Python in your application,
you can stop reading.
Python 2.5 alpha 1 was released April 5, 2006. The second alpha
should be released in a few weeks. There are several changes
which can cause C extens
If you don't write or otherwise maintain Python Extension Modules
written in C (or C++) or embed Python in your application,
you can stop reading.
Python 2.5 alpha 1 was released April 5, 2006. The second alpha
should be released in a few weeks. There are several changes
which can cause C extens
[EMAIL PROTECTED] wrote:
> One question: Is there a safe way to keep extension modules backward-
> compatible with older Python versions?
absolutely.
> I am thinking of something like
>
> #ifndef PY_SSIZE_T_DEFINED
> typedef Py_ssize_t int;
> #endif
>
> assuming that Python 2.5 defines PY_SSIZE_
On 05.04.2006, at 08:44, [EMAIL PROTECTED] wrote:
> Python 2.5 alpha 1 is in the process of being released later today.
> There are important changes that are in 2.5 to support 64-bit systems.
> These changes can cause Python to crash if your module is not upgraded
> to support the changes. Pytho
Thank you for taking the time to pull the relevant links together and
make this post, Neal.
--
http://mail.python.org/mailman/listinfo/python-list
If you don't write or otherwise maintain Python Extension Modules
written in C (or C++), you can stop reading.
Python 2.5 alpha 1 is in the process of being released later today.
There are important changes that are in 2.5 to support 64-bit systems.
These changes can cause Python to crash if your
