Re: [Pythonmac-SIG] SWIG Install problem.

Rob Managan wrote: > Since crazy things happen I will ask. I assume that you can run gcc > from the command line? Yes. Just tried it. > Next question. What shell are you running? Mine is set to tcsh but > newer Macs tend to run bash. I typed "shell" and it came back: tcsh: shell: Command no

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] SWIG Install problem.

Christopher Barker wrote: >David M. Cooke wrote: > > >>Experience has shown that compiling Scipy with gcc 4.0 on a Mac doesn't >>work (various really annoying problems with how Fortran libraries end up >>being linked and so on). So it's suggested that you use 3.3. >> >> > >There is the same

Re: [Pythonmac-SIG] SWIG Install problem.

Rob, Here is the output of the 'make' command after my ./configure command. Again the only difference from your successful output in the beginning is my output shows g++ being used in place of gcc for you. But then in line 5 (I think I counted right) an error of some type occurs. What the he

[Pythonmac-SIG] SWIG Install problem. configure output.

Rob, Here is the output of my ./configure command for SWIG Install. There are some differences from your successful ouput. Not sure you want to see all this, but if you have the time here are where the differences in our configure output are. Lines marked with "+" are in addition to lines yo

Re: [Pythonmac-SIG] SWIG Install problem.

David M. Cooke wrote: > Experience has shown that compiling Scipy with gcc 4.0 on a Mac doesn't > work (various really annoying problems with how Fortran libraries end up > being linked and so on). So it's suggested that you use 3.3. There is the same problem with Fedora Core4, also using gcc 4.*,

Re: [Pythonmac-SIG] Converting to AppleEvents

On Wed 2005-12-07, at Wed 2005-12-07T07:52 AM, Brian Ray wrote: [snipped] > This seems to work well for now. However, is there a way to have > os.system() wait till it's finished? In other words how to I get > the osascript tool to not return until the script has actually > finished. You p

Re: [Pythonmac-SIG] Converting to AppleEvents

Thanks for your guidance. I will play with all three and see where it gets me.Also, with:On Dec 7, 2005, at 5:57 AM, has wrote:1. Execute AppleScript code via os.system() and osascript: os.system(''' osascript -e 'with timeout of 3600 seconds tell application "TextEdit" get name end tell

Re: [Pythonmac-SIG] Converting to AppleEvents

Brian Ray wrote: >I have an AppleScript I am calling with os.system(): > > with timeout of 3600 seconds > tell application "MyApp" > reload startup > end tell > end timeout > >I am interested in various methods to convert this to AppleE

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] SWIG Install problem.

David M. Cooke wrote: >On Tue, Dec 06, 2005 at 05:41:21PM -0500, Louis Pecora wrote: > > >>Rob Managan wrote: >> >> >> >>>PS the command to switch to gcc 3.3 seems to be >>> >>>'sudo gcc_select 3.3' >>> >>>Not sure if you had to do this with scipy or not. >>> >>> >>H... I don't kno

Re: [Pythonmac-SIG] Speed up Python on the Mac?

On Dec 6, 2005, at 6:08 PM, Christopher Barker wrote: > Have I got them all? I hope this helps. > A fairly esoteric one: pycaml. Note that I have not yet tried pycaml. It is claimed to allow Ocaml libraries to be used from Python, and vice versa. Anyone have an