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
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
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
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
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
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) open
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 going
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
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
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\shell
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
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 rep
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 rep...@bugs.python.org
http
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
New submission from netrick:
On both Python 2 or 3, when you have GUI app (for example something in pygame
or pyside or tk), when you launch it on Windows it takes about 4-6 seconds to
display the Window for the first run. The next runs are faster, but only untill
you reboot the PC
netrick added the comment:
The simplest way to reproduce it is:
1) Reboot your PC
2) Launch IDLE (pre-installed with Python)
3) Look how long it takes to launch and then compare that with instant launch
on Linux
--
___
Python tracker rep
16 matches
Mail list logo
