Mailing List Archive

[issue5136] Deprecating (and removing) "globalcall", "merge" and "globaleval"
New submission from Guilherme Polo <ggpolo@gmail.com>:

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.

----------
components: Tkinter
messages: 81021
nosy: gpolo
severity: normal
status: open
title: Deprecating (and removing) "globalcall", "merge" and "globaleval"
versions: Python 2.7, Python 3.0

_______________________________________
Python tracker <report@bugs.python.org>
<http://bugs.python.org/issue5136>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com