🌐 Mailman 3 December 2005 - Pythonmac-SIG - python.org

Re: [Pythonmac-SIG] SWIG Install problem.
by Louis Pecora Dec. 7, 2005

Dec. 7, 2005

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 heck is going on? Sigh. Thanks for taking the time to help. I'm stumped. louispec% make make all-am depbase=`echo CParse/cscanner.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`; \ if g++ -DHAVE_CONFIG_H -I../Source/Include -I../Source/CParse -I../Source/Include -I../Source/DOH -I../Source/CParse -I../Source/Preprocessor -I../Source/Swig -I../Source/Modules -g -O2 -Wall -W -ansi -pedantic -MT CParse/cscanner.o -MD -MP -MF "$depbase.Tpo" -c -o CParse/cscanner.o CParse/cscanner.c; \ then mv -f "$depbase.Tpo" "$depbase.Po"; else rm -f "$depbase.Tpo"; exit 1; fi In file included from CParse/cscanner.c:18: parser.y:1252: error: parse error before `throw' parser.y:1266: error: parse error before `throw' make[2]: *** [CParse/cscanner.o] Error 1 make[1]: *** [all] Error 2 make: *** [source] Error 2 Exit 2 -- Cheers, Lou Pecora Code 6362 Naval Research Lab Washington, DC 20375 USA Ph: +202-767-6002 email: pecora(a)anvil.nrl.navy.mil

1 0

SWIG Install problem. configure output.
by Louis Pecora Dec. 7, 2005

Dec. 7, 2005

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 you have and they occur at the beginning where, apparently I'm missing some script file of some sort. Lines marked with "*" are lines that have differences from yours. It is pretty easy to see that the only differences are that I have g++ where you have gcc and I have 2.3 where you have 2.4 for Python versions. louispec% ./configure checking build system type... powerpc-apple-darwin7.9.0 checking host system type... powerpc-apple-darwin7.9.0 checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes +/Users/louispecora/Documents/Computer: /Users/louispecora/Documents/Computer: No such file or directory +configure: WARNING: `missing' script is too old or missing checking for gawk... no checking for mawk... no checking for nawk... no checking for awk... awk checking whether make sets $(MAKE)... yes *checking for gcc... g++ checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes *checking whether g++ accepts -g... yes *checking for g++ option to accept ANSI C... none needed checking for style of include used by make... GNU *checking dependency style of g++... gcc3 checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking for bison... bison -y checking for ranlib... ranlib *checking whether g++ and cc understand -c and -o together... yes checking for ar... ar checking maximum warning verbosity option... -Wall -W -ansi -pedantic for C++ -Wall -W -ansi -pedantic for C *checking how to run the C preprocessor... g++ -E checking for egrep... grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for bool... yes checking SO... .bundle checking LDSHARED... cc -bundle -undefined suppress -flat_namespace checking CXXSHARED... cc -bundle -undefined suppress -flat_namespace checking TRYLINKINGWITHCXX... CXXSHARED= g++ -bundle -undefined suppress -flat_namespace checking CCSHARED... checking RPATH... checking LINKFORSHARED... Checking for installed packages. Note : None of the following packages are required to compile SWIG checking for dlopen in -ldl... yes checking for shl_load in -ldld... no checking for swill_init in -lswill... no checking for main in -lieee... no checking for crypt in -lcrypt... no checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include checking for Tcl configuration... found /usr/lib/tclConfig.sh checking for Tcl header files... -isystem /usr/include checking for Tcl library... -framework Tcl checking for python... python *checking for Python prefix... /System/Library/Frameworks/Python.framework/Versions/2.3 *checking for Python exec-prefix... /System/Library/Frameworks/Python.framework/Versions/2.3 *checking for Python version... python2.3 checking for Python lib dir... lib *checking for Python header files... -I/System/Library/Frameworks/Python.framework/Versions/2.3/include/python2.3 -I/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/config *checking for Python library... /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/config checking for perl... perl checking for Perl5 header files... /System/Library/Perl/5.8.1/darwin-thread-multi-2level/CORE checking for Perl5 library... perl.dylib checking for Perl5 compiler options... -g -pipe -pipe -fno-common -DPERL_DARWIN -no-cpp-precomp -fno-strict-aliasing -isystem /usr/local/include checking for java... java checking for javac... javac checking for java include file jni.h... /System/Library/Frameworks/JavaVM.framework/Headers checking for java include file jni_md.h... /System/Library/Frameworks/JavaVM.framework/Headers checking for guile-config... no checking for Guile header files... not found checking for Guile library... not found checking whether Guile's gh_ API works... no checking whether Guile's SCM_ API works... no checking for mzscheme... no checking for mzc... no checking for ruby... ruby checking for Ruby header files... /usr/lib/ruby/1.6/powerpc-darwin7.0 checking for Ruby library... not found... using /usr/lib/ruby/1.6/powerpc-darwin7.0 checking for php... php checking for PHP4 header files... -I/usr/include/php -I/usr/include/php/main -I/usr/include/php/TSRM -I/usr/include/php/Zend checking for Ocaml DL load generator... checking for ocamldlgen... no checking for Ocaml package tool... checking for ocamlfind... no checking for Ocaml compiler... checking for ocamlc... no checking for Ocaml interpreter... checking for ocaml... no checking for Ocaml toplevel creator... checking for ocamlmktop... no checking for Ocaml header files... not found checking for pike... no checking for pike7.6... no checking for pike7.4... no checking for pike7.2... no checking for Pike header files... not found checking for chicken... no checking for csc... no checking for csi... no checking for chicken-config... no checking for mcs... no checking for cscc... no checking for lua... no checking for Lua header files... not found checking for Lua library... not found configure: creating ./config.status config.status: creating Makefile config.status: creating swig.spec config.status: creating Source/Makefile config.status: creating Examples/Makefile config.status: creating Examples/guile/Makefile config.status: creating Examples/GIFPlot/Makefile config.status: creating Examples/GIFPlot/Lib/Makefile config.status: creating Examples/test-suite/chicken/Makefile config.status: creating Examples/test-suite/csharp/Makefile config.status: creating Examples/test-suite/guile/Makefile config.status: creating Examples/test-suite/guilescm/Makefile config.status: creating Examples/test-suite/java/Makefile config.status: creating Examples/test-suite/mzscheme/Makefile config.status: creating Examples/test-suite/ocaml/Makefile config.status: creating Examples/test-suite/perl5/Makefile config.status: creating Examples/test-suite/php4/Makefile config.status: creating Examples/test-suite/pike/Makefile config.status: creating Examples/test-suite/python/Makefile config.status: creating Examples/test-suite/ruby/Makefile config.status: creating Examples/test-suite/tcl/Makefile config.status: creating Examples/test-suite/lua/Makefile config.status: creating preinst-swig config.status: creating Source/Include/swigconfig.h config.status: Source/Include/swigconfig.h is unchanged config.status: executing depfiles commands -- Cheers, Lou Pecora Code 6362 Naval Research Lab Washington, DC 20375 USA Ph: +202-767-6002 email: pecora(a)anvil.nrl.navy.mil

