RetroSearch Browse

Mon Dec 17 23:58:15 CET 2007 · https://mail.python.org/pipermail/python-dev/2007-December/075735.html

Yes, a tuple containing NULL should never be exposed to Python code --
it should only ever be a temporary result in C code. The C code should
ensure all tuple items are non-NULL before passing the tuple off to
Python (or even to its caller, in most cases).

--Guido

On Dec 17, 2007 1:19 PM, Lisandro Dalcin <dalcinl at gmail.com> wrote:
> Currently, PyTuple_Pack() does not check for NULL arguments, so it is
> going to segfault in this case. Is this intended for performance
> reasons?
>
>
> --
> Lisandro Dalcín
> ---------------
> Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)
> Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
> Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)
> PTLC - Güemes 3450, (3000) Santa Fe, Argentina
> Tel/Fax: +54-(0)342-451.1594
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org
>

-- 
--Guido van Rossum (home page: http://www.python.org/~guido/)

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2007-December/075735.html below:

[Python-Dev] PyTuple_Pack with NULL argument