Segfault with tktreectrl on python-2.5 on linux
klappnase
klappnase at web.de
Tue Jan 16 05:03:46 EST 2007
Anton Hartl schrieb:
<snip>
>
> Solutions:
>
> a) convince Python developers to prefix ALL new (wrt. 2.5)
> global symbols with a prefix like "_PyAST_" or equivalent;
> this would be consistent with how it is done anyway,
> unfortunately the new AST symbols deviate from this practise
> (there are symbols like "Assert", "If", "Then", ...)
>
> or b) apply an equivalent rule to the global symbols in
> tktreectrl that are global by accident, i.e. because
> of the way the library is structured and built
>
Anton, you're cool,
actually renaming Ellipsis to Py_Ast_Ellipsis in ast.c and Python-ast.c
seems to fix this.
What I don't understand, isn't it very likely that such things will
happen when names like "Ellipsis" or "Slice" and "Index" (which I also
found in Python-ast.c) are being used, or are the treectrl people doing
something they should avoid?
I think the answer to this might be important when deciding to whom I
should send a bug report :)
Thanks and best regards
Michael
More information about the Python-list
mailing list