[issue17290] pythonw - loading cursor bug when launching scripts

Roundup Robot added the comment: New changeset 5fddaa709d6b by Vinay Sajip in branch '3.3': Closes #17290: Loading cursor now does not persist when launching GUI scripts. http://hg.python.org/cpython/rev/5fddaa709d6b New changeset 0d55fb0217f1 by Vinay Sajip in branch 'default': Closes #17290: M

[issue17290] pythonw - loading cursor bug when launching scripts

Vinay Sajip added the comment: Plus, the standalone launcher has already been updated (the version displayed in the installer and the resource version should be 1.0.1.2): https://bitbucket.org/vinay.sajip/pylauncher/downloads -- ___ Python tracker

[issue17290] pythonw - loading cursor bug when launching scripts

netrick added the comment: Vinay, is there a chance that the fix will be included in 3.3.1? If not, is there a chance to create a python 3.3 installer with the patched pyw.exe? As I know nothing of python packaging so I have no idea how to do it and it would be very handy for me. --

[issue17290] pythonw - loading cursor bug when launching scripts

netrick added the comment: Mark, you are my hero! I can't believe it got fixed that fast. I confirm that for me, the fix works. I just replaced pyw.exe in python33 folder and the bug is gone. -- ___ Python tracker

[issue17290] pythonw - loading cursor bug when launching scripts

Vinay Sajip added the comment: Good catch, Mark! I'll wait for confirmation that your patched pyw.exe works, then make the changes in the Python repository and also update the standalone launcher. -- ___ Python tracker

[issue17290] pythonw - loading cursor bug when launching scripts

Mark Hammond added the comment: If anyone would like to test the fix out, I've put a 32bit pyw.exe with the fix at http://starship.python.net/crew/skippy/downloads/pyw.exe -- ___ Python tracker ___

[issue17290] pythonw - loading cursor bug when launching scripts

Mark Hammond added the comment: The problem is that Explorer displays the IDC_APPSTARTING icon when an app launches, until that app does something ui-ish (eg, creating a window, fetching a windows message). I could reproduce the problem on XP, and pushed a fix for the launcher to https://bit

[issue17290] pythonw - loading cursor bug when launching scripts

netrick added the comment: Of course, the "py.exe" launcher with console (both standalone and from python 3.3) DOES NOT produce the error even when launching with double click. It's only pyw.exe double click thing. -- ___ Python tracker

[issue17290] pythonw - loading cursor bug when launching scripts

netrick added the comment: Well I installed python using standard python 3.3.0.msi from python.org, so maybe there is something wrong with setting registry keys? I downloaded standalone launcher from bitbucket and the results are the same: 1) command line "pyw.exe app.pyw" no bug 2) I assigned

[issue17290] pythonw - loading cursor bug when launching scripts

Changes by Vinay Sajip : -- nosy: +loewis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue17290] pythonw - loading cursor bug when launching scripts

Vinay Sajip added the comment: Does the error occur with the standalone launcher downloadable from BitBucket? The "value not set" for shell\open is not good. -- ___ Python tracker _

[issue17290] pythonw - loading cursor bug when launching scripts

