 |
Newsgroups: comp.lang.python
Date: 4 Apr 2006 23:44:16 -0700
Local: Wed, Apr 5 2006 2:44 am
Subject: IMPORTANT 2.5 API changes for C Extension Modules
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. For more details about the Python 2.5 schedule: The effbot wrote a program to check your code and find potential Please test and upgrade your extension modules! Cheers, You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| |||||||||||||
|
Newsgroups: comp.lang.python
From: "David Rushby" <DavidRus...@gmail.com>
Date: 5 Apr 2006 18:27:04 -0700
Local: Wed, Apr 5 2006 9:27 pm
Subject: Re: IMPORTANT 2.5 API changes for C Extension Modules
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| |||||||||||||
|
Newsgroups: comp.lang.python
From: konrad.hin...@laposte.net
Date: Thu, 6 Apr 2006 12:46:56 +0200
Local: Thurs, Apr 6 2006 6:46 am
Subject: Re: IMPORTANT 2.5 API changes for C Extension Modules
On 05.04.2006, at 08:44, nnorw...@gmail.com wrote:
> Python 2.5 alpha 1 is in the process of being released later today. Thanks for the information! > 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. Python was changed internally to use 64-bit > values on 64-bit machines for indices. If you've got a machine with > more than 16 GB of RAM, it would be great if you can test Python with > large (> 2GB) strings and other sequences. > For more details about the Python 2.5 schedule: One question: Is there a safe way to keep extension modules backward- #ifndef PY_SSIZE_T_DEFINED assuming that Python 2.5 defines PY_SSIZE_T_DEFINED. Konrad. You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| |||||||||||||
|
Newsgroups: comp.lang.python
From: "Fredrik Lundh" <fred...@pythonware.com>
Date: Thu, 6 Apr 2006 12:49:42 +0200
Local: Thurs, Apr 6 2006 6:49 am
Subject: Re: IMPORTANT 2.5 API changes for C Extension Modules
konrad.hin...@laposte.net wrote: absolutely. > One question: Is there a safe way to keep extension modules backward- > compatible with older Python versions? > I am thinking of something like the "official" way to do this is described in the conversion guidelines: > #ifndef PY_SSIZE_T_DEFINED > assuming that Python 2.5 defines PY_SSIZE_T_DEFINED. http://www.python.org/dev/peps/pep-0353/#conversion-guidelines </F> You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| |||||||||||||