1 0

Re: [Pythonmac-SIG] pythonw stay open
by has Dec. 7, 2005

Dec. 7, 2005

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 overheads will bite even more. I imagine there's various options open to you, e.g. ditch CGI for something a bit more advanced, or put the AE stuff into a faceless GUI process that runs in the background and have your CGI scripts communicate with that via some other form of IPC. Not my area of expertise, so can't advise further, but you should look into it. Another possibility might be to do AEs over mach: I got sent some proof-of-concept code for this a while back and stuck it in the CarbonX.AE extension; assuming you've the latest versions installed it's a one-line tweak in aem.send.send to use it. Usual caveats apply: unofficial, undocumented, untested; subject to bugs, changes, removal; etc, etc. Also, if you're using appscript then make sure you run the terminology server to reduce the time it takes each process to obtain terminology data, or switch to using aem (tip: appscript.aemcodegen makes translating existing appscript code to aem code fairly easy). HTH has -- http://freespace.virgin.net/hamish.sanderson/

1 0

Speed up Python on the Mac?
by Louis Pecora Dec. 7, 2005

Dec. 7, 2005

I am seeking opinions on the best approaches to speed up Python on my Mac (OS X 10.3.9). I know about the profiling and find the bottlenecks approach, but then the choices of what to do are not clear. I have in the past written a few C modules and turned them into importable Python modules, but that was really time consuming and frustrating. I see there are many other approaches (SWIG, Pyrex, Psyco -- some may not be available on the Mac), so I thought I would start here to ask what people in this email list use and recommend. I am looking for something that is an all-in-one package (if possible), easy to use (if possible), and reliable (a must). Does such exist for OS X? I do number crunching/scientific programming using BBEdit and the Apple supplied Python. I do not need to squeeze every last CPU cycle out of my Mac, just get a good speedup ratio (roughly 5X or better). Thanks for any advice. -- Cheers, Lou Pecora Code 6362 Naval Research Lab Washington, DC 20375 USA Ph: +202-767-6002 email: pecora(a)anvil.nrl.navy.mil

