Re: Strange Problem with pythonw.exe

2012-06-10 Thread asa

  Hello subscribers,
 
  I've recently encountered a strange problem with Python for Windows.
  I'm using Windows 7 Pro 64 Bit and Python 3.2.3 64 Bit (also tried 32
  bit). The Problem is, that pythonw.exe does not work at all!
  Therefore no IDLE for me... But python.exe runs just fine. I ran
  Process Monitor, which showed some activity for pythonw.exe, but no
  window is coming up.
 
 It is not quite clear what you did here, but if you just run 
 pythonw.exe, you should not see anything, as the 'w' stands for 
 'Windows', 'windowless', or 'with user interaction through a gui brought 
 up by the python program being run'. It make it hard to debug if no gui 
 is being brought up.
 
  The problem isn't restricted to my main python
  installation. I have also tried running portable python and active
  state python. No pythonw.exe of them is working. Reinstallation
  didn't change anything. Windows firewall was deactivated, no
  difference. No firewall-software or any possibilities of blocking
  pythonw.exe. I couldn't find the problem online. My problem was
  triggered by using PyQt. I've loaded an .ui, which did NOT show up. I
  have Ne ver seen IDLE since that crash. Advice anyone?
 
 I take it that IDLE *did* work before using PyQT. If this is correct (I 
 must admit, I hope so), I would ask the author of PyQT whether it or QT 
 does anything to the system that could persist across installs. The most 
 likely change to me would be in the registry. So if it were my machine, 
 I would fire up regedit, back up the registry, search it for 'pythonw', 
 look at the results, and perhaps delete all pythonw entries.
 Then reinstall the core component. You might also try 3.3.0a4, which had 
 additional bug fixes, or go back to something like 3.2.0.
 
 -- 
 Terry Jan Reedy
 

Thank you for your help. I found the problem at some other place. The registry 
tweaks didn't solve it. But I found the hint to look up my .idlerc folder. So 
the problem was entirely IDLE related (yes, it worked before). But it wasnt 
PyQt'S problem, but the mapping of some keyboard command I made. I used the 'ü' 
key (german keyboard), which kept me from using IDLE for 4 days now... Deleting 
the %username%/.idlerc folder got the job done finally!

Arthur J
-- 
http://mail.python.org/mailman/listinfo/python-list


Re: Strange Problem with pythonw.exe

2012-06-10 Thread Terry Reedy

On 6/10/2012 7:39 PM, a...@vorsicht-bissig.de wrote:


Thank you for your help. I found the problem at some other place. The
registry tweaks didn't solve it. But I found the hint to look up my
.idlerc folder. So the problem was entirely IDLE related (yes, it
worked before). But it wasnt PyQt'S problem, but the mapping of some
keyboard command I made. I used the 'ü' key (german keyboard), which
kept me from using IDLE for 4 days now... Deleting the
%username%/.idlerc folder got the job done finally!


I believe there is a patch, either on the tracker or applied since 
3.2.3, to catch .idlerc problems and report to the user rather than quit.


--
Terry Jan Reedy


--
http://mail.python.org/mailman/listinfo/python-list


Strange Problem with pythonw.exe

2012-06-09 Thread asa
Hello subscribers,

I've recently encountered a strange problem with Python for Windows. I'm using 
Windows 7 Pro 64 Bit and Python 3.2.3 64 Bit (also tried 32 bit). The Problem 
is, that pythonw.exe does not work at all! Therefore no IDLE for me... But 
python.exe runs just fine. I ran Process Monitor, which showed some activity 
for pythonw.exe, but no window is coming up. The problem isn't restricted to my 
main python installation. I have also tried running portable python and active 
state python. No pythonw.exe of them is working. Reinstallation didn't change 
anything. Windows firewall was deactivated, no difference. No firewall-software 
or any possibilities of blocking pythonw.exe. I couldn't find the problem 
online. My problem was triggered by using PyQt. I've loaded an .ui, which did 
NOT show up. I have Never seen IDLE since that crash.
Advice anyone?