netrick added the comment: Differences: [HKEY_CLASSES_ROOT\Python.CompiledFile\DefaultIcon] @="F:\Python33\DLLs\pyc.ico" [HKEY_CLASSES_ROOT\Python.CompiledFile\shell\open] value not set [HKEY_CLASSES_ROOT\Python.File\DefaultIcon] @="F:\Python33\DLLs\py.ico" [HKEY_CLASSES_ROOT\Python.File\shel

[issue17290] pythonw - loading cursor bug when launching scripts

Vinay Sajip added the comment: The .pys entry needn't be there - I left it in by mistake. -- ___ Python tracker ___ ___ Python-bugs-li

[issue17290] pythonw - loading cursor bug when launching scripts

Vinay Sajip added the comment: Please post, on a machine where the problem is occurring, the contents of the following keys in the registry. What I have shown below is what you should have (allowing for differing locations for Windows): [HKEY_CLASSES_ROOT\.py] @="Python.File" [HKEY_CLASSES_RO

[issue17290] pythonw - loading cursor bug when launching scripts

netrick added the comment: Well I did fresh install of windows xp and encountered it. On the other pc with xp I tried it is also present. I don't know why I encounter this, I must try more PCs. If you have xp, please try if you can reproduce the issue and post your result here. -- __

[issue17290] pythonw - loading cursor bug when launching scripts

Tim Golden added the comment: I can't reproduce this on XP either. I've tried various combinations of .py / .pyw, command line, double-click, etc. and I've not had a single problem. Let's hope someone else can suggest something -- ___ Python tracke

[issue17290] pythonw - loading cursor bug when launching scripts

netrick added the comment: And remember that on the exactly the same computers when I uninstalled python 3.3 and installed python 3.2, everything works flawlessy (because python 3.2 sets .pyw files to open through pythonw.exe). -- ___ Python tracker

[issue17290] pythonw - loading cursor bug when launching scripts

netrick added the comment: I can use assoc command for .py extension but I can't for .pyw. Maybe that's some clue... The strange thing is that explicit "pyw.exe app.pyw" gives no bug, and associating .pyw files to "pyw.exe" gives the bug when double clicking. Honestly I have no idea what's go

[issue17290] pythonw - loading cursor bug when launching scripts

netrick added the comment: So: 1) "assoc .pyw # -> Python.NoConFile" gives an error that it can't find association for .pyw extension 2) opening terminal in proper directory and typing just "app.pyw" gives error that this is not known command I did small test. Using normal (from explorer) "ope

[issue17290] pythonw - loading cursor bug when launching scripts

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 c

[issue17290] pythonw - loading cursor bug when launching scripts

netrick added the comment: My OS is Windows XP so it may be only XP related. So, python 3.3 and my testing: 1) pythonw app.pyw - no bug 2) python app.pyw - no bug 3) pyw app.pyw - no bug 4) py app.pyw - no bug 5) double click on app.pyw - BUG Tested on 2 different computers with exactly the sam

[issue17290] pythonw - loading cursor bug when launching scripts

Changes by Tim Golden : -- nosy: +mhammond, vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue17290] pythonw - loading cursor bug when launching scripts

Tim Golden added the comment: I can't reproduce this running Python 3.3 on Win7. I'll try WinXP later. I'll also add Mark Hammond & Vinay as they implemented the PEP397 loader. -- ___ Python tracker ___

[issue17290] pythonw - loading cursor bug when launching scripts

Tim Golden added the comment: netrick: can you confirm that the same thing occurs when you explicitly run your code via the pyw command. ie when you do this: pyw myprog.pyw Also, what happens when you run: py myprog.pyw ie when you use the Console launcher to launch the .pyw? --

[issue17290] pythonw - loading cursor bug when launching scripts

netrick added the comment: The issue is NOT present in python 3.2. I'm not expert, but given that it work in 3.2 and works in 3.3 using direct "pythonw" command, I'm almost sure it's new windows launcher. Even if I'm wrong, you guys can be sure that the issue appeared in 3.3 so there are only

[issue17290] pythonw - loading cursor bug when launching scripts

netrick added the comment: Well actually it IS a photo, so I think it can remain .jpg (because on print screen there is no cursor). Thanks for the temporary solution, altough I'm not sure if pyside/pygame etc will allow me to change busy cursor too. Is there any chance for this to be fully fix

[issue17290] pythonw - loading cursor bug when launching scripts

Ramchandra Apte added the comment: Advice: anything that's not a photo should be PNG. Temporary fix is to change the cursor see [0] ^0 http://effbot.org/zone/tkinter-busy.htm -- nosy: +Ramchandra Apte ___ Python tracker

[issue17290] pythonw - loading cursor bug when launching scripts

netrick added the comment: I just want to add that it *may* be the issue with the new windows launcher introtuced in 3.3. Because in 2.7 everything runs great and running through "pythonw" command works flawlessy as well. I think it's worth to look into it. --

[issue17290] pythonw - loading cursor bug when launching scripts

Changes by Ned Deily : -- nosy: +brian.curtin, terry.reedy, tim.golden ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue17290] pythonw - loading cursor bug when launching scripts

New submission from netrick: Firstly, just to mention - the issue that I will describe doesn't exist in python 2.7. It is python3 and windows related (python 3.3 for sure, didn't test previous). I also tested it on 2 different PCs (one fresh windows install, second long running with different