[Python-3000] IDLE in new py3k
Guido van Rossum
guido at python.org
Fri Aug 10 00:37:23 CEST 2007
On 8/9/07, "Martin v. Löwis" <martin at v.loewis.de> wrote:
> > But the reason we got here was that an AsString() call failed. Why?
> The only reason I can see is that PyObject_Str failed; that may happen
> if PyObject_Str fails. That, in turn, can happen for bytes objects
> if they are not UTF-8.
> I think _tkinter should get rid of AsString, and use the Tcl object
> API instead (not sure how to do that specifically, though)
> > Here's the traceback:
> Are you sure these are related? This traceback looks like a Tcl
> error - so what does that have to do with AsString?
My only evidence is that after I fixed the segfault, this traceback
appeared. Possibly something in IDLE is catching the AsString() error
in a later stage. There may also be timing dependencies since idle
makes heavy use of after().
--Guido van Rossum (home page: http://www.python.org/~guido/)
More information about the Python-3000