executing a script with pythonw (2.2.1) on win98
results in a console window being visible.  I reverted
my application to Python 2.1.1 and it works fine. 

pythonw works okay on WinXP with 2.2.1 though.

Logged In: YES 
user_id=31435

Please give a specific, short example.  For example, if I 
double-click on this file from Explorer under Win98, using 
2.2.1, it plays the sound but no console window opens:

C:\Python22>type example.pyw
import winsound
winsound.Beep(3000, 1000)

C:\Python22>

What happens when you try that?  If a console window does 
pop up, check the your .pyw file assocation -- you may have 
damaged it.  .pyw (Python File (no console))'s Open action 
should be associated to

C:\PYTHON22\pythonw.exe "%1" %*

or to wherever you installed Python 2.2.1.

    

Logged In: YES 
user_id=52126

This works as you suggest.  I have actually managed to get
this problem with 2.1.1 as well now.  I think that the
problem is with GTK when a g_message or g_warning is issued,
it causes the console to open.  The console doesn't actually
appear right away, only when it gets to the g_message or
g_warning.  Any output that would have appeared before that
is missing, but any output after it does appear ( I think). 

I'm using pygtk0.6.6 to write a GTK-based python app, but
there's lots of C code too.

I will look in glib and see if I can find out what it might
be trying to do ... the unfortunate side effect of this is
that I doubt I can get you a short example unless you are
set up with pygtk.  I could provide binaries though ... 

Logged In: YES 
user_id=52126

it appears that glib forces a console window open under
windows, although I am not sure why this doesn't happen on
WinXP.

I am assuming you will mark as invalid?

Logged In: YES 
user_id=31435

Thanks for the followup!  Unless you can dream up a reason 
for believing this is a bug in the Python core, I'm going to 
close this as 3rdParty.  pythonw doesn't open a console, 
but it can't prevent other code from opening consoles.  If 
pygtk or GTK are opening console windows, and that's 
inappropriate, you'll have to file a report with their 
developers (pygtk and GTK aren't part of the Python core, 
so their maintainers won't even see a report *here*).

Logged In: YES 
user_id=31435

Since this has been traced to GTK, and we don't develop 
that code, I'm closing this as 3rdParty and WontFix.  I 
appreciate your pesistence in tracking this down!  It helps 
us when we get a clear resolution.  I'm just sorry it doesn't 
help you too <wink>.