Mailman 3 November 2002 - Pythonmac-SIG

one fallout of cr/lf code
by Magladry, Stephen March 21, 2003

March 21, 2003

It is nice to be able to run PC Python code unchanged thanks to the code change made to handle cr/lf within the Mac Python code. I have run into one problem through. The cr/lf is view as two separate lines. The following code, --test.py from a pc---- import sys <cr><lf> sys.blah<cr><lf> --test.py from a pc---- returns the following error: File "test.py", line 3 in ? AttributeError: 'module' object has no attribute 'blah' Okay I can deal with doubling of the line number, that's not much of a problem. The real problem is with line continuations. --test2.py from a pc---- x = x\ <cr><lf> +1<cr><lf> --test2.py from a pc---- This code is not able to execute. The line continuation "works" on the <lf>. The <cr> is seen as a new line. Now without a continuation, Mac Python isn't able to correctly process it. I can "fix" my problems my doing the following. --fixedTest2.py from a pc---- x = (x <cr><lf> +1)<cr><lf> --fixedTest2.py from a pc---- Since an expression gets started with the "(", line continuation come for free. This is fine and dandy for cross platform code that I own and work with. It might be more of a problem with Python code one would get from some PC user, though. Don't know if we can do anything about this. If not, consider this as a FYI for those people working in a cross platform environment. Sincerely, Stephen Magladry

4 5

Re: [Pythonmac-SIG] ObjC stuff
by Jack Jansen March 20, 2003

March 20, 2003

Recently, Steve Spicklemire <steve(a)spvi.com> said: > So it's in CVS somewhere? I'll do a check-out and see if I can find it. I don't know, Steven Majewski may know (I think he is the one who looked at it). If it isn't in the repository it probably should be, preferrably in the Modules directory (because it is useful for non-Mac users) but if there's objections against that we'll put it in the Mac/Modules dir. > I just ordered CW-6 today so I might be able to pitch in a bit. While very useful for other things (like MacPython development) you don't need it for OSX unix-Python development: this is all make and gcc-based (and you have those on your OSX developer disc). -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm

5 4

Configure question
by bill fancher Dec. 14, 2002

Dec. 14, 2002

I'm running 10.2 and upgraded autoconf to 2.53 so that I can regenerate configure from configure.in. Having done so, I now notice that I get the following line in configure output: checking LINKCC... ld: Undefined symbols: ___gxx_personality_v0 Should I worry? Is it just something I overlooked before? Is anyone else seeing this? (He asked, hoping to avoid having to isolate, and perhaps remedy, the underlying cause.) -- bill "They laughed at Columbus, they laughed at Fulton, they laughed at the Wright brothers. But they also laughed at Bozo the Clown." Carl Sagan

2 2

mac OS X Apache Webserver Python Cgi's?
by Israel Evans Dec. 13, 2002

Dec. 13, 2002

Hey there Mac Python Folks... I figured that if anyone knew they would probably be on this list... I'm trying to set up my basic Apache webserver (the one that came installed with 10.1.5) to run python based cgi's. I figure that I'll probably have to use the unix version to do this but I'm not sure.. Anyway.. My real difficulty is setting up the apache server to use mod_python mod-snake or pyapache or whatever so that I can use osX as my development machine. Any help or pointers to more appropriate places would be greatly appreciated. ~Israel~

5 5

Install MySQLdb module on mac os x
by Dieter Gyselinck Dec. 9, 2002

Dec. 9, 2002

