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

anyone tried to import module from c coe?
by Zhi Peng Dec. 12, 2005

Dec. 12, 2005

Hi All It seems to me it is very strange that it can not import the module that is in python from C code. The sys.path is correct. What else did I miss? I linked obj with python library. Thanks Zhi __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

Re: [Pythonmac-SIG] import problems
by Zhi Peng Dec. 12, 2005

Dec. 12, 2005

Thanks Ronald and everyone. My OS is Tiger. This shows me that my Python installation or default has been changed or something is missing for sure. It is strange for me to see this type of results. Regards Zhi --- Ronald Oussoren <ronaldoussoren(a)mac.com> wrote: > > On 12-dec-2005, at 19:30, Zhi Peng wrote: > > > Hi! All > > > > If you use MacPython2.3 on MAc, please try the > > following code to see if you can get > "StringModule" > > imported. > > This works for me, run see the attached zipfile for > the code I used. > The only change I made was an additional printf to > demonstrate that > the module is indeed imported by print its repr(). > > This is on OSX 10.4.3. > > BTW. I had to reformat the makefile and C code > because those got > mangled along the way, I prefer to include complete > code examples in > an archive. > > Ronald > > > > > > > > //=============================StringModule.py=========== > > #!pythonw > > > > import os > > > > class Module1: > > def __init__(self): > > self.var1= 9 > > def method1(self): > > self.var1=10; > > > > > > > > > > > > //========================= makefile > > ==================== > > YLIB = > > > > > > PYINC=-I./ -I/usr/include -I/usr/include/python2.3 > > LIBS =-L/usr/lib -ldl -lm -lpython > > > > OPTS= -Wall -Wstrict-prototypes > > > > PROGRAM=ScriptSupport > > ScriptSupport::ScriptSupport.o > > gcc -g ScriptSupport.o $(LIBS) $(PYLIB) -o > > ScriptSupport > > ScriptSupport.o:ScriptSupport.c > > gcc -g ScriptSupport.c -c $(PYINC) $(OPTS) > -o > > ScriptSupport.o > > clean: > > rm -f $(PROGRAM) *.o core > > > > > > > > > > > > //================ ScriptSupport.c > > ======================== > > > > #include <Python.h> > > > > #define FALSE 0 > > #define TRUE 1 > > > > int main(void) > > { > > PyObject *myMod=NULL; > > > > > > Py_Initialize(); > > > > PyRun_SimpleString("import sys \n"); > > > > > PyRun_SimpleString("sys.path.append('.\')\n"); > > PyRun_SimpleString("print sys.path \n"); > > > > //#myMod=PyImport_ImportModule("wave"); > > > > > myMod=PyImport_ImportModule("StringModule"); > > if(!myMod) { printf("cannot import > > StringModule wave\n"); return TRUE; } > > > > Py_Finalize(); > > > > return 0; > > } > > > > > > __________________________________________________ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam > protection around > > http://mail.yahoo.com > > _______________________________________________ > > Pythonmac-SIG maillist - > Pythonmac-SIG(a)python.org > > > http://mail.python.org/mailman/listinfo/pythonmac-sig > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 3

import problems
by Zhi Peng Dec. 12, 2005

Dec. 12, 2005

Hi! All If you use MacPython2.3 on MAc, please try the following code to see if you can get "StringModule" imported. //=============================StringModule.py=========== #!pythonw import os class Module1: def __init__(self): self.var1= 9 def method1(self): self.var1=10; //========================= makefile ==================== YLIB = PYINC=-I./ -I/usr/include -I/usr/include/python2.3 LIBS =-L/usr/lib -ldl -lm -lpython OPTS= -Wall -Wstrict-prototypes PROGRAM=ScriptSupport ScriptSupport::ScriptSupport.o gcc -g ScriptSupport.o $(LIBS) $(PYLIB) -o ScriptSupport ScriptSupport.o:ScriptSupport.c gcc -g ScriptSupport.c -c $(PYINC) $(OPTS) -o ScriptSupport.o clean: rm -f $(PROGRAM) *.o core //================ ScriptSupport.c ======================== #include <Python.h> #define FALSE 0 #define TRUE 1 int main(void) { PyObject *myMod=NULL; Py_Initialize(); PyRun_SimpleString("import sys \n"); PyRun_SimpleString("sys.path.append('.\')\n"); PyRun_SimpleString("print sys.path \n"); //#myMod=PyImport_ImportModule("wave"); myMod=PyImport_ImportModule("StringModule"); if(!myMod) { printf("cannot import StringModule wave\n"); return TRUE; } Py_Finalize(); return 0; } __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

