Thank you people. I'm going to try to strip unneeded things and let you
know the result.
Along with running Python on an embedded system, I am considering two
more things. Suppose the system to be a small Linux router, which, after
the kernel starts, merely configures lots of parameters of the ker
int PyErr_CheckSignals()
Documentation for PyErr_CheckSignals [1] says "If an exception is
raised the error indicator is set and the function returns 1;
otherwise the function returns 0.". But the code I see tells me the
function returns -1 on error. What to do? Fix the code, or the
documentati
Michael Glassford wrote:
> In Python 2.4, traceback.print_exc() and traceback.format_exc() silently
> do nothing if there is no active exception; in Python 2.5, they raise an
> exception. Not too difficult to handle, but unexpected (and a pain if
> you use it in a lot of places). I assume it was
-> http://www.python.org/sf/1564547
--
Gustavo J. A. M. Carneiro
"The universe is always one step beyond logic."
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/ma
> When I want to remove something from a list I typically write:
>
> while x in somelist:
> somelist.remove(x)
An O(n) version of removeall:
somelist[:] = [e for e in somelist if e != x]
Raymond
___
Python-Dev mailing list
Python-Dev@python
"Neal Norwitz" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I ignored these as I'm not certain all the platforms we run on accept
> free(NULL).
>
That sounds like exactly what the autotools are designed for. You simply use
free(), and have autoconf check for support of free(NUL