Hi, I'm trying to install the python MySQLdb module on os x 10.2 but when I try to run 'setup.py build' I get this error message : ld: can't locate file for: -lmysqlclient error: command 'gcc' failed with exit status 1 I have installed binary mysql-3.23.52 package and it seems to be working fine, I can access my db via php. I am trying to run the MySQL-python-0.9.2 setup. I have changed 'thread_safe_library' to 'NO' but that does not solve the problem. Anyone can help me out with this problem??? This is the output when I run setup.py build : running build running build_py not copying CompatMysqldb.py (output up-to-date) not copying _mysql_exceptions.py (output up-to-date) not copying MySQLdb/__init__.py (output up-to-date) not copying MySQLdb/converters.py (output up-to-date) not copying MySQLdb/connections.py (output up-to-date) not copying MySQLdb/cursors.py (output up-to-date) not copying MySQLdb/sets.py (output up-to-date) not copying MySQLdb/times.py (output up-to-date) not copying MySQLdb/constants/__init__.py (output up-to-date) not copying MySQLdb/constants/CR.py (output up-to-date) not copying MySQLdb/constants/FIELD_TYPE.py (output up-to-date) not copying MySQLdb/constants/ER.py (output up-to-date) not copying MySQLdb/constants/FLAG.py (output up-to-date) not copying MySQLdb/constants/REFRESH.py (output up-to-date) not copying MySQLdb/constants/CLIENT.py (output up-to-date) running build_ext building '_mysql' extension skipping _mysql.c (build/temp.darwin-6.0-Power Macintosh-2.2/_mysql.o up-to-date) gcc -arch i386 -arch ppc -bundle -flat_namespace -undefined suppress build/temp.darwin-6.0-Power Macintosh-2.2/_mysql.o -L/usr/lib/mysql -L/usr/local/lib/mysql -L/usr/local/mysql/lib/mysql -L/sw/lib -lmysqlclient -lz -o build/lib.darwin-6.0-Power Macintosh-2.2/_mysql.so -flat_namespace ld: for architecture i386 ld: warning -L: directory name (/usr/lib/mysql) does not exist ld: warning -L: directory name (/sw/lib) does not exist ld: warning /usr/lib/bundle1.o cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) ld: warning build/temp.darwin-6.0-Power Macintosh-2.2/_mysql.o cputype (18, architecture ppc) does not match cputype (7) for specified -arch flag: i386 (file not loaded) ld: can't locate file for: -lmysqlclient error: command 'gcc' failed with exit status 1 Thanx, Dieter

4 4

Warning: incompatible change in 2.3a0
by Jack Jansen Dec. 8, 2002

Dec. 8, 2002

Folks, I'm about to check in an incompatible change in the CVS trunk for users of Carbon.Qd: no longer will direct access to attributes of grafports be allowed, only the accessor functions will work. Also, the Carbon.Qd.qd object, the Quickdraw global variables, will disappear and you will have to use the accessor functions here also. To give an example, in stead of "port.bounds" you'll have to use "port.GetPortBounds()", and in stead of "Carbon.Qd.qd.arrow" you'll have to use "Carbon.Qd.GetQDGlobalsArrow()". If this causes major inconvenience: clamor loudly and I'll try to create a workaround. But I would rather not: the accessor functions have been required for C programmers since Carbon, and using them will make Python code more readable with the Apple documentation in hand. And, Just, don't worry: I've converted the IDE and the Lib directory to use accessor functions already, I'll check that in before I check in the incompatible change. -- - Jack Jansen <Jack.Jansen(a)oratrix.com> http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman -

2 1

Running Python scripts without full paths
by Paul Berkowitz Dec. 8, 2002

Dec. 8, 2002

Hello. I'm brand new to Python, in OS 10.2.2, but an experienced AppleScripter. (I'm quite amazed by the similarities of the syntax of the two languages, which is making it easy to learn Python. I predict there will be a lot of new converts.) I hope you don't mind a newbie setup question. I'm brand new to Unix as well, and that's probably where I'm going wrong. I was directed to pythonmac-sig when I was trying to find out how to import a module with the Interactive interpreter. I saw a reference to Russell Owen's webpage in the archives, where I found the solution to the problem (which is Mac OS X-only): making my own 'environment.plist' XML file in ~/.MacOSX. The website URL is http://www.astro.washington.edu/owen/AquaEnvVar.html This should be added to the Python FAQ. Now I'm stumped again. Russell's solution works for importing modules from directories that I've added to PYTHONPATH. But I can't get the shell to run script files without the file's full path or having to cd to the file's directory first, even though I've now added the directory to the path shell variable, which in turn has automatically added it to the PATH environment. I can import the script as a module with only the module name in the Interactive interpreter: >>> import module1 Hello module world! This (very simple) script does run when I give its full or relative path name or cd to its directory first, in the shell: [250-166:~] berkowit% python Library/Scripts/Python/module1.py Hello module world! But it won't work like this: [250-166:~] berkowit% python module1.py python: can't open file 'module1.py' The shell does know about its directory now (I set path to include it): [250-166:~] berkowit% printenv PATH /Users/berkowit/bin/powerpc-apple-darwin:/Users/berkowit/bin:/usr/local/bin: /usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/Users/berkowit/Library/Script s/Python:. That next-to-last directory: /Users/berkowit/Library/Scripts/Python is the one with module1.py. Why doesn't the shell find it? Or why doesn't Python find it since it too knows where it is now, as the module import makes clear? Is this another Mac-only problem? Maybe I need to add another key to the environment.plist file? Or am I just doing something wrong? Many thanks for any guidance. -- Paul Berkowitz

