Message 141052 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

In-reply-to
Author	culler
Recipients	culler, ned.deily, ronaldoussoren
Date	2011年07月24日.18:55:38
SpamBayes Score	6.3400366e-05
Marked as misclassified	No
Message-id	<1311533739.36.0.347234120453.issue10731@psf.upfronthosting.co.za>

Content
I am running OSX 10.5.8 on this macbook. The Tcl/Tk package on the system is ActiveState Tcl/Tk 8.4.19. I just installed Python 3.2 (r32:88452, Feb 20 2011, 10:19:59) from http://www.python.org/getit/releases/3.2/ and I am still seeing this bug. It does not occur with the Python 2.7 Tkinter package, which uses the same Tcl/Tk framework. So if it is a bug in Tk, it is harmless when used with Python 2.7. But, after all, it is not so surprising to see new UnicodeDecodeErrors when porting from Python 2 to Python 3.

Content

I am running OSX 10.5.8 on this macbook. The Tcl/Tk package on the system is ActiveState Tcl/Tk 8.4.19.
I just installed Python 3.2 (r32:88452, Feb 20 2011, 10:19:59) from http://www.python.org/getit/releases/3.2/ and I am still seeing this bug. It does not occur with the Python 2.7 Tkinter package, which uses the same Tcl/Tk framework. So if it is a bug in Tk, it is harmless when used with Python 2.7. But, after all, it is not so surprising to see new UnicodeDecodeErrors when porting from Python 2 to Python 3.

History
Date	User	Action	Args
2011年07月24日 18:55:39	culler	set	recipients: + culler, ronaldoussoren, ned.deily
2011年07月24日 18:55:39	culler	set	messageid: <1311533739.36.0.347234120453.issue10731@psf.upfronthosting.co.za>
2011年07月24日 18:55:38	culler	link	issue10731 messages
2011年07月24日 18:55:38	culler	create

homepage