Re: [Pythonmac-SIG] pythonw vs. python

2006-02-20 Thread Bob Ippolito
On Feb 20, 2006, at 1:22 PM, Ronald Oussoren wrote: > > On 20-feb-2006, at 19:51, Bob Ippolito wrote: > >> >> On Feb 20, 2006, at 9:56 AM, Ronald Oussoren wrote: >> >>> I've been thinking a little about pythonw vs. python. The former is >>> needed because on OSX any API that needs a connection to

Re: [Pythonmac-SIG] pythonw vs. python

2006-02-20 Thread Ronald Oussoren
On 20-feb-2006, at 19:51, Bob Ippolito wrote: > > On Feb 20, 2006, at 9:56 AM, Ronald Oussoren wrote: > >> I've been thinking a little about pythonw vs. python. The former is >> needed because on OSX any API that needs a connection to the window >> server (anything that uses a native GUI and some

Re: [Pythonmac-SIG] pythonw vs. python

2006-02-20 Thread Bob Ippolito
On Feb 20, 2006, at 9:56 AM, Ronald Oussoren wrote: > I've been thinking a little about pythonw vs. python. The former is > needed because on OSX any API that needs a connection to the window > server (anything that uses a native GUI and some other calls) need to > be in an application bundle. py

[Pythonmac-SIG] pythonw vs. python

2006-02-20 Thread Ronald Oussoren
I've been thinking a little about pythonw vs. python. The former is needed because on OSX any API that needs a connection to the window server (anything that uses a native GUI and some other calls) need to be in an application bundle. pythonw is a program that can be placed anywhere on the