Message 18027 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Recipients
Author	kbk
Date	2005年02月04日.04:16:01
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to

Content
Logged In: YES user_id=149084 Michiel de Hoon's comments re this Bug on python-dev: http://mail.python.org/pipermail/python-dev/2005-January/050895.html In IDLE there are two processes. One runs the GUI and communicates with the second via the socket interface. The subprocess has two threads: MainThread, which runs the user code, and SocketThread, which monitors the socket interface. SocketThread communicates with MainThread via two Queue objects and several global flags which are involved in shutting down the subprocess. So it's the subprocess (run.py) MainThread that should call PyOS_InputHook. See Patch 989712. Noam Raphael is trying to hook in tkinter's mainloop. This should all be solved together. Putting it back in IDLE for now so I can keep an eye on it.

Content

Logged In: YES 
user_id=149084
Michiel de Hoon's comments re this Bug on python-dev:
http://mail.python.org/pipermail/python-dev/2005-January/050895.html
In IDLE there are two processes. One runs the GUI and
communicates with the second via the socket interface. The
subprocess has two threads: MainThread, which runs the user
code, and SocketThread, which monitors the socket interface.
SocketThread communicates with MainThread via two Queue
objects and several global flags which are involved in shutting
down the subprocess.
So it's the subprocess (run.py) MainThread that should call
PyOS_InputHook.
See Patch 989712. Noam Raphael is trying to hook in
tkinter's mainloop. This should all be solved together.
Putting it back in IDLE for now so I can keep an eye on it.

History
Date	User	Action	Args
2007年08月23日 14:16:34	admin	link	issue798058 messages
2007年08月23日 14:16:34	admin	create

homepage