[Pymilter] pymilter segfaults

[Stuart D. Gathman]

On Thu, 4 Dec 2008, Stuart D. Gathman wrote:

> The two likely segfault inducing changes are:
> 
> 1) http://www.python.org/doc/2.5.2/whatsnew/pep-353.html#pep-353
>    Must use Py_ssize_t instead of int in many situations.  Can break
>    working 2.4 code with 2.5 on 64-bit.

The only function affected by the change according to ssizecheck.py is
generic_env_wrapper(), and all Py_ssize_t args are autoconverted by compiler
(passed as non-varargs).

> 2) Changes to obmalloc means that PyMem and PyObject calls must be
>    carefully matched.  This would break working (but incorrect)
>    2.4 code on 2.5.

PyMem_* is never used.

-- 
	      Stuart D. Gathman <stuart at bmsi.com>
    Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.