469,610 Members | 1,775 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,610 developers. It's quick & easy.

SystemError: ... cellobject.c:22: bad argument to internal ?

From the trace of a 2.3.5 software i got:

\'SystemError:
C:\\\\sf\\\\python\\\\dist23\\\\src\\\\Objects\\\\ cellobject.c:22: bad
argument to internal
function\\n\']
from the middle of normal function / or its call. What is this?

There is:

http://mail.python.org/pipermail/pyt...ry/260273.html

but seems to be something else. There is no dynamic addition of
class-method. But the last function called is a callback function in
3rd level inner function of class method like:

class X:
def a():
def b():
...
def c():... # breaks with systemerror
schedule_callback(c) # -> upon Windows WM_TIMER event
...
Will there be another bug-fix release of Python 2.3 ?

-robert
May 13 '06 #1
2 2474
robert wrote:
From the trace of a 2.3.5 software i got:

\'SystemError:
C:\\\\sf\\\\python\\\\dist23\\\\src\\\\Objects\\\\ cellobject.c:22: bad
argument to internal
function\\n\']
....
Will there be another bug-fix release of Python 2.3 ?


No, is this still a problem in 2.4? 2.4.4 is planned to be released
this summer. Can you post the entire code (that doesn't reference
anything outside the stdlib) that causes this problem?

n

May 13 '06 #2
nn******@gmail.com wrote:
robert wrote:
From the trace of a 2.3.5 software i got:

\'SystemError:
C:\\\\sf\\\\python\\\\dist23\\\\src\\\\Objects\\ \\cellobject.c:22: bad
argument to internal
function\\n\']

...

Will there be another bug-fix release of Python 2.3 ?

No, is this still a problem in 2.4? 2.4.4 is planned to be released


( Am bound to py2.3 for this app - as py2.4 more than doubled
distributable app sizes with MSVCRTL71, CJK codecs in core etc... )
this summer. Can you post the entire code (that doesn't reference
anything outside the stdlib) that causes this problem?


Solved - no Python error.

The bug turned out to be a refcount bug in PythonWin's
win32ui.HookMessage internals: the Python callback upon WM_TIMER didn't
INCREF the called function object itself. When the function removed
itself from the hook list (indirectly), the executing functions
closure/cells.. were recycled while the function was still executing.

https://sourceforge.net/tracker/inde...18&atid=551954

-robert
May 16 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by Gerrit Holl | last post: by
9 posts views Thread by alban.minassian | last post: by
8 posts views Thread by Kevin Grigorenko | last post: by
reply views Thread by 356523600 | last post: by
1 post views Thread by Waitman Gobble | last post: by
1 post views Thread by max.aginaga | last post: by
reply views Thread by devrayhaan | last post: by
reply views Thread by gheharukoh7 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.