universal python framework?
by William Kyngesburye Dec. 10, 2005

Dec. 10, 2005

I'm starting to build universal binaries for a bunch of 'nix stuff, some of which have python bindings/extensions. Has anyone looked at a universal Python framework? I'd hate to have to step backwards to Apple's included Python framework for that, but I may have to. ----- William Kyngesburye <kyngchaos(a)kyngchaos.com> http://www.kyngchaos.com/ "Mon Dieu! but they are all alike. Cheating, murdering, lying, fighting, and all for things that the beasts of the jungle would not deign to possess - money to purchase the effeminate pleasures of weaklings. And yet withal bound down by silly customs that make them slaves to their unhappy lot while firm in the belief that they be the lords of creation enjoying the only real pleasures of existence.... - the wisdom of Tarzan

4 6

import problems
by Zhi Peng Dec. 9, 2005

Dec. 9, 2005

Hi! All When I have module say module.py with sentance like #!pythonw import os from appscript import * and then import from terminal say pythonw, it show me error or warning message /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-packages/aem/send/errors.py:5: DeprecationWarning: Non-ASCII character '\x80' in file /System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/plat-mac/macerrors.py on line 326, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details import macerrors But if I erased "from appscript import *" then it will be fine. I think there is problem in appscript Any advice or suggestion? Thanks Zhi __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 4

Re: [Pythonmac-SIG] Solution to some SWIG Install problems on Mac OS X
by Henning.Ramm＠mediapro-gmbh.de Dec. 9, 2005

Dec. 9, 2005

>(3) running 'make install' would not work since I had no permission to >write in some directories. I don't fully understand this since >I am the >admin and I was running logged in as such, but to no avail. > Solution: run this as > >sudo make install > >type in the password and you're off. An admin user is not root, and it's better this way; it's far less a security issue if you can 'get root' at every time with sudo than if you would run everything constantly as root (or an admin user with root permissions). Greetlings, HR

1 0

Re: [Pythonmac-SIG] Converting to AppleEvents
by has Dec. 8, 2005