8 12

pythonw stay open
by Ryan Wilcox Dec. 7, 2005

Dec. 7, 2005

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-ish load (CPU hogging applications), it feels like launching pythonw takes "too long" (read: a second or two, which is too long in CGI time.) Is it possible to leave pythonw open all of the time, and avoid paying the "launch costs", or is the price for launching pythonw too minimal to notice ("time... says...")? (Meaning that I should try to optimize my system some other way, like moving the CPU hogging process off that machine...) Thanks for your advice on the situation, _Ryan Wilcox

2 1

Re: [Pythonmac-SIG] SWIG Install problem.
by Louis Pecora Dec. 6, 2005

Dec. 6, 2005

Rob Managan wrote: > [cut] > > [mangrove:~/Documents/My_Downloads/swig-1.3.27] managan% make > make all-am > depbase=`echo CParse/cscanner.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`; \ > if gcc -DHAVE_CONFIG_H -I../Source/Include -I../Source/CParse > -I../Source/Include -I../Source/DOH -I../Source/CParse > -I../Source/Preprocessor -I../Source/Swig -I../Source/Modules -g -O2 > -Wall -W -ansi -pedantic -MT CParse/cscanner.o -MD -MP -MF > "$depbase.Tpo" -c -o CParse/cscanner.o CParse/cscanner.c; \ > then mv -f "$depbase.Tpo" "$depbase.Po"; else rm -f "$depbase.Tpo"; > exit 1; fi > depbase=`echo CParse/parser.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`; \ > if gcc -DHAVE_CONFIG_H -I../Source/Include -I../Source/CParse > -I../Source/Include -I../Source/DOH -I../Source/CParse > -I../Source/Preprocessor -I../Source/Swig -I../Source/Modules -g -O2 > -Wall -W -ansi -pedantic -MT CParse/parser.o -MD -MP -MF > "$depbase.Tpo" -c -o CParse/parser.o CParse/parser.c; \ > then mv -f "$depbase.Tpo" "$depbase.Po"; else rm -f "$depbase.Tpo"; > exit 1; fi > depbase=`echo CParse/templ.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`; \ > ... > > I notice that yours has "if g++ -D... " while mine uses gcc there. > Check configure output against mine and see if there are differences. > > I am running OSX 10.3.9 (Panther) so it may be a gcc 3.3 versus 3.4 > problem. > I am running 10.3.9, too. Thanks for giving me something (successful) to compare to. -- Cheers, Lou Pecora Code 6362 Naval Research Lab Washington, DC 20375 USA Ph: +202-767-6002 email: pecora(a)anvil.nrl.navy.mil

1 0

SWIG Install problem.
by Louis Pecora Dec. 6, 2005

Dec. 6, 2005

