Wheel-reinvention with Python

[Cliff Wells]

On Sun, 2005-07-31 at 10:07 -0700, Kay Schluehr wrote:

> Some other people already abandoned Python not for the worst reasons:
> 
> http://www.kevin-walzer.com/pivot/entry.php?id=69

Being a developer requires not only a bit of brains, but quite a bit of
tenacity as well.  Apparently Kevin lacks the second.

> My objection with wrappers around wrappers around wrappers is that I
> have no hope ever watching the ground. If some error occurs, which
> layer has to be addressed? Which developing group is reponsible? My own
> or that of team A, team B, team C ... ? The baroque concept is
> repulsive to me and only acceptable in case of legacy code that gets
> wrapped around old one and is dedicated to substitute it continously.

Of course, Tkinter is still a wrapper around a third party library (Tk)
borrowed from a different language (Tcl) and written again in a third
language (C), much the same as wxPython.  

Your concerns are valid in a theoretical sense, but in practice make
little difference.  If you are using Tkinter and it exposes a bug in Tk,
then you report to the Tkinter maintainers and they will get it fixed.
The same can be said for wxPython.  Robin Dunn is a wxWidgets developer
and if wxPython exposes a bug in wxWidgets, then he will be responsible
for getting that bug fixed.

As an aside, at one time, Tkinter required that Tcl be installed (and
used) in order to interface with Tk.  This is no longer the case.  Tk
has been abstracted into a standalone library (quite some time ago,
actually) and Python uses it pretty much the same way Tk does.

Regards,
Cliff

-- 
cliff at develix.com
http://www.develix.com :: Web applications and hosting :: Linux, PostgreSQL and Python specialists ::