5 19

Announce: OSATools
by Michael J. Barber Dec. 4, 2002

Dec. 4, 2002

The recent discussion of AppleScript and OSA inspired me to finally write a package I've been thinking about for a while. I'm calling it OSATools, and it basically is a set of wrappers for the 'osascript' and 'osacompile' OS X system calls. There are convenience functions for several cases, and a basic but useful class modeling an AppleScript interface. You can do things like: Python 2.2.1 (#1, 09/14/02, 00:14:43) [GCC Apple devkit-based CPP 6.02] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from OSATools import AppModels >>> finder = AppModels.AppleScriptApp("Finder") >>> finder.tell('get the name of the startup disk') 'Macintosh HD\n' >>> finder.tellBlock(['set countList to {}', ... 'set the end of countList to the count of the folder "Library" of the startup disk', ... 'set the end of countList to the count of folder "Applications" of the startup disk', ... 'return the countList']) '36, 88\n' >>> Written quickly and only tested a bit, so there are probably bugs. Seems to work ok, though. One caveat: OSATools uses pipes to talk to osascript and friends. In other words, it won't work with MacPython just yet, you need a Unix python. Anyone who is interested can get it here: <http://www.artsci.wustl.edu/~mjbarber/OSATools.tgz> Hope this is useful for someone. Michael

5 10

Re: [Pythonmac-SIG] Running Python scripts without full paths
by kevin parks Dec. 2, 2002

Dec. 2, 2002

Someone who really understands this ought to put something up on the web on this! I know that it is not exclusively a python item, but it is relevent. Thanks to the folks on the list i have it working but i am still digesting the reasons why it does and what the relationship is between the OS X, Terminal.app, the ~/Library/init/tcsh/, files are, whether you need a ~/.tcshrc file at all, the /usr/share/tcsh/examples/ files, /etc, and PYTHONPATH (where is this set exactly? for macho and for the other python? is it even needed) and the evil mysterious ~/.MacOSX/environment.plist. file. The whole thing is terrible if you ask me. Too complex and not documented at all. Someone said that it is easy if you understand it. Well *if* is the key word there and how you get to understand it is another thing all together. A look in the bookstore through OS X books makes no mention of this. >>> Most of Terminal's environment is what is in >>> ~/.MacOSX/environment.plist. >>> That file is only read on login, which is a real pain, but until >>> there's some way to force WindowServer to reread it, you're stuck >>> with >>> trial and error. A temporary workaround is to run the app you want >>> directly from the shell instead of using LaunchServices to do it (as >>> with the 'open' command, the Finder, etc.) The 'pythonw' script does >>> exactly this. >> >> Thanks again, Nicholas. So can/should I add a new PATH key to my >> ~/.MacOSX/environment.plist, to get all future tcsh shell Terminal >> windows >> to inherit my scripts folder, as PYTHONPATH now does in the >> interactive >> interpreter? Will that work? (I understand that I'll need to log out >> and in, >> as OS X user, before it takes effect. I can put up with that for now.) > > Yes, that's one way to do it. If you just want stuff launched from > tcsh to be affected, then use ~/.tcshrc instead.

5 5

Re: Running Python scripts without full paths
by kevin parks Nov. 30, 2002

Nov. 30, 2002

I think that i got it to work. Apparently you can *NOT* set your path in ~/Library/init/tcsh/environment.mine. I looked at: /usr/share/tcsh/examples/login and that is where the path is set and if you want to append it it has to be in /Users/kevin/Library/init/tcsh/path because that where it looks for appended items. [snowcat:~] kevin% cd scripts/ [snowcat:~/scripts] kevin% ls -- foo.py [snowcat:~/scripts] kevin% ./foo.py hello kevin [snowcat:~/scripts] kevin% foo.py hello kevin So maybe it does work after all. I am not sure that ~/.MacOSX/environment.plist even needs to be set if you are not using an interface or framework.

4 6