You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This patch uses the Tcl object API to convert return
values to Python objects. For boolean, bytearray,
double, int, list, and string objects, the equivalent
Python objects are constructed (Unicode for Tcl
string). For untyped objects, strings are returned. For
all other objects, a Python wrapper object is returned
which supports a tp_str conversion.
I was originally asked to put this on SF for review because
the potential backwards incompatibility in return types.
IDLE seems to work fine with this change, so I expect
incompatibility to come up rarely.
Can I commit this as-is, with the suggestion that
applications that break with this can do
I can't answer that question, since I don't know what's out
in the field. If you don't get response from python-dev,
let's try this and see how it fares during the alpha tests.
loewis commented on Nov 26, 2002
loewismannequin
MannequinAuthor
More actions
Logged In: YES
user_id=21627
Since there were no further comments, committed as
According to some of the Tcl/Tk folks there is a problem with this patch, in
that Tcl objects really *are* strings, and any typing is purely an
implementation speedup shortcut. This showed up when Tkinter got a
floating point value for tcl_version on MacOSX. Details are in bug report bpo-729317.
I'm adding this comment purely to make sure this bit of knowledge doesn't
get lost.
Activity
loewis commentedon Feb 17, 2002
This patch uses the Tcl object API to convert return
values to Python objects. For boolean, bytearray,
double, int, list, and string objects, the equivalent
Python objects are constructed (Unicode for Tcl
string). For untyped objects, strings are returned. For
all other objects, a Python wrapper object is returned
which supports a tp_str conversion.
gvanrossum commentedon Nov 22, 2002
Logged In: YES
user_id=6380
Looks OK in theory.
loewis commentedon Nov 22, 2002
Logged In: YES
user_id=21627
I was originally asked to put this on SF for review because
the potential backwards incompatibility in return types.
IDLE seems to work fine with this change, so I expect
incompatibility to come up rarely.
Can I commit this as-is, with the suggestion that
applications that break with this can do
gvanrossum commentedon Nov 22, 2002
Logged In: YES
user_id=6380
I can't answer that question, since I don't know what's out
in the field. If you don't get response from python-dev,
let's try this and see how it fares during the alpha tests.
loewis commentedon Nov 26, 2002
Logged In: YES
user_id=21627
Since there were no further comments, committed as
Tkinter.py 1.166
NEWS 1.543
_tkinter.c 1.131
jackjansen commentedon May 19, 2003
Logged In: YES
user_id=45365
According to some of the Tcl/Tk folks there is a problem with this patch, in
that Tcl objects really *are* strings, and any typing is purely an
implementation speedup shortcut. This showed up when Tkinter got a
floating point value for tcl_version on MacOSX. Details are in bug report
bpo-729317.
I'm adding this comment purely to make sure this bit of knowledge doesn't
get lost.