Tim Golden added the comment: Things may be a little more complicated, because one of two distinct mechanisms may be invoked to determine what to run when double-clicking: an Explorer-based mechanism, and a non-Explorer one. AFAICT, the former falls back to the latter.
To check the latter, the command-line you used earlier: assoc .pyw # -> Python.NoConFile ftype Python.NoConFile # -> whatever path To check the former, there's a registry key which escapes me at the moment but wouldn't be too hard to find. Obviously there's no reason why either should cause a delay, unless you've previously done something obscure like associate .pyw files with a network-based copy of Python or something. To see the non-Explorer association in action, open a command shell in the appropriate directory, and just start the program with: app.pyw (ie without specifying a program). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17290> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
