RetroSearch Browse

Mon Aug 16 23:19:07 CEST 2004 · https://mail.python.org/pipermail/python-dev/2004-August/047902.html

On Mon, Aug 16, 2004, Bob Ippolito wrote:
> On Aug 15, 2004, at 11:59 PM, Aahz wrote:
>>On Sun, Aug 15, 2004, Bob Ippolito wrote:
>>>
>>>Many platform GUIs require that all or most all GUI activities be
>>>consolidated to one and only one thread.  I don't think any of them
>>>'care' if another thread is also running, but it can't communicate
>>>directly with the GUI.
>>
>>That's true, but it also applies to other external resources, such as
>>files.
> 
> Maybe I don't understand what you're saying.. but I don't know any 
> platform that forces you to work with files from one and only one 
> specific thread.  But I definitely do know at least one platform where 
> you may only perform most GUI operations from the main thread of 
> execution.

For any one file handle, you use only one thread.  It just happens in
the case of GUIs that there is only one GUI handle.
-- 
Aahz (aahz at pythoncraft.com)           <*>         http://www.pythoncraft.com/

"To me vi is Zen.  To use vi is to practice zen.  Every command is a
koan.  Profound to the user, unintelligible to the uninitiated.  You
discover truth everytime you use it."  --reddy at lion.austin.ibm.com

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2004-August/047902.html below:

[Python-Dev] Threading in the Standard Library Tour Part II