[Python-Dev] Bug in PyErr_WriteUnraisable ?

I can fix that in my code, by raising an appropiate exception instance, but I think PyErr_WriteUnraisable lacks some checks. -- Gabriel Becedillas Developer CORE SECURITY TECHNOLOGIES ___ Python-Dev mailing list Python-Dev@python.org http://mail.pytho

Re: [Python-Dev] Bug in PyErr_WriteUnraisable ?

Brett Cannon wrote: > On 2/22/07, Gabriel Becedillas <[EMAIL PROTECTED]> wrote: >> I'd hit an access violation inside PyErr_WriteUnraisable when a >> non-exception instance was raised. The call to PyExceptionClass_Name >> with a non-exception instance is yieldi

[Python-Dev] PyThreadState_SetAsyncExc and native extensions

Does anyone know if PyThreadState_SetAsyncExc stops a thread while its inside a native extension ? I'm trying to stop a testing script that boils down to this: while True: print "aaa" native_extension_call() print "bbb" Using PyThreadState_SetAsyncExc the module doesn't stop but if

[Python-Dev] PyThreadState_SetAsyncExc, PyErr_Clear and native extensions

I use PyThreadState_SetAsyncExc to stop a python thread but there are situations when the thread doesn't stop and continues executing normally. After some debugging, I realized that the problem is that PyThreadState_SetAsyncExc was called when the thread was inside a native extension, that for some

[Python-Dev] Syscall Proxying in Python

all the time are import.c and pythonrun.c, but I'm not sure at all. Maybe you guys figure out another way to achieve what we need. Thanks in advance. -- Gabriel Becedillas Developer CORE SECURITY TECHNOLOGIES Florida 141 - 2º cuerpo - 7º piso C1005AAC Buenos Aires - Argen

Re: [Python-Dev] Syscall Proxying in Python

Donovan Baarda wrote: > On Mon, 2005-08-01 at 10:36, Gabriel Becedillas wrote: > >>Hi, >>We embbeded Python 2.0.1 in our product a few years ago and we'd like to >>upgrade to Python 2.4.1. This was not a simple task, because we needed >>to execute syscalls on

[Python-Dev] Sharing between multiple interpreters and restricted mode

eters ?. Thanks. -- Gabriel Becedillas Developer CORE SECURITY TECHNOLOGIES Florida 141 - 2º cuerpo - 7º piso C1005AAC Buenos Aires - Argentina Tel/Fax: (54 11) 5032-CORE (2673) http://www.corest.com ___ Python-Dev mailing list Python-Dev@python.org http://

[Python-Dev] PyThreadState_Delete vs PyThreadState_DeleteCurrent

(and this often happens), and the previous thread used PyThreadState_Delete instead of PyThreadState_DeleteCurrent, an old and invalid value for autoTLSkey is stored, and that is triggering the Py_FatalError. Thanks. -- Gabriel Becedillas Developer CORE SECURITY TECHNOLOGIES Florida 14

[Python-Dev] pystate.c changes for Python 2.4.2

Hi, At the company I work for, we've embedded Python in C++ application we develop. Since our upgrade to Python 2.4.2 from 2.4.1 we started hitting Py_FatalError("Invalid thread state for this thread") when using debug builds. We use both multiple interpreters and thread states. I think the pro

Re: [Python-Dev] pystate.c changes for Python 2.4.2

Michael Hudson wrote: > Gabriel Becedillas <[EMAIL PROTECTED]> writes: > > >>Hi, >>At the company I work for, we've embedded Python in C++ application we >>develop. Since our upgrade to Python 2.4.2 from 2.4.1 we started hitting >>Py_FatalError(

Re: [Python-Dev] pystate.c changes for Python 2.4.2

Gabriel Becedillas wrote: > Michael Hudson wrote: >> Gabriel Becedillas <[EMAIL PROTECTED]> writes: >> >> >>> Hi, >>> At the company I work for, we've embedded Python in C++ application >>> we develop. Since our upgrade to Python 2.4.

Re: [Python-Dev] pystate.c changes for Python 2.4.2

Thanks to everyone for the great support. I've submitted a patch for this: http://sourceforge.net/tracker/index.php?func=detail&aid=1413181&group_id=5470&atid=305470. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listi