python-mtTkinter-0.4-1.fc17 RPM for noarch

From ATrpms Stable packages for f17 i386

Although Tkinter is technically thread-safe
(assuming Tk is built with --enable-threads),
practically speaking there are still problems when used in multithreaded
Python applications.  The problems stem from the fact that the _tkinter
module attempts to gain control of the main thread via a polling technique
when processing calls from other threads.  If it succeeds, all is well.
If it fails (i.e., after a timeout), the application receives an exception
with the message: "RuntimeError: main thread is not in main loop".
There is no way to tell when this might happen, so calling Tk routines
from multiple threads seems to be problematic at best.

The mtTkinter module solves this problem by modifying some Tkinter
module definitions (in memory). The modified code intercepts
out-of-thread Tkinter calls and marshals them through a queue which
is read by an 'after' event running periodically in the main loop.
This is similar to the technique used in many other platforms
(e.g., .NET's InvokeRequired/Invoke mechanism).
The technique used in mtTkinter is exception-safe as well,
marshaling exceptions through a response queue back to the caller's thread.

Provides

• python-mtTkinter

Requires

• python(abi) = 2.7
• rpmlib(CompressedFileNames) <= 3.0.4-1
• rpmlib(FileDigests) <= 4.6.0-1
• rpmlib(PayloadFilesHavePrefix) <= 4.0-1
• tkinter
• rpmlib(PayloadIsXz) <= 5.2-1

License

GPLv3+

Changelog

* Thu Jan 13 2011 Paulo Roma <roma@lcg.ufrj.br> 0.4-1
  - Updated to 0.4
  - Changed license.
* Sat Oct 23 2010 Paulo Roma <roma@lcg.ufrj.br> 0.3-2
  - Added BR python-devel.
* Mon Feb 01 2010 Paulo Roma <roma@lcg.ufrj.br> 0.3-1
  - Initial spec file.

Files

/usr/lib/python2.7/site-packages/mtTkinter.py
/usr/share/doc/python-mtTkinter-0.4
/usr/share/doc/python-mtTkinter-0.4/clock-bezier.py
/usr/share/doc/python-mtTkinter-0.4/gpl.txt
/usr/share/doc/python-mtTkinter-0.4/lgpl.txt

Generated by rpm2html 1.8.1

Fabrice Bellet, Tue Jul 9 09:01:13 2024