On Sat, Jun 06, 2009 at 01:51:29PM -0700, Art Botterell wrote:
.
.
.
> On Jun 6, 2009, at 6/6/09 1:40 PM, Guilherme Polo wrote:
> >Please, include a code that runs and that also contains the
> >described problem.
>
> Not sure how to be sure of meeting your requirements short of posting
> my entire application plus my full Python/Tk/Tcl/OS X stack... and
> shipping you my hardware to boot. (I think you assume the problem is
> in my ap code, but I'm not sure that's the only possibility.)
>
> So I guess I'll just have to muddle through, unless anyone else has
> something constructive to offer.
.
.
.
There's probably a leak in your code. It's possible Tkinter
itself leaks; if that can be confirmed, though, it's almost
certain it'll quickly be fixed.
Pyglet is no guarantee of better results.
Experienced developers generally can find leaks as reproducible
as yours seems to be. Leaks are subtle, though, and Guilherme
is absolutely right in advising you that help depends on your
specific implementation.
You could hire someone to come look at your system and spot the
leak. That probably can be done for a modest charge.
To pursue this on your own, you need to do what Guilherme
describes: make a small code sample. I entirely understand
that, right now, you can only exhibit the symptom in your entire,
properly-hosted-on-the-right-OS, application. To reduce such a
symptom to a small example is a major element of programming
technique. You can practice the skill, or pay someone else to
lead the investigation, or put up with the leak. Realistic
alternatives are few.
There *are* common leak-producing errors with Entry and Label,
but they're hard to describe in the abstract.
_______________________________________________
Tkinter-discuss mailing list
Tkinter-discuss@python.org
http://mail.python.org/mailman/listinfo/tkinter-discuss