Regards, 

Arthur
-- 
http://mail.python.org/mailman/listinfo/python-list


Re: Strange Problem with pythonw.exe

2012-06-09 Thread Terry Reedy

On 6/9/2012 10:23 AM, a...@vorsicht-bissig.de wrote:

Hello subscribers,

I've recently encountered a strange problem with Python for Windows.
I'm using Windows 7 Pro 64 Bit and Python 3.2.3 64 Bit (also tried 32
bit). The Problem is, that pythonw.exe does not work at all!
Therefore no IDLE for me... But python.exe runs just fine. I ran
Process Monitor, which showed some activity for pythonw.exe, but no
window is coming up.


It is not quite clear what you did here, but if you just run 
pythonw.exe, you should not see anything, as the 'w' stands for 
'Windows', 'windowless', or 'with user interaction through a gui brought 
up by the python program being run'. It make it hard to debug if no gui 
is being brought up.



The problem isn't restricted to my main python
installation. I have also tried running portable python and active
state python. No pythonw.exe of them is working. Reinstallation
didn't change anything. Windows firewall was deactivated, no
difference. No firewall-software or any possibilities of blocking
pythonw.exe. I couldn't find the problem online. My problem was
triggered by using PyQt. I've loaded an .ui, which did NOT show up. I
have Ne ver seen IDLE since that crash. Advice anyone?


I take it that IDLE *did* work before using PyQT. If this is correct (I 
must admit, I hope so), I would ask the author of PyQT whether it or QT 
does anything to the system that could persist across installs. The most 
likely change to me would be in the registry. So if it were my machine, 
I would fire up regedit, back up the registry, search it for 'pythonw', 
look at the results, and perhaps delete all pythonw entries.
Then reinstall the core component. You might also try 3.3.0a4, which had 
additional bug fixes, or go back to something like 3.2.0.


--
Terry Jan Reedy

--
http://mail.python.org/mailman/listinfo/python-list


Re: problem with pythonw.exe

2009-10-23 Thread Christian Heimes
Martin Shaw wrote:
 I have a tkinter application running on my windows xp work machine and I am
 attempting to stop the console from appearing when the application runs.
 I've researched around and the way to do this appears to be to use
 pythonw.exe instead of python.exe. However when I try to run pythonw.exe
 from the command prompt it simply does nothing. I can't find anything like
 this where I've searched. I've tried reinstalling python. Pythonw.exe
 appears to work when i run it through cygwin however I don't really want to
 use cygwin for this application. Any idea as to what might be the problem?

Windows GUI programs don't have any standard streams. stdin, stdout and
stderr aren't attached so any print statement or traceback isn't shown.
Could this explain the behavior?

Christian
-- 
http://mail.python.org/mailman/listinfo/python-list


Re: problem with pythonw.exe

2009-10-23 Thread Dave Angel

Martin Shaw wrote:

Hi,

I have a tkinter application running on my windows xp work machine and I am
attempting to stop the console from appearing when the application runs.
I've researched around and the way to do this appears to be to use
pythonw.exe instead of python.exe. However when I try to run pythonw.exe
from the command prompt it simply does nothing. I can't find anything like
this where I've searched. I've tried reinstalling python. Pythonw.exe
appears to work when i run it through cygwin however I don't really want to
use cygwin for this application. Any idea as to what might be the problem?

Thanks in advance,

Martin

  






Exactly what program is pythonw executing?  You need to search your PATH 
to see what's on it.  For example, if your PATH has a c:\bat directory 
on it, and in that directory you have a one-line batch file:


   @c:\python26\pythonw.exe

then you're seeing the expected behavior.  You'd need to add a parameter 
to the batch file, probably %*


Or you could be pointing at some other executable.

The other possibility for you is to use the .pyw file association that 
your install probably set up for you.  Rename your main script to have a 
.pyw extension, and then just type it as your command.  To check file 
associations, use assoc and ftype utilities, both standard on Windows XP 
and Vista.


DaveA

--
http://mail.python.org/mailman/listinfo/python-list