Message81021
| Author |
gpolo |
| Recipients |
gpolo |
| Date |
2009年02月03日.01:04:43 |
| SpamBayes Score |
4.885996e-10 |
| Marked as misclassified |
No |
| Message-id |
<1233623088.62.0.412008570682.issue5136@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Hi, I'm going to try explaining in short why I think each of these
functions in _tkinter could be marked as deprecated and then removed on
2.8 (if it is decided to do it) and 3.1.
globalcall: It is not used anywhere in tkinter. It was abandoned, and
doesn't work in the same situations where "call" would work (with
threads). It doesn't care about converting the result to a proper python
object -- it is always a string (another result of the abandonment).
"call" already works in the Tcl global space, because it needs to do so
(see issue1581476). Even tcl 8.2 says Tcl_GlobalEval (the root of
"globalcall") is old and deprecated.
merge: globalcall depends on merge, but removing globalcall makes merge
obsolete. It is not used by tkinter either. Searching for "tk.merge" on
google codesearch returns a single result dating back python 1.1!
globaleval: Uses Tcl_GlobalEval too. I haven't seen it being used,
instead I always see eval being used. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2009年02月03日 01:04:50 | gpolo | set | recipients:
+ gpolo |
| 2009年02月03日 01:04:48 | gpolo | set | messageid: <1233623088.62.0.412008570682.issue5136@psf.upfronthosting.co.za> |
| 2009年02月03日 01:04:46 | gpolo | link | issue5136 messages |
| 2009年02月03日 01:04:44 | gpolo | create |
|