Re: [Pythonmac-SIG] "pythonw" in a Unix build

> On 18 Jan 2021, at 18:38, Christopher Barker wrote: > > On Mon, Jan 18, 2021 at 1:34 AM Ronald Oussoren > wrote: > As mentioned on python-dev adding the “pythonw” functionality to the unix > build is not very hard. I expect that integrating with the build syst

Re: [Pythonmac-SIG] "pythonw" in a Unix build

On Mon, Jan 18, 2021 at 4:33 PM Jack Jansen wrote: > it still isn't clear to me _why_ you wouldn’t want to use a framework > build… > on a personal level, it's because the conda folks really want to use a plain vanilla unix build -- and I want things to work with conda. As to why conda wants to

Re: [Pythonmac-SIG] "pythonw" in a Unix build

Christopher, it still isn't clear to me _why_ you wouldn’t want to use a framework build… The whole exercise feels a bit like discussions from 15 years ago, with Unix wizards who wanted MacOS to behave as if it was plain vanilla Unix without all the things Apple changed. And that is much less tr

Re: [Pythonmac-SIG] "pythonw" in a Unix build

On Mon, Jan 18, 2021 at 1:34 AM Ronald Oussoren wrote: > As mentioned on python-dev adding the “pythonw” functionality to the unix > build is not very hard. I expect that integrating with the build system > (Makefile/configure script) will be the hardest part due to introducing > different behavi

Re: [Pythonmac-SIG] "pythonw" in a Unix build

> On 15 Jan 2021, at 06:24, Christopher Barker wrote: > > On Thu, Jan 14, 2021 at 3:14 PM Jack Jansen > wrote: > For example, the brew Python is installed into a framework tucked away deep > in /usr/local/Cellar but you don’t notice this at all: you can just use >

Re: [Pythonmac-SIG] "pythonw" in a Unix build

On Thu, Jan 14, 2021 at 3:14 PM Jack Jansen wrote: > For example, the brew Python is installed into a framework tucked away > deep in /usr/local/Cellar but you don’t notice this at all: you can just > use “python foo.py” and the moment the script does GUI calls it’ll get an > icon in the doc and

Re: [Pythonmac-SIG] "pythonw" in a Unix build

I’m not sure there is a point anymore? For example, the brew Python is installed into a framework tucked away deep in /usr/local/Cellar but you don’t notice this at all: you can just use “python foo.py” and the moment the script does GUI calls it’ll get an icon in the doc and all that. What pr

[Pythonmac-SIG] "pythonw" in a Unix build

Ned suggested I bring this conversation over here from python-dev, so here it is. What I'd like to see done is have the "pythonw" wrapper buildable in an otherwise non-framework build. I *think* there are no real technical show stoppers, but it would take some auto-conf magic, which I am fully un

Re: [Pythonmac-SIG] Pythonw 2.3.5 error on OSX 10.3.9

Kevin Walzer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Michael Glassford wrote: >> When I try to run /usr/local/bin/pythonw2.3, I get the error: >> >> """ >> /usr/local/bin/pythonw2.3: line 2: >> /Library/Frameworks/Python.framework/Versions/2.3/Resources/Python.app/Contents/Ma

Re: [Pythonmac-SIG] Pythonw 2.3.5 error on OSX 10.3.9

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Glassford wrote: > When I try to run /usr/local/bin/pythonw2.3, I get the error: > > """ > /usr/local/bin/pythonw2.3: line 2: > /Library/Frameworks/Python.framework/Versions/2.3/Resources/Python.app/Contents/MacOS/Python: > > No such file o

[Pythonmac-SIG] Pythonw 2.3.5 error on OSX 10.3.9