Dec. 8, 2005

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 AppleEvents. >Any sample codes of something similar? There seems to be more than >one approach. > >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. Any particular reason for that? e.g. If it's distribution worries, use py2app to build an application bundle with all dependencies included. Standard options: 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 end timeout' ''') Slow, inefficient, and lowest-common-denominator approach, but if speed isn't an issue and you don't need to do anything complex then it'll do the job. 2. Use the low-level Carbon.AE extension, which provides a minimal wrapper around the Apple Event Manager API. See Apple's site for AEM documentation. Expect to write lots and lots of code this way; not much fun at all. 3. Attempt to use Python's aetools/aetypes modules (I think you can forget about gensuitemodule: I've tried it under 10.4 with no success and assume it is now completely senile): #!/usr/bin/env pythonw from aetools import * from aetypes import * te = TalkTo(signature='ttxt', start=1) print te.send('core', 'getd', {'----':ObjectSpecifier('prop', 'prop', 'pnam')})[1] Not much fun either. Documentation is minimal, and figuring out how it works will require background knowledge of Apple events and the Apple Event Manager. You'll probably need to spend time troubleshooting bugs and omissions as well (these modules predate OS X and haven't been maintained in years) and the code is less than pleasant. I really would recommend against trying #2 or #3 as they will only make you miserable. Use #1 for basic tasks, but for anything complex you should consider biting the bullet and using appscript or aem (see my site). The latest version of appscript includes an introduction to application scripting and a tutorial, and it's miles ahead of all of the above. Even if you do have to rig up your own solution in the end, you'll learn a lot more by taking aem apart and studying it than trying to figure this stuff out any other way. HTH has http://freespace.virgin.net/hamish.sanderson/

4 3

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

Dec. 7, 2005

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 not found. My terminal prefs also show tsch. > The first lines that were different in the configure output seems to > refer to the script in Tools/config/missing. Try running it as > > Tools/config/.missing --help Did that (without the . in front of missing) and got: louispec% Tools/config/missing --help Tools/config/missing [OPTION]... PROGRAM [ARGUMENT]... Handle `PROGRAM [ARGUMENT]...' for when PROGRAM is missing, or return an error status if there is no known handling for PROGRAM. Options: -h, --help display this help and exit -v, --version output version information and exit --run try to run the given command, and emulate it if it fails Supported PROGRAM values: aclocal touch file `aclocal.m4' autoconf touch file `configure' autoheader touch file `config.h.in' automake touch all `Makefile.in' files bison create `y.tab.[ch]', if possible, from existing .[ch] flex create `lex.yy.c', if possible, from existing .c help2man touch the output file lex create `lex.yy.c', if possible, from existing .c makeinfo touch the output file tar try tar, gnutar, gtar, then tar without non-portable flags yacc create `y.tab.[ch]', if possible, from existing .[ch] *** I GOT IT ! Well, partially *************** The above along with the ./configure output gave me the clue. I had folders (directories) with spaces in the names and Mac type characters. I changed all names in the path to the SWIG folder to be Unix compatible and the ./configure ran properly. Except I still have g++ for gcc and the 'make' step still gives the same error: 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 **** Sigh ***************************** > > Configure seems to not be able to find it or thinks it is outdated. > Maybe you have a newer version of the autotools software than I do but > I doubt that since it comes with the system software. I'm using the latest SWIG: 1.3.27 > > more later, I have to run to a talk Thanks for the help. At least I'm part of the way there. Enjoy the talk. -- 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

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 I wonder if something else is going on. Oh, absolutely. OMM (not the fastest, admittedly) it probably takes a quarter of a second to import appscript (Python hauls in a big chunk of Carbon at that point). There's another quarter-second overhead in creating your first app instance (can't remember why offhand, but a profiler will tell you). If ASTS is running then it's clear sailing the rest of the way thanks to ASTS's terminology caching. If ASTS isn't running then there's a further quarter-second penalty on connecting to the first app as OSAGetAppTerminology() has to instantiate an AppleScript component before it can retrieve aete resources (stupid, I know; blame Apple's API). Plus there's the time it takes to retrieve the terminology (some Cocoa apps generate it on the fly from Cocoa Scripting data, making this even slower) and parse it (appscript is pretty fast at this, but it's still only Python) for each application the script uses; some heavyweights may well take over a second. Though you can avoid these particular overheads by only using aem, since it doesn't use terminology; aem code just takes a little more work to write. >Have you looked at your memory use under that load? > >Otherwise, there are many web frameworks for Python, most of which provide some way to keep the python process persistent. I don't see why you couldn't use any of those. > >We're using Quixote successfully on OS-X, you also might want to look into wsgi and paste. I'd be interested to know myself if anyone has used appscript/aem in a web framework context. (I'm not a web-head, so haven't explored this area myself.) Shoving the application scripting stuff into a persistent GUI process and using a light[er]weight IPC system to bridge between this and the CGI script is always an option. But having it in the main web app would be simpler and more efficient, assuming the web app uses a suitable Python distribution, of course (you won't get far without the Carbon extensions, obviously). Cheers, has -- http://freespace.virgin.net/hamish.sanderson/

1 0

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

Dec. 7, 2005

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. Hmmmm... I don't know about this one. What has this to do with Scipy? -- Cheers, Lou Pecora Code 6362 Naval Research Lab Washington, DC 20375 USA Ph: +202-767-6002 email: pecora(a)anvil.nrl.navy.mil

3 4