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.

classification
Title: ConnectRegistry blocks all threads
Type: Stage:
Components: Windows Versions: Python 2.4
process
Status: closed Resolution: accepted
Dependencies: Superseder:
Assigned To: Nosy List: larslj, loewis
Priority: normal Keywords: patch

Created on 2006-03-12 08:40 by larslj, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
_winreg.diff larslj, 2006-03-12 08:40 Diff for _winreg.c
Messages (2)
msg49717 - (view) Author: Lars L (larslj) Date: 2006-03-12 08:40
ConnectRegistry might take quite some time when
connecting to a remote machine (especially if it's not
responding). It should be possible to run other threads
while waiting for this call to return. I notice that
some registry calls are enclosed by Py_*_ALLOW_THREADS
pairs while some aren't, is there any reason for this?

The patch adds Py_*_ALLOW_THREADS around the call to
RegConnectRegistry in PC/_winreg.c
msg49718 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2006-07-24 10:33
Logged In: YES 
user_id=21627

Thanks for the patch. Committed as r50795.
History
Date User Action Args
2022-04-11 14:56:15adminsetgithub: 43020
2006-03-12 08:40:17larsljcreate