Francisco Martín Brugué added the comment:
Hi,
just a question:
the status of this issue is pending but it seems to be already
resolved/duplicated. Means that this issue can be closed?
Thansk in advance!
--
nosy: +francismb
status: pending - open
Changes by Berker Peksag berker.pek...@gmail.com:
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1602742
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
resolution: - duplicate
stage: needs patch - committed/rejected
status: open - pending
superseder: - Regression: Windows-tkinter-idle, unicode, and 0xxx filename
___
Python tracker
Serhiy Storchaka added the comment:
The patch for issue19020 fixes this issue.
--
nosy: +serhiy.storchaka
versions: +Python 3.3, Python 3.4 -Python 3.1, Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1602742
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
stage: - needs patch
type: - behavior
versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.4, Python 2.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1602742
Guilherme Polo [EMAIL PROTECTED] added the comment:
The problem is actually on Tkinter side, not really tcl/tk fault here.
Tkinter should be formatting that text option as {text here} when the
value contains one or more spaces (it is actually fine to use this tcl
formatting when there are no
Guilherme Polo [EMAIL PROTECTED] added the comment:
Uhm, now I see.. Tkinter already formats it correctly, and you shouldn't
be using itemconfigure for this task. If you try it directly in tk, like
this:
canvas .c
.c create text 0 0 -text {a b}
.c itemconfigure 1 -text
You would get something
