Re: Segfault with tktreectrl on python-2.5 on linux

2007-01-16 Thread klappnase
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

Re: Segfault with tktreectrl on python-2.5 on linux

2007-01-16 Thread Anton Hartl
On 2007-01-16, klappnase [EMAIL PROTECTED] wrote: 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

Re: Segfault with tktreectrl on python-2.5 on linux

2007-01-16 Thread klappnase
Anton Hartl schrieb: The bug report should go to both; I actually contacted Jeremy Hylton as a main contributor of the new AST code two weeks ago but didn't get any response. Ok, I submitted bug reports on both the tktreectrl and the python sourceforge pages. Now I'll have a nice cup of

Segfault with tktreectrl on python-2.5 on linux

2007-01-15 Thread klappnase
Hello, I use the tktreectrl Tk extension (http://tktreectrl.sourceforge.net) through the python wrapper module (http://klappnase.zexxo.net/TkinterTreectrl/index.html). With python-2.5 it seems that each time some text is inserted into the treectrl widget a segfault occurs (on linux, on

Re: Segfault with tktreectrl on python-2.5 on linux

2007-01-15 Thread Anton Hartl
Hi, On 2007-01-15, klappnase [EMAIL PROTECTED] wrote: Some people sent me mail describing the same problem, so I think it is not a problem with my installation of python-2.5. The treectrl widget itself works well when running from Tcl or from python2.4, so i suspect that it is a bug in