When I try to run /usr/local/bin/pythonw2.3, I get the error: """ /usr/local/bin/pythonw2.3: line 2: /Library/Frameworks/Python.framework/Versions/2.3/Resources/Python.app/Contents/MacOS/Python: No such file or directory /usr/local/bin/pythonw2.3: line 2: exec: /Library/Frameworks/Python.frame

Re: [Pythonmac-SIG] pythonw vs. python

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

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

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

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

Re: [Pythonmac-SIG] Pythonw and VPython and Fink

> Framework builds of Python can use X11 just fine. I'm not sure > that's the holdup. The holdup is that it hasn't really been ported to OS X, they've just tweaked the Linux/Gnome version enough that you can build it on OS X, as long as you build GTK and friends first, and use X11, and get

Re: [Pythonmac-SIG] Pythonw and VPython and Fink

Dethe Elza wrote: > I think the solution is for VPython to be ported to Aqua instead of > using X11 (so it can use regular OS X Python, not Fink, among other > good things). Framework builds of Python can use X11 just fine. I'm not sure that's the holdup. -- Robert Kern [EMAIL PROTECTED] "

Re: [Pythonmac-SIG] Pythonw and VPython and Fink

On Feb 14, 2006, at 8:58 PM, Dethe Elza wrote: > On 14-Feb-06, at 1:28 PM, Matthias Milczynski wrote: >> I assume that the solution of this problem would be to somehow get a >> fink-based pythonw, but this seems to be not avaiable. >> Can anybody help me with this? > > I think the solution is for

Re: [Pythonmac-SIG] Pythonw and VPython and Fink

On 14-Feb-06, at 1:28 PM, Matthias Milczynski wrote: > I assume that the solution of this problem would be to somehow get a > fink-based pythonw, but this seems to be not avaiable. > Can anybody help me with this? I think the solution is for VPython to be ported to Aqua instead of using X11 (so

Re: [Pythonmac-SIG] Pythonw and VPython and Fink

On Feb 14, 2006, at 1:28 PM, Matthias Milczynski wrote: > I would like to use SPE (cool Python editor) with vpython, that I > installed with fink (unfortunately there is no other possibility > yet). My vpython stuff is located in /sw/lib/python2.4/site-packages/ > visual, but I run SPE with /usr/l

[Pythonmac-SIG] Pythonw and VPython and Fink

Hello, I would like to use SPE (cool Python editor) with vpython, that I installed with fink (unfortunately there is no other possibility yet). My vpython stuff is located in /sw/lib/python2.4/site-packages/ visual, but I run SPE with /usr/local/bin/pythonw2.4. When I try to run any vpytho

Re: [Pythonmac-SIG] pythonw and python with applescript

Thanks, Chris   I will send my simple example to you later on     Zhi Christopher Barker <[EMAIL PROTECTED]> wrote: On Tuesday 13 December 2005 7:24 pm, Zhi Peng wrote:> I would like> to have a small C code and then compile and linked as dynamic library so> that it can be imported by python

Re: [Pythonmac-SIG] pythonw and python with applescript

On Tuesday 13 December 2005 7:24 pm, Zhi Peng wrote: > I would like > to have a small C code and then compile and linked as dynamic library so > that it can be imported by python code as we had in Linux platform. Are you doing exactly the same thing on OS-X and Linux? Are you using distutils to c

Re: [Pythonmac-SIG] pythonw and python with applescript

If part of all code can be compiled as .so library on Mac and also be imported by python, it will be ideal case. As I tried swig utility, it seems it does not work well on Mac. It does not show the error message. I do not know the reason. The compile and ld linker seems fine. I would like to have

Re: [Pythonmac-SIG] pythonw and python with applescript

On Dec 13, 2005, at 4:45 PM, Zhi Peng wrote: > See if I go the right direction. > > On Wed, I will use my old code to build .so file which is run on > Linux. See what happen. > > I used swig and get name.so file and get rid of error message. When > I start python or pythonw and import name >

Re: [Pythonmac-SIG] pythonw and python with applescript

See if I go the right direction.   On Wed, I will use my old code to build .so file which is run on Linux. See what happen.   I used swig and get name.so file and get rid of error message. When I start python or pythonw and import name from command line, it just hang there. It is interesting

Re: [Pythonmac-SIG] pythonw and python with applescript

On Dec 13, 2005, at 3:59 PM, Zhi Peng wrote: > As I tried to make shared dynamic library, ld command shows some > error message > > ld: Undefined symbols: > dyld_stub_binding_helper > > I do not know which lib including this "dyld_stub_binding_helper" > even though I used "nm" to find it. The

Re: [Pythonmac-SIG] pythonw and python with applescript

Hi! Bob   As I tried to make shared dynamic library, ld command shows some error message   ld: Undefined symbols: dyld_stub_binding_helper   I do not know which lib including this "dyld_stub_binding_helper" even though I used "nm" to find it. The list libs that I used is -L/usr/lib -L/usr

Re: [Pythonmac-SIG] pythonw and python with applescript

On Dec 13, 2005, at 1:30 PM, Zhi Peng wrote: > Actually there is only one step away, that is, pythonw and python. > With python, I can import modules by using PyImport_ImportModule > ("name"). But I have to use pythonw since I used appscript. Then I > can not import modules sucessfully with

Re: [Pythonmac-SIG] pythonw and python with applescript

Bob   Actually there is only one step away, that is, pythonw and python. With python, I can import modules by using PyImport_ImportModule("name"). But I have to use pythonw since I used appscript. Then I can not import modules sucessfully with same commands.   If converting C code to python, th

Re: [Pythonmac-SIG] pythonw and python with applescript

You don't have to change it all to Python, you just need to refactor it a bit.  Instead of embeding Python from C, you embed C from Python.  Of course, it's better to prefer Python code because there will be less of it, it's not always a good idea to just throw all the old code away.-bobOn Dec 13,

Re: [Pythonmac-SIG] pythonw and python with applescript

Hi! Bob   What you suggested is right.   The interesting thing is that I have a lot of old c code which will try to call python code. It is true that I can write pure python code and use py2app (I use py2exe on windows) to make an executable. That  will make life easy. But ..   I think tha

Re: [Pythonmac-SIG] pythonw and python with applescript

On Dec 13, 2005, at 12:18 PM, Zhi Peng wrote: > If we use pythonw, then there may be problem in C code to call the > python code with appscript inside because it seems > PyImport_ImportModule("ModuleName") only works with python instead > of pythonw. pythonw is just a shell script. You're

Re: [Pythonmac-SIG] pythonw and python with applescript

First of all, Thanks 'Has"'s help during past months.   If we use pythonw, then there may be problem in C code to call the python code with appscript inside because it seems PyImport_ImportModule("ModuleName") only works with python instead of pythonw.   By the way, I have another question fo

Re: [Pythonmac-SIG] pythonw and python with applescript

Kevin Walzer wrote: >Not sure if appscript modules can be run interactively with the Python >interpreter/shell--has can chime in here. Sure, as long as you use pythonw. An interactive shell can be quite handy when learning your way around an application's object model; appscript's built-in help

Re: [Pythonmac-SIG] pythonw and python with applescript

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zhi Peng wrote: > Hi! All > > I posted a few items in a few days. I think the first > problem I had is that it can not import python module > when I used "from appscrpt import *" inside modue > because appscript need pythonw instead of python. Here >

Re: [Pythonmac-SIG] pythonw and python with applescript

On Dec 13, 2005, at 10:02 AM, Zhi Peng wrote: > I posted a few items in a few days. I think the first > problem I had is that it can not import python module > when I used "from appscrpt import *" inside modue > because appscript need pythonw instead of python. Here > is the error message: -- >

[Pythonmac-SIG] pythonw and python with applescript

Hi! All I posted a few items in a few days. I think the first problem I had is that it can not import python module when I used "from appscrpt import *" inside modue because appscript need pythonw instead of python. Here is the error message:

[Pythonmac-SIG] pythonw and python with applescript

Hi! All I posted a few items in a few days. I think the first problem I had is that it can not import python module when I used "from appscrpt import *" inside modue because appscript need pythonw instead of python. Here is the error message:

Re: [Pythonmac-SIG] pythonw stay open

Christopher Barker wrote: >has wrote: >>CGI's always going to be expensive as it starts a new process for each >>request. And yeah, if it's a GUI process then the overheads will bite even >>more. > >Yes, but it sounded like the OP was getting over a second start-up time. This >is very long, so

Re: [Pythonmac-SIG] pythonw stay open

Ryan Wilcox wrote: >I have a bunch of CGIs that make use of pythonw (+cgiwrap) to allow me >to send AppleEvents (via appscript) to applications on the web server >machine. CGI's always going to be expensive as it starts a new process for each request. And yeah, if it's a GUI process then the o

Re: [Pythonmac-SIG] pythonw stay open

On Wed, Dec 07, 2005 at 06:18:49AM +, Ryan Wilcox wrote: > Hello all, > > I have a bunch of CGIs that make use of pythonw (+cgiwrap) to allow me > to send AppleEvents (via appscript) to applications on the web server > machine. > > Everytime I hit one of these CGIs, pythonw launches a Pyt

[Pythonmac-SIG] pythonw stay open

Hello all, I have a bunch of CGIs that make use of pythonw (+cgiwrap) to allow me to send AppleEvents (via appscript) to applications on the web server machine. Everytime I hit one of these CGIs, pythonw launches a Python application (which makes sense). While this machine is under heavy-is

Re: [Pythonmac-SIG] pythonw

On Mon, 7 Feb 2005 12:37:06 -0500, Bob Ippolito <[EMAIL PROTECTED]> wrote: > > On Feb 7, 2005, at 12:34, Chris Fonnesbeck wrote: > > > > OK, so if I replace the symbolic link from /usr/bin/python to > > /usr/bin/python2.3 with a link to /usr/bin/pythonw2.3, nothing bad > > will happen? I dont envi

Re: [Pythonmac-SIG] pythonw, site-packages, .pth problem

Sorry, the.pth files are evaluated. I was simply too stupid to copy the vtk stuff to the right place. Torsten On Fri, 11 Feb 2005, Torsten Sadowski wrote: > Hi, > > I ran into a namespace conflict between wx2.5.3 and vtk4.4 on Panther > with the Macpython additions. > Analyzing the problem I stu

[Pythonmac-SIG] pythonw, site-packages, .pth problem

Hi, I ran into a namespace conflict between wx2.5.3 and vtk4.4 on Panther with the Macpython additions. Analyzing the problem I stumbled across a strange behaviour. It seems that *.pth files are simply ignored. If that is so, where does pythonw keep its pathes as I did not set a PYTHONPATH? Torst

Re: [Pythonmac-SIG] pythonw

On Feb 7, 2005, at 12:12, has wrote: Bob Ippolito wrote: Would it be possible to keep /usr/bin/python as a full-fledged interpreter while adding to it the ability to automatically start a second interpreter at a known location when needed? "when needed" is ambiguous. You don't know you need it u

Re: [Pythonmac-SIG] pythonw

On Feb 7, 2005, at 12:34, Chris Fonnesbeck wrote: On Sat, 5 Feb 2005 13:35:10 -0500, Bob Ippolito <[EMAIL PROTECTED]> wrote: For running your own scripts and playing around in the terminal, just use pythonw all the time. There is a very slight increase in start-up time, but nothing worth caring ab

Re: [Pythonmac-SIG] pythonw

On Sat, 5 Feb 2005 13:35:10 -0500, Bob Ippolito <[EMAIL PROTECTED]> wrote: > For running your own scripts and playing around in the terminal, just > use pythonw all the time. There is a very slight increase in start-up > time, but nothing worth caring about. > OK, so if I replace the symbolic l

Re: [Pythonmac-SIG] pythonw

On Feb 5, 2005, at 9:55 PM, has wrote: Bob Ippolito wrote: It makes /usr/bin/python depend on another executable at a specific location on the filesystem, Would it be possible to keep /usr/bin/python as a full-fledged interpreter while adding to it the ability to automatically start a second int

Re: [Pythonmac-SIG] pythonw

Bob Ippolito wrote: It makes /usr/bin/python depend on another executable at a specific location on the filesystem, Would it be possible to keep /usr/bin/python as a full-fledged interpreter while adding to it the ability to automatically start a second interpreter at a known location when neede

Re: [Pythonmac-SIG] pythonw

On Feb 5, 2005, at 9:17 PM, has wrote: Bob Ippolito wrote: It is not possible to solve this problem without changing the way Python gets installed (making /usr/bin/python a fork-exec stub or shell script) Any reason for not doing that then? Eliminating this wart would be good. It would break bund

Re: [Pythonmac-SIG] pythonw

Bob Ippolito wrote: It is not possible to solve this problem without changing the way Python gets installed (making /usr/bin/python a fork-exec stub or shell script) Any reason for not doing that then? Eliminating this wart would be good. It would break bundlebuilder's --standalone option, probably

Re: [Pythonmac-SIG] pythonw

On Feb 5, 2005, at 2:26 PM, has wrote: Bob Ippolito wrote: > Are there any plans to remove this apparently unnecessary > dichotomy? It is not possible to solve this problem without changing the way Python gets installed (making /usr/bin/python a fork-exec stub or shell script) Any reason for not

Re: [Pythonmac-SIG] pythonw

Bob Ippolito wrote: > Are there any plans to remove this apparently unnecessary > dichotomy? It is not possible to solve this problem without changing the way Python gets installed (making /usr/bin/python a fork-exec stub or shell script) Any reason for not doing that then? Eliminating this wart

Re: [Pythonmac-SIG] pythonw

As far as I know, other platforms do not have this problem. Windows does. Windows has the idea of subsystems (eg OS/2, Posix, Win32). Pretty much only win32 is used these days. Win32 apps can be marked as console or gui. However console apps can also do gui stuff. So PythonW is used to run gui

Re: [Pythonmac-SIG] pythonw

On Feb 5, 2005, at 12:08 PM, Chris Fonnesbeck wrote: Sorry in advance for what may, in fact, be a naive post, but I am trying to figure out the significance of pythonw on OSX. I know that you need to run pythonw if you intend to use python programs with certain graphical backends, otherwise the UI

[Pythonmac-SIG] pythonw

Sorry in advance for what may, in fact, be a naive post, but I am trying to figure out the significance of pythonw on OSX. I know that you need to run pythonw if you intend to use python programs with certain graphical backends, otherwise the UI becomes unresponsive. Running idle from the command l