I'm trying to install the SWIG The README says to treat Mac OS X like a Unix (makes sense) and do the following, % ./configure % make % make install ./configure seemed to run ok. No errors that I could see in the long print out. When I try the first make I get, louispec% make make all-am depbase=`echo CParse/cscanner.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`; \ if g++ -DHAVE_CONFIG_H -I../Source/Include -I../Source/CParse -I../Source/Include -I../Source/DOH -I../Source/CParse -I../Source/Preprocessor -I../Source/Swig -I../Source/Modules -g -O2 -Wall -W -ansi -pedantic -MT CParse/cscanner.o -MD -MP -MF "$depbase.Tpo" -c -o CParse/cscanner.o CParse/cscanner.c; \ then mv -f "$depbase.Tpo" "$depbase.Po"; else rm -f "$depbase.Tpo"; exit 1; fi In file included from CParse/cscanner.c:18: parser.y:1252: error: parse error before `throw' parser.y:1266: error: parse error before `throw' make[2]: *** [CParse/cscanner.o] Error 1 make[1]: *** [all] Error 2 make: *** [source] Error 2 Exit 2 This leaves me baffled. Anyone know what's wrong? I checked and the Mac uses the GNU make as required. -- Cheers, Lou Pecora Code 6362 Naval Research Lab Washington, DC 20375 USA Ph: +202-767-6002 email: pecora(a)anvil.nrl.navy.mil

2 1

Converting to AppleEvents
by Brian Ray Dec. 6, 2005

Dec. 6, 2005

Hi All: 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 AppleEvents. Any sample codes of something similar? There seems to be more than one approach. Also, I do not mind keeping as an AppleScript in a triple quoted string, but I am onsure how this is done. I am trying to learn how to handle all my communication between Mach- O applications and Python2.3 with AppleEvents, although I do not know where to get started. Are there any tutorials on this topic? I do not want to use any helper modules because I also must stick with just Python2.3. Thanks in Advance. Brian Ray http://brianray.chipy.org

1 0

Fwd: Preferred IDE
by Jeffrey E. Forcier Dec. 6, 2005

Dec. 6, 2005

Oops, Jerry forgot to send his original email to the list, and thus my Reply-All didn't really do anything :) Forwarding. Begin forwarded message: > From: "Jeffrey E. Forcier" <jforcier(a)strozllc.com> > Date: November 29, 2005 10:48:32 AM EST > To: lanceboyle(a)bluebottle.com > Subject: Re: [Pythonmac-SIG] Preferred IDE > > I don't have it installed anymore, but I tried TextWrangler a while > ago; if memory serves it had the same lack of auto-indent that > XCode has. Certainly it was something along those lines, something > preventing me from "properly" using it for Python, which is why I'm > not using it now. I also seem to remember BBEdit not having that > issue for some reason, but it wasn't worth the price tag for that > one tweak. > > Other than whatever that issue was, though, TextWrangler/BBEdit is > an *excellent* editor, so be sure to try it out yourself (this > directed at Jerry and the OP) before dismissing it. > > Regards, > Jeff > > On Nov 28, 2005, at 10:23 PM, lanceboyle(a)bluebottle.com wrote: > >> Can someone compare TextMate with BBEdit and/or the free version >> of BBEdit, Text Wrangler? Either as a Python editor or otherwise? >> >> Jerry >

7 9

Re: [Pythonmac-SIG] Speed up Python on the Mac?
by Louis Pecora Dec. 6, 2005

Dec. 6, 2005

Christopher Barker wrote: > Louis Pecora wrote: > >> Christopher Barker wrote: > > >> Yeow, Chris, you really have a lot to say about what I'm interested >> in. Thanks very much! > > > That's because I'm in the same boat. I keep bouncing back and forth > between the approaches, because it's hard to find one that does > everything well. At the moment, I think I'm going with SWIG. I found > some typemaps (what SWIG uses to translate for Python types to C > types) for Numeric arrays that I want to use. I use Numeric a lot. Where are those typemaps? Por favor. :-) > > I'm going with SWIG because I want to wrap a couple existing > libraries, and one that is under development now, and we need to use > from both C++ and Python. If it were just me, I'd dump C++ for primary > app development (like you're working on), and just write Python for > anything not computationally intensive. But it's not up to me, and > folks here are distrustful of anything "new". At NOAA? Isn't that a research place? Sheeze. You think they'd want you looking for new stuff. > > If I didn't need to use the same libs from C++ and Python, and was > more comfortable with C++ I'd probably give Boost::python a try. Or > Pyrex. It depends on whether you see yourself writing just the inner > loops in C, where pyrex would be an excellent choice, or writing a > full lib with classes and all that, where Boost::Python would probably > be a better option. I tried installing the Boost libraries and got hung up. That was for another project where I wanted to use someone elses code for n-ary search tress, but it required boost. Never did get it to work. > > I'd like to hear how things go for you. Particularly if you use SWIG, > we could probably help each other out. > Ya got a deal. I'm going to look hard at SWIG right now. Thanks. -- Cheers, Lou Pecora Code 6362 Naval Research Lab Washington, DC 20375 USA Ph: +202-767-6002 email: pecora(a)anvil.nrl.navy.mil

1 0