From mday@mac.com Wed May 1 00:44:39 2002 From: mday@mac.com (Mark Day) Date: Tue, 30 Apr 2002 16:44:39 -0700 Subject: [Pythonmac-SIG] BBEdit questions In-Reply-To: <90C69BCC-5C8A-11D6-9F00-0003930C98D2@semi-retired.com> Message-ID: <3C7AB524-5C94-11D6-943C-00039354009A@mac.com> On Tuesday, April 30, 2002, at 03:35 PM, Kevin Altis wrote: > syntax coloring is on. > > I would like to change the default colors being used for syntax > coloring but can't find the dialog. Does that have to be changed > manually in a file on disk and if so where? Use the Preferences menu item and pick "Text Colors" from the scrolling list. You'll see a list of colorized things and their colors; just click on the color to bring up the color picker. > Auto-indent seems pretty dumb, I have to tab after typing a colon and > Return so it apparently doesn't understand blocks. If there is a > setting for this, I would like to change the behavior. Auto-indent isn't syntax aware. It just means that when you press Return, the new line starts out indented the same as the line you were previously on (so you don't have to keep tabbing when typing in a block that's all the same indentation level). > In the Text Options dialog I have it set to auto-indent, auto-expand > tabs (4 spaces) > Worse, it doesn't know that the tabs expanded to four spaces, so when > you have to backspace, so you have to backspace once for each space. > That is sort of annoying, any workarounds besides always using tabs > instead of spaces? I'd suggest just setting tabs to be 4 spaces wide and just always use tabs. You can do that with Preferences: Fonts for a global setting, or use the "Font & Tabs" menu item for per-file settings. Python will assume 8 spaces per tab, but if you only use tabs, there shouldn't be any confusion. The downside is that error messages printed out in Terminal, etc., will assume 8 spaces per tab, so using tabs to align things other than the start of line may not look the same as they would in BBEdit. -Mark From Robin.Siebler@corp.palm.com Wed May 1 00:53:17 2002 From: Robin.Siebler@corp.palm.com (Robin Siebler) Date: Tue, 30 Apr 2002 16:53:17 -0700 Subject: [Pythonmac-SIG] Is MacPython the right tool for me? Message-ID: <400CE9390E334A4393CEECDD6863120A0412FB4E@ussccm003.corp.palm.com> Let me prefice this by saying that I haven't used a Mac in 5 years and I haven't used MPW in over 5 years. With that said, here is what I am trying to do: I have some command-line tools that run in MPW. I would like to create some automated scripts to test these CLT's. Is MacPython the right tool for this? If not, what would be? I have used Python quite successfully to test CLT's under Windows, so I'm hoping that I can use it on the Mac to do the same thing. Thanks! Robin L. Siebler ------------------------------------- "Bother", said Pooh, as he deleted windows. From bs1535@sbc.com Wed May 1 02:58:22 2002 From: bs1535@sbc.com (SNYDER, BARRON F (AIT)) Date: Tue, 30 Apr 2002 21:58:22 -0400 Subject: [Pythonmac-SIG] Where's the output? Message-ID: <35BD410BA148D411A7ED00508BCFFBDA0C16C894@msgil65170u05.nbk2305.il.ameritech.com> I'm probably missing the obvious but when I run a simple script at the command line, I see no output. What am I not doing? My script is as simple as: ----------------------------------- #! /sw/bin/python print "hello" ----------------------------------- At the command prompt %, I type: python hello.py but I see no results and no errors! If I enter the python interpreter, everything works fine. How do I run my script from the shell? (btw, I running the Fink python installation) feeling like an idiot, Barron From jhrsn@pitt.edu Wed May 1 03:52:55 2002 From: jhrsn@pitt.edu (Jim Harrison) Date: Tue, 30 Apr 2002 22:52:55 -0400 Subject: [Pythonmac-SIG] BBEdit questions In-Reply-To: <90C69BCC-5C8A-11D6-9F00-0003930C98D2@semi-retired.com> Message-ID: on 4/30/02 6:35 PM, Kevin Altis at altis@semi-retired.com wrote: > The Run command does not work with wxPython Mac and MachoPython scripts, > it appears to go into a loop trying to launch the script while the > "Script Progress" dialog is up. I've assumed that this might be related to the wxPython Mac problem that requires "open -a script.py" from the command line rather than "python script.py". I think BBEdit does the equivalent of the latter. Jim Harrison Univ. of Pittsburgh From altis@semi-retired.com Wed May 1 04:27:10 2002 From: altis@semi-retired.com (Kevin Altis) Date: Tue, 30 Apr 2002 20:27:10 -0700 Subject: [Pythonmac-SIG] Where's the output? In-Reply-To: <35BD410BA148D411A7ED00508BCFFBDA0C16C894@msgil65170u05.nbk2305.il.ameritech.com> Message-ID: Did you check the Console? You're running from the Terminal, but depending on how stdout and stderr are bound, output can go to the Console. ka > -----Original Message----- > From: pythonmac-sig-admin@python.org > [mailto:pythonmac-sig-admin@python.org]On Behalf Of SNYDER, BARRON F > (AIT) > Sent: Tuesday, April 30, 2002 6:58 PM > To: 'Pythonmac-SIG@python.org' > Subject: [Pythonmac-SIG] Where's the output? > > > > I'm probably missing the obvious but when I run a simple script at the > command line, I see no output. What am I not doing? > > My script is as simple as: > > ----------------------------------- > #! /sw/bin/python > > print "hello" > ----------------------------------- > > At the command prompt %, I type: python hello.py > but I see no results and no errors! If I enter the python interpreter, > everything works fine. How do I run my script from the shell? > > (btw, I running the Fink python installation) > > feeling like an idiot, > Barron From barronsnyder@mac.com Wed May 1 05:39:47 2002 From: barronsnyder@mac.com (Barron Snyder) Date: Tue, 30 Apr 2002 23:39:47 -0500 Subject: [Pythonmac-SIG] Where's the output? Message-ID: <7774A3C3-5CBD-11D6-A890-003065CC5884@mac.com> I took a look but nothing's there either. Hmmm... Any other ideas? Anyone? > Kevin Altis wrote: > Did you check the Console? You're running from the Terminal, but depending > on how stdout and stderr are bound, output can go to the Console. ka > >> -----Original Message----- >> From: pythonmac-sig-admin@python.org >> [mailto:pythonmac-sig-admin@python.org]On Behalf Of SNYDER, BARRON F >> (AIT) >> Sent: Tuesday, April 30, 2002 6:58 PM >> To: 'Pythonmac-SIG@python.org' >> Subject: [Pythonmac-SIG] Where's the output? >> I'm probably missing the obvious but when I run a simple script at the >> command line, I see no output. What am I not doing? >> My script is as simple as: >> ----------------------------------- >> #! /sw/bin/python >> print "hello" >> ----------------------------------- >> At the command prompt %, I type: python hello.py >> but I see no results and no errors! If I enter the python interpreter, >> everything works fine. How do I run my script from the shell? >> (btw, I running the Fink python installation) >> feeling like an idiot, >> Barron From Jack.Jansen@cwi.nl Wed May 1 10:25:39 2002 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Wed, 1 May 2002 11:25:39 +0200 Subject: [Pythonmac-SIG] Where's the output? In-Reply-To: <35BD410BA148D411A7ED00508BCFFBDA0C16C894@msgil65170u05.nbk2305.il.ameritech.com> Message-ID: <6702512E-5CE5-11D6-897C-0030655234CE@cwi.nl> On Wednesday, May 1, 2002, at 03:58 , SNYDER, BARRON F (AIT) wrote: > > I'm probably missing the obvious but when I run a simple script at the > command line, I see no output. What am I not doing? > > My script is as simple as: > > ----------------------------------- > #! /sw/bin/python > > print "hello" > ----------------------------------- > > At the command prompt %, I type: python hello.py > but I see no results and no errors! If I enter the python interpreter, > everything works fine. This should work, and it works fine for me (even though I'm not using the fink distribution it shouldn't make a difference, especially since you *do* get the right Python for interactive work). A few suggestion for tracking this: - You have a #! line but say you're typing "python hello.py". Check that you're indeed using the Python you're expecting to use. "which python" will help you here. - You don't have anything funny in your PYTHONSTARTUP or PYTHONHOME or so shell variable? - Try "python -v hello.py" to see whether stderr is connected. Also, it may show problems during initialization. - See whether it's actually the output getting lost, and not something else (like nothing hallening at all). Running a script like import time time.sleep(10) should tell you (if it takes 10 seconds to come back then it probably did run). - If interactive mode normally works, try "python -i hello.py" and see if you indeed get interactive mode, and maybe find out what is wrong with sys.stderr. > -- - Jack Jansen http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman - From terabaap@yumpee.org Wed May 1 10:24:08 2002 From: terabaap@yumpee.org (Manoj Plakal) Date: Wed, 01 May 2002 04:24:08 -0500 Subject: [Pythonmac-SIG] Re: [wxPython-mac] editing Python scripts on OS X References: Message-ID: <3CCFB438.10604@yumpee.org> Kevin Altis wrote: > Editor recommendations on OS X are welcome. > > The list at http://www.python.org/editors/ contains quite a few Unix & > Multiplatform Text Editors. What I want is a GUI editor that is > Python-aware, so it understands whitespace in Python scripts, can insert > four spaces instead of tabs, manage indent/dedent of code blocks and > preferably has syntax coloring and can run tabnanny, and jump to the line in > the source with a syntax error. It needs to be able to at least read and > save files with Unix (LF) line endings, but it would be best if it can deal > with Windows (CR/LF) and Mac (CR). I don't particularly care about more than > basic key bindings like Cut/Copy/Paste and arrow keys, I'm mostly a mouser. If you don't mind running an X server, you can use Wing IDE (wingide.com). There is a beta version that runs on OS X (on top of Gtk and X Windows). A little buggy and sluggish (mainly due to Gtk/X) but it has a good editor, excellent debugger and nice project/class browser. (BTW, it is a Python IDE) Also, Komodo is Mozilla-based, so there are hopes of it running on OS X too ... Manoj From lists@netelligent.biz Wed May 1 11:39:38 2002 From: lists@netelligent.biz (tmk) Date: Wed, 1 May 2002 12:39:38 +0200 Subject: [Pythonmac-SIG] Where's the output? In-Reply-To: <6702512E-5CE5-11D6-897C-0030655234CE@cwi.nl> Message-ID: I'll also add this one: Check that your file is saved with Unix line endings. (I'll must confess that i've been bitten by this one more than once, and the symptoms where the ones you describe) HTH, = tmk = On Wednesday, May 1, 2002, at 11:25 , Jack Jansen wrote: > > On Wednesday, May 1, 2002, at 03:58 , SNYDER, BARRON F (AIT) wrote: > >> >> I'm probably missing the obvious but when I run a simple script at the >> command line, I see no output. What am I not doing? >> >> My script is as simple as: >> >> ----------------------------------- >> #! /sw/bin/python >> >> print "hello" >> ----------------------------------- >> >> At the command prompt %, I type: python hello.py >> but I see no results and no errors! If I enter the python interpreter, >> everything works fine. > > This should work, and it works fine for me (even though I'm not > using the fink distribution it shouldn't make a difference, > especially since you *do* get the right Python for interactive > work). > > A few suggestion for tracking this: > - You have a #! line but say you're typing "python hello.py". Check > that you're indeed using the Python you're expecting to use. "which > python" will help you here. > - You don't have anything funny in your PYTHONSTARTUP or PYTHONHOME > or so shell variable? > - Try "python -v hello.py" to see whether stderr is connected. > Also, it may show problems during initialization. > - See whether it's actually the output getting lost, and not > something else (like nothing hallening at all). Running a script > like > import time > time.sleep(10) > should tell you (if it takes 10 seconds to come back then it > probably did run). > - If interactive mode normally works, try "python -i hello.py" and > see if you indeed get interactive mode, and maybe find out what is > wrong with sys.stderr. >> -- > - Jack Jansen > http://www.cwi.nl/~jack - > - If I can't dance I don't want to be part of your revolution -- > Emma Goldman - > > > > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG@python.org > http://mail.python.org/mailman/listinfo/pythonmac-sig > From barronsnyder@mac.com Wed May 1 14:18:07 2002 From: barronsnyder@mac.com (Barron Snyder) Date: Wed, 1 May 2002 08:18:07 -0500 Subject: [Pythonmac-SIG] Where's the output? In-Reply-To: Message-ID: Well, I tried all of the submitted suggestions (Thanks everyone!) but everything was setup as it was supposed to be. tmk's idea however, panned out. It was the line endings! In OS X, I use BBEdit and didn't realize that it was defaulting to mac line endings rather than unix line endings. Actually, until tmk mentioned it, I wasn't aware that you could save a file both ways in OS X. I thought everything was unix. But why doesn't this throw an error? Thank you one and all! -Barron On Wednesday, May 1, 2002, at 05:39 AM, tmk wrote: > I'll also add this one: > > Check that your file is saved with Unix line endings. (I'll must > confess that i've been bitten by this one more than once, and the > symptoms where the ones you describe) > > HTH, > > = tmk = > > On Wednesday, May 1, 2002, at 11:25 , Jack Jansen wrote: > >> >> On Wednesday, May 1, 2002, at 03:58 , SNYDER, BARRON F (AIT) wrote: >> >>> >>> I'm probably missing the obvious but when I run a simple script at the >>> command line, I see no output. What am I not doing? >>> >>> My script is as simple as: >>> >>> ----------------------------------- >>> #! /sw/bin/python >>> >>> print "hello" >>> ----------------------------------- >>> >>> At the command prompt %, I type: python hello.py >>> but I see no results and no errors! If I enter the python interpreter, >>> everything works fine. >> >> This should work, and it works fine for me (even though I'm not using >> the fink distribution it shouldn't make a difference, especially since >> you *do* get the right Python for interactive work). >> >> A few suggestion for tracking this: >> - You have a #! line but say you're typing "python hello.py". Check >> that you're indeed using the Python you're expecting to use. "which >> python" will help you here. >> - You don't have anything funny in your PYTHONSTARTUP or PYTHONHOME or >> so shell variable? >> - Try "python -v hello.py" to see whether stderr is connected. Also, >> it may show problems during initialization. >> - See whether it's actually the output getting lost, and not something >> else (like nothing hallening at all). Running a script like >> import time >> time.sleep(10) >> should tell you (if it takes 10 seconds to come back then it probably >> did run). >> - If interactive mode normally works, try "python -i hello.py" and see >> if you indeed get interactive mode, and maybe find out what is wrong >> with sys.stderr. >>> -- >> - Jack Jansen >> http://www.cwi.nl/~jack - >> - If I can't dance I don't want to be part of your revolution -- Emma >> Goldman - >> >> >> >> _______________________________________________ >> Pythonmac-SIG maillist - Pythonmac-SIG@python.org >> http://mail.python.org/mailman/listinfo/pythonmac-sig >> > > > > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG@python.org > http://mail.python.org/mailman/listinfo/pythonmac-sig From Jack.Jansen@cwi.nl Wed May 1 14:51:25 2002 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Wed, 1 May 2002 15:51:25 +0200 Subject: [Pythonmac-SIG] Where's the output? In-Reply-To: Message-ID: <87428702-5D0A-11D6-897C-0030655234CE@cwi.nl> On Wednesday, May 1, 2002, at 03:18 , Barron Snyder wrote: > tmk's idea however, panned out. It was the line endings! In OS X, I use > BBEdit and didn't realize that it was defaulting to mac line endings > rather than unix line endings. Actually, until tmk mentioned it, I > wasn't aware that you could save a file both ways in OS X. I thought > everything was unix. But why doesn't this throw an error? I was going to say something completely different, but then I thought about it for a while, and there's little Python can do about it. The whole file is seen as a single line, albeit one without a terminating newline, and it starts with a # so it's a comment line. Or, in other words, it functions as an empty file. But: this will be fixed as of Python 2.3, because there it'll understand any newline convention, so your script will work as expected. -- - Jack Jansen http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman - From danielt3@gte.net Wed May 1 14:53:40 2002 From: danielt3@gte.net (Daniel T.) Date: Wed, 1 May 2002 09:53:40 -0400 Subject: [Pythonmac-SIG] wxPython in Carbon? In-Reply-To: <3CCEF4F8.10204@hagen.de> References: <3CCEF4F8.10204@hagen.de> Message-ID: I prefer using MacPython rather than MachoPython, but I really want to play with GUI stuff on my OS X box. Is it possible to use wxPython for this? What is the best way for me to go? Must I break down and use MachoPython in a terminal window? -- From Jack.Jansen@cwi.nl Wed May 1 14:54:25 2002 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Wed, 1 May 2002 15:54:25 +0200 Subject: [Pythonmac-SIG] Is MacPython the right tool for me? In-Reply-To: <400CE9390E334A4393CEECDD6863120A0412FB4E@ussccm003.corp.palm.com> Message-ID: On Wednesday, May 1, 2002, at 01:53 , Robin Siebler wrote: > Let me prefice this by saying that I haven't used a Mac in 5 years and I > haven't used MPW in over 5 years. With that said, here is what I am > trying > to do: I have some command-line tools that run in MPW. I would like to > create some automated scripts to test these CLT's. Is MacPython the > right > tool for this? If not, what would be? You could use MacPython with the mpwsystem module (in :Mac:Contrib) and the toolserver, but it would probably be a bit convoluted. Somebody did an MPW version of Python a long long time ago, but I'm pretty sure that that isn't maintained anymore (i.e. macpythonistas who know anything about this: please speak up!). And the chance of anyone picking up MPW-python nowadays, with MPW as good as dead, is minimal... -- - Jack Jansen http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman - From altis@semi-retired.com Wed May 1 16:21:35 2002 From: altis@semi-retired.com (Kevin Altis) Date: Wed, 1 May 2002 08:21:35 -0700 Subject: [Pythonmac-SIG] wxPython in Carbon? In-Reply-To: Message-ID: > From: Daniel T. > > I prefer using MacPython rather than MachoPython, but I really want > to play with GUI stuff on my OS X box. Is it possible to use wxPython > for this? What is the best way for me to go? Must I break down and > use MachoPython in a terminal window? Jack said that MacPython and MachoPython can co-exist. You can use MachoPython from a terminal window, but you don't have to. If you install MachoPython and the wxPython Mac preview available at http://sourceforge.net/project/showfiles.php?group_id=10718 then you can install the MachoPython package and then the wxPython package. The wxPython-mac mailing list is probably the best place to check for daily changes or updates: http://lists.wxwindows.org/mailman/listinfo/wxpython-mac If you use Get Info to associate /Applications/Python.app/Contents/MacOS/python with .py and .pyw files then you can double-click those scripts in the Finder. Output will go to the Console. On my system I made an alias in the Terminal (the pym is not significant, you can use another short-cut name) alias pym /Applications/Python.app/Contents/MacOS/python So when I'm testing scripts I just cd (change directory) to the directory the script is in and can simply type pym followed by the name of the script: pym minimal.py You do not need to have a #! line in your script or make the script executable with chmod if you launch with /Applications/Python.app/Contents/MacOS/python There are other ways to run scripts, in fact, knowing which Python and Python wrapper/framework to launch in what context can definitely be confusing. A complete list would be beneficial. I'm definitely at the "I got it to work and I'm not messing with it." stage. ;-) I started a few wikis to cover installation, bugs, and other issues. It will be beneficial if someone with more OS X experience than I updates the installation instructions and provides better getting started instructions (maybe a new section after installation?). A portion of the wiki once it is in better shape would be appropriate for a FAQ page on this stuff. I suspect this is going to come up a lot. http://wiki.wxpython.org/index.cgi/wxPythonMac http://wiki.wxpython.org/index.cgi/MachoPython http://wiki.wxpython.org/index.cgi/PythonCardOnMac http://wiki.wxpython.org/index.cgi/wxPython_20Mac_20and_20PythonCard_20Issue s ka From tony@metanet.com Wed May 1 16:31:44 2002 From: tony@metanet.com (Tony Lownds) Date: Wed, 1 May 2002 08:31:44 -0700 Subject: [Pythonmac-SIG] Where's the output? In-Reply-To: <87428702-5D0A-11D6-897C-0030655234CE@cwi.nl> References: <87428702-5D0A-11D6-897C-0030655234CE@cwi.nl> Message-ID: > >But: this will be fixed as of Python 2.3, because there it'll >understand any newline convention, so your script will work as >expected. Hooray for Universal Newlines! -Tony From owen@astro.washington.edu Wed May 1 16:54:49 2002 From: owen@astro.washington.edu (Russell E Owen) Date: Wed, 1 May 2002 08:54:49 -0700 Subject: [Pythonmac-SIG] Re: BBEdit questions Message-ID: Kevin Altis wrote: >I'm in the process of evaluating BBEdit as a Python editor... > >I would like to change the default colors being used for syntax coloring but can't find the dialog. Does that have to be changed manually in a file on disk and if so where? I don't know of any way to do this. >Auto-indent seems pretty dumb, I have to tab after typing a colon and Return so it apparently doesn't understand blocks. If there is a setting for this, I would like to change the behavior. Alas, this is true. I don't believe BBEdit has "smart" indent for any language. Auto indent just means that when you hit return, the indent matches the previous line. Smart indent would be great! It would show me right away when I omitted a ":" (one of my more common mistakes). >Worse, it doesn't know that the tabs expanded to four spaces, so when you have to backspace, so you have to backspace once for each space. That is sort of annoying, any workarounds besides always using tabs instead of spaces? I agree this should be fixed. However, as somebody else suggested, just use tabs. You can pick how many spaces a tab is worth, and you can always turn tabs into spaces later if you want to (i.e. if you are writing code that MUST be in spaces because GvR insists). >Check syntax under the #! menu always complains with an error "The front window isn't in a scripting language BBEdit currently recognizes (application error code 30001)." Yeah, same here. I hadn't noticed this before. That's worth a bug report. BBEdit definitely has its weaknesses. BB stands for Bare Bones, and I think that's part of the problem. My own pet peeves include: - The range checkboxes in the find/replace dialog box. Some have to be unchecked before others can be checked. Hence I can't just leave "wrap" checked all the time and check "in selection" when I need it. (Pepper does this right. I am really confused why the BB haven't fixed this.) I should try to write a script to put it in the desired state. - The find/replace dialog box is modal. In this day and age? That's taking "bare bones" too far! (Pepper does this right). - The main tool for commenting and uncommenting code TOGGLES the state based on the first line in your selection. This can be unpleasant when you are trying to temporarily comment out a block of code that starts with comments. I wrote a pair of scripts so I could be explicit about what I'm trying to accomplish ("explicit is better than implicit"). - File browsers (including the one put up by "Find All") don't allow editing of file contents. (Pepper does this right). I attribute this to the "bare bones" aspect, but perhaps they may implement it someday. Some others I've used include: - Qued was a wonderful text editor -- ahead of BBEdit in its day in some important ways (such as multiple undo). But Nisus stopped supporting it when BBEdit got popular. You can probably still buy it, but I wouldn't bother unless they've updated it. - Alpha is powerful and incredibly extensible. But I find it really cluttered. Also, every time I've tried it I've somehow managed to get it into modes where text entry doesn't work right (presumably some configuration got twisted or some weird script accidentally got run). I didn't want to spend the time to try to get it straightened out and reconfigured to my taste. - Pepper has some very nice features, but is behind BBEdit in some important areas, including being able to run scripts. I own it, and really hope a major update of Pepper materializes someday. - NEdit (a free X-based editor). I'd use it if I had nothing better, but X is clumsy if one is used to Mac and NEdit isn't particularly powerful. BBEdit isn't perfect, but it is what I use at present. It has powerful find/replace (including excellent multi-file find/replace), handles files with different line endings (indispensable in the schizoid MacOS X world of Mac/unix line endings), handles huge file, and is robust. I also find it pleasant to use, with a nice balance of power and simplicity. Regards, -- Russell From Maarten L. Hekkelman" References: Message-ID: <1871070991062.20020501184404@hekkelman.com> Hello Russell, >>I'm in the process of evaluating BBEdit as a Python editor... >> >>I would like to change the default colors being used for syntax >>coloring but can't find the dialog. Does that have to be changed >>manually in a file on disk and if so where? > I don't know of any way to do this. Use Pepper :-) >>Worse, it doesn't know that the tabs expanded to four spaces, so >>when you have to backspace, so you have to backspace once for each >>space. That is sort of annoying, any workarounds besides always >>using tabs instead of spaces? This works like expected in Pepper. > - The main tool for commenting and uncommenting code TOGGLES the > state based on the first line in your selection. This can be > unpleasant when you are trying to temporarily comment out a block of > code that starts with comments. I wrote a pair of scripts > > so I could be explicit about what I'm trying to accomplish > ("explicit is better than implicit"). Pepper should do this better. > - Pepper has some very nice features, but is behind BBEdit in some > important areas, including being able to run scripts. I own it, and > really hope a major update of Pepper materializes someday. You can run scripts from within Pepper using the extensions menu. I don't know Python but in Perl you have an eval command that evaluates a script and puts the output into a variable. Next you can print out the content of this variable to the environmental variable $PEPPER_NEW_WINDOW and a new window will be opened by Pepper containing the output of the selected script lines. > BBEdit isn't perfect, but it is what I use at present. It has > powerful find/replace (including excellent multi-file find/replace), > handles files with different line endings (indispensable in the > schizoid MacOS X world of Mac/unix line endings), handles huge file, > and is robust. I also find it pleasant to use, with a nice balance > of power and simplicity. Too bad you don't use Pepper. Please have a look at the new version and tell me why it is you prefer BBEdit so I can improve Pepper. -- Best regards, Maarten mailto:maarten@hekkelman.com From pecora@anvil.nrl.navy.mil Wed May 1 18:03:57 2002 From: pecora@anvil.nrl.navy.mil (Louis M. Pecora) Date: Wed, 1 May 2002 13:03:57 -0400 Subject: [Pythonmac-SIG] Re[2]: BBEdit questions In-Reply-To: <1871070991062.20020501184404@hekkelman.com> References: <1871070991062.20020501184404@hekkelman.com> Message-ID: > >>I'm in the process of evaluating BBEdit as a Python editor... >>> >>>I would like to change the default colors being used for syntax >>>coloring but can't find the dialog. Does that have to be changed >>>manually in a file on disk and if so where? > > > I don't know of any way to do this. > Look under Preferences (Edit menu)/ Text Colors You can set colors to whatever you want. > >>Worse, it doesn't know that the tabs expanded to four spaces, so >>>when you have to backspace, so you have to backspace once for each >>>space. That is sort of annoying, any workarounds besides always > >>using tabs instead of spaces? Just use Tabs and set BBEdit tabs to 4 spaces or whatever you want. -- Cheers, Lou Pecora From gherman@darwin.in-berlin.de Thu May 2 09:00:38 2002 From: gherman@darwin.in-berlin.de (Dinu Gherman) Date: Thu, 02 May 2002 10:00:38 +0200 (CEST) Subject: [Pythonmac-SIG] How to detect in a Cocoa app if Python is available? Message-ID: <1020326438.3cd0f2267bcfb@webmail.in-berlin.de> Hi, I'm writing some Cocoa front-ends to Python apps and wonder what is the best way to detect if Python is available on a target OS X box? If not I'm popping up an Alert panel so you can download Python with one click. First I tried a popen() on "which python", but that runs into some shell problems due to environment variables, I assume. So, for now I'm expicitly indicating "usr/local/bin/python" and make a C-popen() on a bundled dummy Python file (using usr/local/bin/python) writing just "Hello World" which I compare the output of popen() with. This is not really satisfactory and I wonder if anybody did better than this? Note, that I'm using vanilla Python 2.2 built from the sources with configure/make, so there is no Python.framework stuff involved. I also wonder if this would this make things easier and how, if so? I can send some C/Objective-C code if anybody is interested. Regards, Dinu From cwebster@unlv.edu Thu May 2 16:30:59 2002 From: cwebster@unlv.edu (Corran Webster) Date: Thu, 2 May 2002 08:30:59 -0700 Subject: [Pythonmac-SIG] Is MacPython the right tool for me? In-Reply-To: Message-ID: <200205021531.AEG53645@100m.mpr200-1.esr.lvcm.net> On Wednesday, May 1, 2002, at 06:54 AM, Jack Jansen wrote: > > On Wednesday, May 1, 2002, at 01:53 , Robin Siebler wrote: > >> Let me prefice this by saying that I haven't used a Mac in 5 years >> and I >> haven't used MPW in over 5 years. With that said, here is what I am >> trying >> to do: I have some command-line tools that run in MPW. I would like >> to >> create some automated scripts to test these CLT's. Is MacPython the >> right >> tool for this? If not, what would be? > > You could use MacPython with the mpwsystem module (in :Mac:Contrib) and > the toolserver, but it would probably be a bit convoluted. Somebody did > an MPW version of Python a long long time ago, but I'm pretty sure that > that isn't maintained anymore (i.e. macpythonistas who know anything > about this: please speak up!). Back in the 1.5.2 days I experimented with getting Python to compile as an MPW tool. As I recall, most of it compiled without too much pain (I think there was a fair amount of MPW support already in the source) and I ended up with something that had basic functionality: you could use simple scripts interactively. However internal file system access was broken - I couldn't run a script in a .py file because python couldn't access the file system - and I gave up before I resolved this issue. I never made what I did public, and I don't know if I still have the makefiles and modifications (and even if I did, they are 3 years out of date). Based on my experience, you may well be able to get something running in about a week if you had the time and sufficient knowledge of the MPW compilers and makefile system. > And the chance of anyone picking up MPW-python nowadays, with MPW as > good as dead, is minimal... My principal interest at the time was because I didn't have access to CodeWarrior and MPW was freely available. For those not on OS X, this could still be a compelling argument. Regards, Corran From Chris.Barker@noaa.gov Thu May 2 17:37:07 2002 From: Chris.Barker@noaa.gov (Chris Barker) Date: Thu, 02 May 2002 09:37:07 -0700 Subject: [Pythonmac-SIG] Where's the output? References: <87428702-5D0A-11D6-897C-0030655234CE@cwi.nl> Message-ID: <3CD16B33.B9FC2BC8@noaa.gov> Jack Jansen wrote: > The > whole file is seen as a single line, albeit one without a terminating > newline, and it starts with a # so it's a comment line. Or, in other > words, it functions as an empty file. > > But: this will be fixed as of Python 2.3, because there it'll understand > any newline convention, so your script will work as expected. Unfortunately, this is only a partial fix, as it only fixes the Python portion of the problem. If you want your script to run as a program, by setting the executable permission, and putting a #! line at the top, Darwin will see the whole file as one line, so the #! line won't work. I just ran into this testing out a Python CGI script, so you still really need to use *nix line endings in this context. By the way, Jack, did Guido officially approve the Universal newlines patch? It is a bit odd that Apple would create this wierd two-kinds-of-newlines-on-one system mess, but I suppose they had little choice, and I, for one, apprechiate the new *nix compatability. -Chris -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker@noaa.gov From Chris.Barker@noaa.gov Thu May 2 18:00:20 2002 From: Chris.Barker@noaa.gov (Chris Barker) Date: Thu, 02 May 2002 10:00:20 -0700 Subject: [Pythonmac-SIG] Re[2]: BBEdit questions References: <1871070991062.20020501184404@hekkelman.com> Message-ID: <3CD170A4.34AA2978@noaa.gov> "Louis M. Pecora" wrote: > >>>space. That is sort of annoying, any workarounds besides always > > >>using tabs instead of spaces? > > Just use Tabs and set BBEdit tabs to 4 spaces or whatever you want. This is really only a good option is you only use a Mac, don't share code with people on other systems, or use other people's code. If you do want to use tabs, I HIGHLY recommend that you set tabs to 8 spaces so you have WYSIWYG indenting. Another option is to keep "show invisibles" on so that you are immediately aware that you have mixed them up if you do. Also, make sure you have easy access to a tabs-to-spaces and spaces-to-tabs converter. I have one I can post if people want it. It was a mistake to ever allow mixed tabs+spaces indenting, but we are stuck with that legacy now. The solution on every other platform is to establish the four-spaces-for-an-indent convention, and it works just fine everywhere but the Mac. I'm still not sure why there seems to be a dirth of fully capable programmer's editors for the Mac, but both BBedit and Pepper seem so close that all we need to do is solve this tiny problem. (perhaps it's solved for Pepper already; unfortunately the demo version is so annoyingly crippled that I haven't really checked it out). It must be possible to somehow configure BBedit to indent intelligently with spaces. If not, perhaps a string of requests to BareBones from every one of us will persuade them to add this capability. In fact, while consistent and easy indenting is more critical in Python than other languages, smart indenting is useful in all languages, it's amazing to me that BBedit doesn't support it. I guess It'll be back to emacs on OS-X for me for a while. It's funny, I use emacs for everything on Linuxeven though I don't particularly like it, but it has a powerful mode for every language I write, and that is invaluable. I have never found another editor on any platform that supports everything I need (Python, Perl, LateX, BibTeX, MATLAB, Fortran, C, C++ HTML, etc. etc.) OT: does anyone know if BBedit has a decent LaTeX mode? I am on the verge of buying it despite my other complaints. -Chris -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker@noaa.gov From owen@astro.washington.edu Thu May 2 19:59:38 2002 From: owen@astro.washington.edu (Russell E Owen) Date: Thu, 2 May 2002 11:59:38 -0700 Subject: [Pythonmac-SIG] Re: BBEdit questions (Russell E Owen) Message-ID: (I included copies of my message to the author of Pepper and to the BBEdit folks. The former responded directly to the list. The latter gave me permission to forward their reply. Editorial comment: John's statement that it makes no logical sense to be able to select "in selection" and "wrap" is disappointing, since most other text editors allow this. "In selection" simply trumps "wrap". Still..it explains why this has never gotten fixed. I consider it to be a very serious design flaw because it is clumsy and encourages you to get BBEdit into a state where none of the range checkboxes is checked, at which point a Replace All acts only from the cursor downwards -- almost never what you want!!! -- Russell). > Kevin Altis wrote: > > >I'm in the process of evaluating BBEdit as a Python editor... > > > >I would like to change the default colors being used for syntax > >coloring but can't find the dialog. Does that have to be changed > >manually in a file on disk and if so where? > > I don't know of any way to do this. You can do this in the Text Colors panel of the Preferences window. > >Worse, it doesn't know that the tabs expanded to four spaces, so > >when you have to backspace, so you have to backspace once for each > >space. That is sort of annoying, any workarounds besides always > >using tabs instead of spaces? > > I agree this should be fixed. However, as somebody else suggested, > just use tabs. You can pick how many spaces a tab is worth, and you > can always turn tabs into spaces later if you want to (i.e. if you > are writing code that MUST be in spaces because GvR insists). If you're using spaces, and you want BBEdit to delete four spaces at a time when you hit the delete key, how would you delete only *one* space if that's what you wanted? We try to avoid features like this, where the program tries to be smarter than you, because it's more frustrating to workaround it than the problem it originally tried to solve. Try using BBEdit's Entab and Detab commands when you open and save your files. (In the Text menu.) > >Check syntax under the #! menu always complains with an error "The > >front window isn't in a scripting language BBEdit currently > >recognizes (application error code 30001)." > > Yeah, same here. I hadn't noticed this before. That's worth a bug report. We're aware of this limitation, I believe syntax checking for Python is already slated for a future update. > - The range checkboxes in the find/replace dialog box. Some have to > be unchecked before others can be checked. Hence I can't just leave > "wrap" checked all the time and check "in selection" when I need > it. (Pepper does this right. I am really confused why the BB > haven't fixed this.) I should try to write a script to put it in > the desired state. For one thing, wrap-around has serious performance side-effects. Start at Top is a much better option in most cases, and has no performance side effects. It makes no logical sense for both Wrap Around and Only Search Selection to be turned on; you can't wrap around the selected text. We provide shortcut keys for all the checkboxes to make it easy to toggle them on and off. > - The find/replace dialog box is modal. In this day and age? That's > taking "bare bones" too far! (Pepper does this right). We respectfully disagree. > - File browsers (including the one put up by "Find All") don't > allow editing of file contents. (Pepper does this right). I > attribute this to the "bare bones" aspect, but perhaps they may > implement it someday. Once again, this is an explicit design decision, not a limitation. We welcome comments and questions from anyone; let us know if you have more. Best regards, -- John Gruber Bare Bones Software Technical Support From pecora@anvil.nrl.navy.mil Thu May 2 20:11:06 2002 From: pecora@anvil.nrl.navy.mil (Louis M. Pecora) Date: Thu, 2 May 2002 15:11:06 -0400 Subject: [Pythonmac-SIG] Re: BBEdit questions (Russell E Owen) In-Reply-To: References: Message-ID: John Gruber Bare Bones Software Technical Support of BBEdit wrote: >It makes no logical sense for both Wrap Around and Only Search >Selection to be turned on; you can't wrap around the selected text. Huh? Sure it makes sense. You just want to start at the beginning of the selection when you reach the end of the selection. Did I miss something? >If you're using spaces, and you want BBEdit to delete four spaces at >a time when you hit the delete key, how would you delete only *one* >space if that's what you wanted? We try to avoid features like this, >where the program tries to be smarter than you, because it's more >frustrating to workaround it than the problem it originally tried to >solve. Although it's not a BBEdit solution, you can easily program a hot key with QuicKeys to do this. QuicKeys is good for lots of stuff. Adding functionality to programs that don't have what you want is one. I think there's now a Mac OS X version (just a satisfied user). -- Cheers, Lou Pecora From ep@epoz.org Thu May 2 21:19:59 2002 From: ep@epoz.org (Etienne Posthumus) Date: Thu, 2 May 2002 22:19:59 +0200 Subject: [Pythonmac-SIG] Programmer's editor under OS X Message-ID: I have been following this thread with half-an-ear, so not up to date on the exact requirements. But I haven't seen anyone mention VIM yet. I use the graphical VIM-carbon for my Python editing on OS X, and it does Syntax highlighting and editing very nicely. And has the added benefit that the key bindings stay the same when used on other platforms... There is a Mac version on: http://homepage.mac.com/macvim/index.html and an OS X version on: http://homepage.mac.com/fisherbb/index.html (I use this one) Etienne Posthumus Amsterdam, Nederland From Chris.Barker@noaa.gov Fri May 3 00:19:51 2002 From: Chris.Barker@noaa.gov (Chris Barker) Date: Thu, 02 May 2002 16:19:51 -0700 Subject: [Pythonmac-SIG] Re: BBEdit questions (Russell E Owen) References: Message-ID: <3CD1C997.BEB04C45@noaa.gov> Russell E Owen wrote: > > (I included copies of my message to the author of Pepper and to the BBEdit folks. The former responded directly to the list. The latter gave me permission to forward their reply. It's nice to see that the providers of both BBEdit and Pepper are responsive, although I have to say that the replies from John appeared to be all of the "I already know my program is perfect, so I'm going to try to justify all of its features" nature. That makes me think that there is really no point in trying to further explain the issues, but in case someone want to... > > >Worse, it doesn't know that the tabs expanded to four spaces, so > > >when you have to backspace, so you have to backspace once for each > > >space. > If you're using spaces, and you want BBEdit to delete four spaces at > a time when you hit the delete key, how would you delete only *one* > space if that's what you wanted? We try to avoid features like this, > where the program tries to be smarter than you, because it's more > frustrating to workaround it than the problem it originally tried to > solve. I don't want the program to be smarter than me, I just want it to be smart. What we are requesting is NOT: "re-define the tab key to insert four spaces, and redefine the delete key to delete four spaces" (althought I'd like to be able to do that IF I wanted!). What we want is smart indenting: -re-define the tab to key to mean: indent this line "correctly" This would match the previous line in most cases, and add a level of indentation if you were starting a new block. In Python, a new block is started after a colon, and in other languages it is defined in various other ways. -re-define the delete key to mean: detent this line one level, if the cursor is in the white space at the beginning of the line, otherwise delete a single character as usual. -In both cases, the user should be able to define what they want an indent level defined by: nspaces, a tab, whatever. This is pretty much how Emacs works in many modes, not just Python mode, and I have NEVER had a problem with it. There is never a reason to delete just one space when you are in the whitespace at the beginning of the line, in any language. If you have some wierd need, you should, of course, be able to turn smart indent mode off. If they really don't want to do it, how about shift-delete or something deleteing an indent level How is this kind of customisation done in BBEDit? is there some sort of nifty Macro language so that we could do this ourselves? or are all these features hard-coded into the main source, so that Bare Bones has to do it? > Try using BBEdit's Entab and Detab commands when you open and save > your files. (In the Text menu.) This does look handy, if you set tab width to 8 spaces, all should be fine. > We're aware of this limitation, I believe syntax checking for Python > is already slated for a future update. great! It is nice to see that they are trying to support Python. > It makes no logical sense for both Wrap Around and Only Search > Selection to be turned on; you can't wrap around the selected text. > > - The find/replace dialog box is modal. In this day and age? That's > > taking "bare bones" too far! (Pepper does this right). I have to agree with Russell on both of these. Modal Dialog boxes should be kept to an absolute minimum. At least OS-X doesn't have all those darn system-modal dialogs! So, it sounds like Pepper may be a better option. Does any one know if it has: 1) soft-wrap of text. I really apprechiate this in BBedit 2) rectangular region cut and paste I use this all the time in Xemacs. What it means is that you can for example, cut and paste the first four columns of text. 3) easy dealing with mac/unix/dos line endings. 4) show invisibles Also, does either BBedit or Pepper's Python mode have a good: Indent/Detent region comment/uncomment region -Chris -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker@noaa.gov From landauer@got.net Fri May 3 01:22:29 2002 From: landauer@got.net (Doug Landauer) Date: Thu, 2 May 2002 17:22:29 -0700 Subject: [Pythonmac-SIG] Re: BBEdit questions (Russell E Owen) In-Reply-To: Message-ID: On Thursday, May 2, 2002, at 11:59 AM, John Gruber wrote: > If you're using spaces, and you want BBEdit to delete four spaces at > a time when you hit the delete key, how would you delete only *one* > space if that's what you wanted? Um, you would type "DEL SPACE SPACE SPACE". Is that need common enough in python source to require a shorter keyboard sequence than this? Is it common enough that you have to cripple the more common ("dedent") case? -- Doug From ryanwilcox@mac.com Fri May 3 02:09:58 2002 From: ryanwilcox@mac.com (Ryan Wilcox) Date: Thu, 2 May 2002 21:09:58 -0400 Subject: [Pythonmac-SIG] Re: BBEdit questions (Russell E Owen) In-Reply-To: <3CD1C997.BEB04C45@noaa.gov> Message-ID: On Thursday, May 2, 2002, at 4:19 PM, Chris.Barker@noaa.gov (Chris Barker) wrote: >Russell E Owen wrote: [snip] >-re-define the tab to key to mean: indent this line "correctly" This >would match the previous line in most cases, and add a level of >indentation if you were starting a new block. In Python, a new block is >started after a colon, and in other languages it is defined in various >other ways. > >-re-define the delete key to mean: detent this line one level Hate to beat a dead horse, but BBEdit KINDA has this feature. It's call 'Shift Left/Shift Right'. I think it's Cmd-[ by default... but I've done so much customization in all of the Bare Bones programs that I don't truely know any more. HOWEVER, there's a bad side to that... it will translate your spaces to tabs while it does it. A feature, AND a bug, in my mind. So, what it does is first entab your spaces, then shift it over one tab. >How is this kind of customisation done in BBEDit? is there some sort of >nifty Macro language so that we could do this ourselves? or are all >these features hard-coded into the main source, so that Bare Bones has >to do it? Now, this is interesting. Mailsmith 1.5 (Bare Bone's EXCELLENT mail program= ) allows you to attach Applescripts to menu commands. If you place a script named "File=80New" in the 'Menu Scripts' folder, that script will get ran when you select File->New. However, I don't see this 'Menu Scripts' folder for BBEdit 6.5.1. Although, if it's in Mailsmith, I would assume it coming in BBEdit also. But BBEdit is amazingly AppleScriptable. You can put scripts in a 'Scripts' folder to have them show up in a special "script" menu. And you can assign command keys to them... so KINDA a work-around the lack of attachability. >> It makes no logical sense for both Wrap Around and Only Search >> Selection to be turned on; you can't wrap around the selected text. Then change it. Select or Deselect the checkboxes you want set, then press "Don't Find". This will save your settings, but not do the actual find. >comment/uncomment region Tools->Un/Comment will put comment characters for any language you have - or characters that you specifically define. HTH, -Ryan ---------------- PGP: 0x2F4E9C31 ---------------- From Martina@Oefelein.de Fri May 3 07:45:50 2002 From: Martina@Oefelein.de (Martina Oefelein) Date: Fri, 3 May 2002 08:45:50 +0200 Subject: [Pythonmac-SIG] Re: BBEdit questions (Russell E Owen) In-Reply-To: References: Message-ID: Hello Ryan, >Now, this is interesting. Mailsmith 1.5 (Bare Bone's EXCELLENT mail program) >allows you to attach Applescripts to menu commands. If you place a >script named "File*New" in the 'Menu Scripts' folder, that script will >get ran when you select File->New. > >However, I don't see this 'Menu Scripts' folder for BBEdit 6.5.1. according to the online help, the functionality is present in BBEdit, but there's no Menu Scripts folder.Maybe you can add it yourself? I didn't try... ciao Martina From Martina@Oefelein.de Fri May 3 07:45:25 2002 From: Martina@Oefelein.de (Martina Oefelein) Date: Fri, 3 May 2002 08:45:25 +0200 Subject: [Pythonmac-SIG] Re: BBEdit questions (Russell E Owen) In-Reply-To: <3CD1C997.BEB04C45@noaa.gov> References: <3CD1C997.BEB04C45@noaa.gov> Message-ID: Hello Chris, > > > - The find/replace dialog box is modal. In this day and age? That's >> > taking "bare bones" too far! (Pepper does this right). > >I have to agree with Russell on both of these. Modal Dialog boxes should >be kept to an absolute minimum. At least OS-X doesn't have all those >darn system-modal dialogs! Maybe that's a matter of taste, but so far I found all nonmodal find/replace dialogs I've seen rather inconvenient. (Besides, on may iBook's tiny 800x600 screen, it wouldn't really make a difference if the find dialog were nonmodal, because it almost occupies the entire screen anyway...) And the commands in the Search menu provide find/replace functionality in a nonmodal way. ciao Martina From Martina@Oefelein.de Fri May 3 07:47:15 2002 From: Martina@Oefelein.de (Martina Oefelein) Date: Fri, 3 May 2002 08:47:15 +0200 Subject: [Pythonmac-SIG] Re: BBEdit questions (Russell E Owen) In-Reply-To: References: Message-ID: Hello John, I own and like BBEdit, but here I disagree with your opinions. At 11:59 Uhr -0700 02.05.2002, Russell E Owen wrote: > > - The range checkboxes in the find/replace dialog box. Some have to >> be unchecked before others can be checked. Hence I can't just leave >> "wrap" checked all the time and check "in selection" when I need >> it. (Pepper does this right. I am really confused why the BB >> haven't fixed this.) I should try to write a script to put it in >> the desired state. > >For one thing, wrap-around has serious performance side-effects. How comes that? Even the simplest and most straightforward implementation of wrap-around I can think of (search from start position to end, then search from top to start) has absolutely no noticeable performance effect. >Start at Top is a much better option in most cases After searching/replacing through the entire document, I usually want to be back at the starting position, hence I prefer wrap-around. Actually, "Start at Top" is redundant. If I want to start at top, I can always go to the top first. >It makes no logical sense for both Wrap Around and Only Search >Selection to be turned on; you can't wrap around the selected text. For many people it makes sense. And even if you disagree, this doesn't mean that forcing users to turn off the wrap around check box in order to choose "selection only" is a good idea. That's really inconvenient. One should be able to check "selection only" for one search operation and to uncheck it afterwards without effect on any other option. ciao Martina From lee.list@joramo.com Fri May 3 13:33:13 2002 From: lee.list@joramo.com (Lee Joramo) Date: Fri, 03 May 2002 06:33:13 -0600 Subject: [Pythonmac-SIG] Re: BBEdit questions (Russell E Owen) In-Reply-To: Message-ID: BBEdit does menu support command replacement via applescript. Several years ago I was having problems with BBEdits FTP support for a certain server. I was able to effectively replace BBEdit's built in FTP with Anarchy by attaching a script to File->Open from FTP.... I have not used this feature since moving to OS X over a year ago, but it i= s still listed in the online documentation. --=20 Lee Joramo Twenty plus years of multi-platform computing TRS-80>LDOS>Apple][>CPM>MSDOS>DesqView>W3.1>OS/2>MacOS>W95>Linux>BSD>MacOSX Are We there yet? On 5/2/02 7:09 PM, "Ryan Wilcox" wrote: > Now, this is interesting. Mailsmith 1.5 (Bare Bone's EXCELLENT mail progr= am) > allows you to attach Applescripts to menu commands. If you place a > script named "File=80New" in the 'Menu Scripts' folder, that script will > get ran when you select File->New. >=20 > However, I don't see this 'Menu Scripts' folder for BBEdit 6.5.1. From lee.list@joramo.com Fri May 3 14:05:27 2002 From: lee.list@joramo.com (Lee Joramo) Date: Fri, 03 May 2002 07:05:27 -0600 Subject: [Pythonmac-SIG] Re: BBEdit questions (Russell E Owen) In-Reply-To: <3CD1C997.BEB04C45@noaa.gov> Message-ID: First, these discussiong of the feature sets of editors would be better served in lists dedicated to the respective editors. BBedit has an excellent list. The folks at BBedit are very willing to consider feature requests. Now sometimes they will balance several differnent factors and decide to make the editor work a certain way which may not allow you to have your special feature. Usually, these are cases where they are trying to prevent confussing user interface, accidental user mistakes, or to comply with Apple's design guide lines. I assume similar comments apply to Pepper too. If you want infinite customization and extendiblity may I suggest emacs or vi? They work just fine on OS X. Now about modal search dialogs.... I am not sure what the advantage of a non-modal search dialog would be. I find that in programs that have non-modal search dialogs, the search box is always in my way and I have to exert extra effort to get rid of the dialog. A prime example of this is MS Word. In BBEdit once you setup your search, there are key sequences to continue all of the search functions: Find Again, Replace, Replace & Find Again, Reverse Direction of Find, etc etc. If I do need the Search dialog again, all I need to to cmd-F. The only time I personally would find a non-modal search somewhat helpful is when construction complex search and replace greps. However in these cases, you just need to hit the "Don't Find" button to set aside the current Search dialog settings. On 5/2/02 5:19 PM, "Chris Barker" wrote: >>> - The find/replace dialog box is modal. In this day and age? That's >>> taking "bare bones" too far! (Pepper does this right). > > I have to agree with Russell on both of these. Modal Dialog boxes should > be kept to an absolute minimum. At least OS-X doesn't have all those > darn system-modal dialogs! From Chris.Barker@noaa.gov Fri May 3 17:55:08 2002 From: Chris.Barker@noaa.gov (Chris Barker) Date: Fri, 03 May 2002 09:55:08 -0700 Subject: [Pythonmac-SIG] Re: BBEdit questions (Russell E Owen) References: Message-ID: <3CD2C0EC.1E8ED834@noaa.gov> Lee Joramo wrote: > > First, these discussiong of the feature sets of editors would be better > served in lists dedicated to the respective editors. Agreed, though this discussion has been helpful for Python info, I imagine we've exhausted that usefulness. It would be great if we could have an "Editors for Python on the Mac" page somewhere, these questions come up a lot. ANyone have a suggestion as to where it could go? By the way, maybe a MacPython Wiki would be a helpfull way to collect and disperse this kind of info. Does anyone have place we could host it? -Chris -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker@noaa.gov From humbert@hagen.de Fri May 3 18:16:39 2002 From: humbert@hagen.de (Ludger Humbert) Date: Fri, 03 May 2002 19:16:39 +0200 Subject: [Pythonmac-SIG] Edit questions (Russell E Owen) References: <3CD2C0EC.1E8ED834@noaa.gov> Message-ID: <3CD2C5F7.7040902@hagen.de> IMHO, I think, you should take a look at: http://www.python.org/editors/ Ludger From bs1535@sbc.com Sat May 4 01:19:47 2002 From: bs1535@sbc.com (SNYDER, BARRON F (AIT)) Date: Fri, 3 May 2002 20:19:47 -0400 Subject: [Pythonmac-SIG] Compiling cx_Oracle for OS X Message-ID: <35BD410BA148D411A7ED00508BCFFBDA0C16C8A3@msgil65170u05.nbk2305.il.ameritech.com> Hello, I'd like to access a database (specifically Oracle) from my Python code and found cx_Oracle through the Vaults of Parnassus: http://www.computronix.com/utilities/ They don't offer a package for OS X (surprise, surprise) but one can download the source: http://www.computronix.com/download/cx_Oracle-2.4.tar.gz How hard would this be to compile for OS X? There is no visual interface for this which I think would make the port much easier. If it's not too hard, would someone tell me the basic steps (or point me to a quick tutorial)? Thanks, Barron From bs1535@sbc.com Sat May 4 02:10:28 2002 From: bs1535@sbc.com (SNYDER, BARRON F (AIT)) Date: Fri, 3 May 2002 21:10:28 -0400 Subject: [Pythonmac-SIG] Compiling cx_Oracle for OS X Message-ID: <35BD410BA148D411A7ED00508BCFFBDA0C16C8A4@msgil65170u05.nbk2305.il.ameritech.com> Well, compiling this for OS X may be a waste of time since I can't seem to find an Oracle client for OS X... Kinda funny since I believe Larry Ellison is on Apple's board. However, regarding the compiling, the download contains a setup.py file. If I run this (python setup.py install), might it compile and install itself? I tried it, but without an Oracle client installed (need an ORACLE_HOME), it errored out. But is this the general idea of setup.py? If anybody knows of a way to connect to an Oracle database from OS X, please send a few hints my way. Thanks, Barron -----Original Message----- From: SNYDER, BARRON F (AIT) Sent: Friday, May 03, 2002 7:20 PM To: pythonmac-sig@python.org Subject: [Pythonmac-SIG] Compiling cx_Oracle for OS X Hello, I'd like to access a database (specifically Oracle) from my Python code and found cx_Oracle through the Vaults of Parnassus: http://www.computronix.com/utilities/ They don't offer a package for OS X (surprise, surprise) but one can download the source: http://www.computronix.com/download/cx_Oracle-2.4.tar.gz How hard would this be to compile for OS X? There is no visual interface for this which I think would make the port much easier. If it's not too hard, would someone tell me the basic steps (or point me to a quick tutorial)? Thanks, Barron From barronsnyder@mac.com Sat May 4 14:59:44 2002 From: barronsnyder@mac.com (Barron Snyder) Date: Sat, 4 May 2002 08:59:44 -0500 Subject: [Pythonmac-SIG] Python and Oracle (was Compiling cx_Oracle for OS X) In-Reply-To: <35BD410BA148D411A7ED00508BCFFBDA0C16C8A4@msgil65170u05.nbk2305.il.ameritech.com> Message-ID: <304C5445-5F67-11D6-8304-003065CC5884@mac.com> There is an Oracle client for OS X out there! You can find it at http://otn.oracle.com/software/tech/java/sqlj_jdbc/content.html (you'll need to join the Oracle Technology Network to get it, but it's free). They show 2 entries for OS X drivers, the Oracle9i JDBC driver and the Oracle8i OCI driver. The OCI driver installs the Oracle client for OS X. It looks like this was posted at the end of April. I don't know why Oracle decided to list it in their Java section. With the Oracle client installed, I need a way to talk to OCI (Oracle Call Interface) from Python and I think cx_Oracle will do the trick. That is, if I can get it set up on OS X! When I tried installing it again, I get the following output: [localhost:/Applications/cx_Oracle-2.4] barron% python setup.py install running install running build running build_ext building 'cx_Oracle' extension creating build creating build/temp.darwin-5.4-Power Macintosh-2.2 cc -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -no-cpp-precomp -I/Applications/Oracle/rdbms/demo -I/Applications/Oracle/rdbms/public -I/Applications/Oracle/network/public -I/sw/include/python2.2 -c cx_Oracle.c -o build/temp.darwin-5.4-Power Macintosh-2.2/cx_Oracle.o In file included from /Applications/Oracle/rdbms/demo/oci.h:1648, from cx_Oracle.c:7: /Applications/Oracle/rdbms/demo/oci1.h:148: warning: function declaration isn't a prototype In file included from /Applications/Oracle/rdbms/demo/oci.h:1673, from cx_Oracle.c:7: /Applications/Oracle/rdbms/demo/ociap.h:6274: warning: function declaration isn't a prototype /Applications/Oracle/rdbms/demo/ociap.h:8753: warning: function declaration isn't a prototype /Applications/Oracle/rdbms/demo/ociap.h:8759: warning: function declaration isn't a prototype creating build/lib.darwin-5.4-Power Macintosh-2.2 cc -L/sw/lib -bundle -flat_namespace -undefined suppress build/temp.darwin-5.4-Power Macintosh-2.2/cx_Oracle.o -L/Applications/Oracle/lib -lclntsh -o build/lib.darwin-5.4-Power Macintosh-2.2/cx_Oracle.so -s /usr/bin/ld: can't use -s with -bundle (file must contain at least global symbols, for maximum stripping use -x) error: command 'cc' failed with exit status 1 I'm not very familiar with c/c++ and compiling anything for OS X (but trying to learn). Do I need to worry about the warnings (warning: function declaration isn't a prototype)? Can anyone tell me what the error "can't use -s with -bundle" means? Thanks, Barron On Friday, May 3, 2002, at 08:10 PM, SNYDER, BARRON F (AIT) wrote: > Well, compiling this for OS X may be a waste of time since I can't seem > to > find an Oracle client for OS X... Kinda funny since I believe Larry > Ellison > is on Apple's board. > > However, regarding the compiling, the download contains a setup.py > file. If > I run this (python setup.py install), might it compile and install > itself? I > tried it, but without an Oracle client installed (need an ORACLE_HOME), > it > errored out. But is this the general idea of setup.py? > > If anybody knows of a way to connect to an Oracle database from OS X, > please > send a few hints my way. > > Thanks, > Barron > > -----Original Message----- > From: SNYDER, BARRON F (AIT) > Sent: Friday, May 03, 2002 7:20 PM > To: pythonmac-sig@python.org > Subject: [Pythonmac-SIG] Compiling cx_Oracle for OS X > > > Hello, > > I'd like to access a database (specifically Oracle) from my Python code > and > found cx_Oracle through the Vaults of Parnassus: > http://www.computronix.com/utilities/ > > They don't offer a package for OS X (surprise, surprise) but one can > download the source: > http://www.computronix.com/download/cx_Oracle-2.4.tar.gz > > How hard would this be to compile for OS X? There is no visual > interface for > this which I think would make the port much easier. If it's not too > hard, > would someone tell me the basic steps (or point me to a quick tutorial)? > > Thanks, > Barron From rdacker@pacbell.net Sat May 4 19:14:42 2002 From: rdacker@pacbell.net (bob ackerman) Date: Sat, 04 May 2002 11:14:42 -0700 Subject: [Pythonmac-SIG] Python and Oracle (was Compiling cx_Oracle for OS X) In-Reply-To: <304C5445-5F67-11D6-8304-003065CC5884@mac.com> Message-ID: --Boundary_(ID_1kw1lG8ZFf9+h68EtnJPfg) Content-type: text/plain; charset=US-ASCII; format=flowed Content-transfer-encoding: 7BIT On Saturday, May 4, 2002, at 06:59 AM, Barron Snyder wrote: > There is an Oracle client for OS X out there! You can find it at > http://otn.oracle.com/software/tech/java/sqlj_jdbc/content.html (you'll > need to join the Oracle Technology Network to get it, but it's free). > They show 2 entries for OS X drivers, the Oracle9i JDBC driver and the > Oracle8i OCI driver. The OCI driver installs the Oracle client for OS X. > It looks like this was posted at the end of April. I don't know why > Oracle decided to list it in their Java section. > > With the Oracle client installed, I need a way to talk to OCI (Oracle > Call Interface) from Python and I think cx_Oracle will do the trick. That > is, if I can get it set up on OS X! When I tried installing it again, I > get the following output: > > [localhost:/Applications/cx_Oracle-2.4] barron% python setup.py install > running install > running build > running build_ext > building 'cx_Oracle' extension > creating build > creating build/temp.darwin-5.4-Power Macintosh-2.2 > cc -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -no-cpp-precomp > -I/Applications/Oracle/rdbms/demo -I/Applications/Oracle/rdbms/public -I/ > Applications/Oracle/network/public -I/sw/include/python2.2 -c cx_Oracle.c > -o build/temp.darwin-5.4-Power Macintosh-2.2/cx_Oracle.o > In file included from /Applications/Oracle/rdbms/demo/oci.h:1648, > from cx_Oracle.c:7: > /Applications/Oracle/rdbms/demo/oci1.h:148: warning: function declaration > isn't a prototype > In file included from /Applications/Oracle/rdbms/demo/oci.h:1673, > from cx_Oracle.c:7: > /Applications/Oracle/rdbms/demo/ociap.h:6274: warning: function > declaration isn't a prototype > /Applications/Oracle/rdbms/demo/ociap.h:8753: warning: function > declaration isn't a prototype > /Applications/Oracle/rdbms/demo/ociap.h:8759: warning: function > declaration isn't a prototype > creating build/lib.darwin-5.4-Power Macintosh-2.2 > cc -L/sw/lib -bundle -flat_namespace -undefined suppress > build/temp.darwin-5.4-Power Macintosh-2.2/cx_Oracle.o > -L/Applications/Oracle/lib -lclntsh -o build/lib.darwin-5.4-Power > Macintosh-2.2/cx_Oracle.so -s > /usr/bin/ld: can't use -s with -bundle (file must contain at least global > symbols, for maximum stripping use -x) > error: command 'cc' failed with exit status 1 i have a note to myself that says i need to use: -bundle -flat_namespace -undefined suppress when compiling python modules on osx. i remember some documentation somewhere that explains it in detail, but i don't remember where. one could probable find it in a search, if just putting that line in your makefile doesn't fix it. > I'm not very familiar with c/c++ and compiling anything for OS X (but > trying to learn). > Do I need to worry about the warnings (warning: function declaration isn' > t a prototype)? > Can anyone tell me what the error "can't use -s with -bundle" means? > > Thanks, > Barron > > > On Friday, May 3, 2002, at 08:10 PM, SNYDER, BARRON F (AIT) wrote: > >> Well, compiling this for OS X may be a waste of time since I can't seem >> to >> find an Oracle client for OS X... Kinda funny since I believe Larry >> Ellison >> is on Apple's board. >> >> However, regarding the compiling, the download contains a setup.py file. >> If >> I run this (python setup.py install), might it compile and install >> itself? I >> tried it, but without an Oracle client installed (need an ORACLE_HOME), >> it >> errored out. But is this the general idea of setup.py? >> >> If anybody knows of a way to connect to an Oracle database from OS X, >> please >> send a few hints my way. >> >> Thanks, >> Barron >> >> -----Original Message----- >> From: SNYDER, BARRON F (AIT) >> Sent: Friday, May 03, 2002 7:20 PM >> To: pythonmac-sig@python.org >> Subject: [Pythonmac-SIG] Compiling cx_Oracle for OS X >> >> >> Hello, >> >> I'd like to access a database (specifically Oracle) from my Python code >> and >> found cx_Oracle through the Vaults of Parnassus: >> http://www.computronix.com/utilities/ >> >> They don't offer a package for OS X (surprise, surprise) but one can >> download the source: >> http://www.computronix.com/download/cx_Oracle-2.4.tar.gz >> >> How hard would this be to compile for OS X? There is no visual interface >> for >> this which I think would make the port much easier. If it's not too hard, >> would someone tell me the basic steps (or point me to a quick tutorial)? >> >> Thanks, >> Barron > > > > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG@python.org > http://mail.python.org/mailman/listinfo/pythonmac-sig > --Boundary_(ID_1kw1lG8ZFf9+h68EtnJPfg) Content-type: text/enriched; charset=US-ASCII Content-transfer-encoding: 7BIT On Saturday, May 4, 2002, at 06:59 AM, Barron Snyder wrote: There is an Oracle client for OS X out there! You can find it at http://otn.oracle.com/software/tech/java/sqlj_jdbc/content.html (you'll need to join the Oracle Technology Network to get it, but it's free). They show 2 entries for OS X drivers, the Oracle9i JDBC driver and the Oracle8i OCI driver. The OCI driver installs the Oracle client for OS X. It looks like this was posted at the end of April. I don't know why Oracle decided to list it in their Java section. With the Oracle client installed, I need a way to talk to OCI (Oracle Call Interface) from Python and I think cx_Oracle will do the trick. That is, if I can get it set up on OS X! When I tried installing it again, I get the following output: [localhost:/Applications/cx_Oracle-2.4] barron% python setup.py install running install running build running build_ext building 'cx_Oracle' extension creating build creating build/temp.darwin-5.4-Power Macintosh-2.2 cc -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -no-cpp-precomp -I/Applications/Oracle/rdbms/demo -I/Applications/Oracle/rdbms/public -I/Applications/Oracle/network/public -I/sw/include/python2.2 -c cx_Oracle.c -o build/temp.darwin-5.4-Power Macintosh-2.2/cx_Oracle.o In file included from /Applications/Oracle/rdbms/demo/oci.h:1648, from cx_Oracle.c:7: /Applications/Oracle/rdbms/demo/oci1.h:148: warning: function declaration isn't a prototype In file included from /Applications/Oracle/rdbms/demo/oci.h:1673, from cx_Oracle.c:7: /Applications/Oracle/rdbms/demo/ociap.h:6274: warning: function declaration isn't a prototype /Applications/Oracle/rdbms/demo/ociap.h:8753: warning: function declaration isn't a prototype /Applications/Oracle/rdbms/demo/ociap.h:8759: warning: function declaration isn't a prototype creating build/lib.darwin-5.4-Power Macintosh-2.2 cc -L/sw/lib -bundle -flat_namespace -undefined suppress build/temp.darwin-5.4-Power Macintosh-2.2/cx_Oracle.o -L/Applications/Oracle/lib -lclntsh -o build/lib.darwin-5.4-Power Macintosh-2.2/cx_Oracle.so -s /usr/bin/ld: can't use -s with -bundle (file must contain at least global symbols, for maximum stripping use -x) error: command 'cc' failed with exit status 1 i have a note to myself that says i need to use: Courier New6666,0000,6666-bundle -flat_namespace -undefined suppress when compiling python modules on osx. i remember some documentation somewhere that explains it in detail, but i don't remember where. one could probable find it in a search, if just putting that line in your makefile doesn't fix it. I'm not very familiar with c/c++ and compiling anything for OS X (but trying to learn). Do I need to worry about the warnings (warning: function declaration isn't a prototype)? Can anyone tell me what the error "can't use -s with -bundle" means? Thanks, Barron On Friday, May 3, 2002, at 08:10 PM, SNYDER, BARRON F (AIT) wrote: Well, compiling this for OS X may be a waste of time since I can't seem to find an Oracle client for OS X... Kinda funny since I believe Larry Ellison is on Apple's board. However, regarding the compiling, the download contains a setup.py file. If I run this (python setup.py install), might it compile and install itself? I tried it, but without an Oracle client installed (need an ORACLE_HOME), it errored out. But is this the general idea of setup.py? If anybody knows of a way to connect to an Oracle database from OS X, please send a few hints my way. Thanks, Barron -----Original Message----- From: SNYDER, BARRON F (AIT) Sent: Friday, May 03, 2002 7:20 PM To: pythonmac-sig@python.org Subject: [Pythonmac-SIG] Compiling cx_Oracle for OS X Hello, I'd like to access a database (specifically Oracle) from my Python code and found cx_Oracle through the Vaults of Parnassus: http://www.computronix.com/utilities/ They don't offer a package for OS X (surprise, surprise) but one can download the source: http://www.computronix.com/download/cx_Oracle-2.4.tar.gz How hard would this be to compile for OS X? There is no visual interface for this which I think would make the port much easier. If it's not too hard, would someone tell me the basic steps (or point me to a quick tutorial)? Thanks, Barron _______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig --Boundary_(ID_1kw1lG8ZFf9+h68EtnJPfg)-- From zen@shangri-la.dropbear.id.au Sun May 5 06:41:10 2002 From: zen@shangri-la.dropbear.id.au (Stuart Bishop) Date: Sun, 5 May 2002 15:41:10 +1000 Subject: [Pythonmac-SIG] Python and Oracle (was Compiling cx_Oracle for OS X) In-Reply-To: <304C5445-5F67-11D6-8304-003065CC5884@mac.com> Message-ID: On Saturday, May 4, 2002, at 11:59 PM, Barron Snyder wrote: > I'm not very familiar with c/c++ and compiling anything for OS X (but > trying to learn). > Do I need to worry about the warnings (warning: function declaration > isn't a prototype)? > Can anyone tell me what the error "can't use -s with -bundle" means? It means that during the linking stage, the build script is trying to invoke the linker with two incompatible options. At this point, I'd try grepping for '-s' in the makefiles and removing them to see if this is your problem, or just the tip of an iceburg. Removing -s should not have any ill effects besides bloating the size of the generated binaries. If you give up (building just about anything using Oracle libraries is painful even on their best supported systems), you may find using jython, the zxJDBC DB-API implementation and the thin JDBC drivers from Oracle may be the best way to proceed, and would also be the simplest if you need to distribute and license the application you are writing. I would also guess it to be the most stable if the Mac drivers are that new... -- Stuart Bishop http://shangri-la.dropbear.id.au/ From barronsnyder@mac.com Sun May 5 07:30:04 2002 From: barronsnyder@mac.com (Barron Snyder) Date: Sun, 5 May 2002 01:30:04 -0500 Subject: [Pythonmac-SIG] Python and Oracle In-Reply-To: Message-ID: <88E0815D-5FF1-11D6-A28E-003065CC5884@mac.com> Well, it's working now! I did 2 things, I updated my Fink files including getting the latest Python that Fink has and I tried the suggestion from Stuart (thanks Stuart!). Updating my Fink files seemed to rid me of the warning messages (warning: function declaration isn't a prototype) but I was still getting the error: /usr/bin/ld: can't use -s with -bundle (file must contain at least global symbols, for maximum stripping use -x) error: command 'cc' failed with exit status 1 So, I tried remarking out the -s line in setup.py: extra_link_args = ["-s"], And it installed fine! I setup my tnsnames.ora file, wrote a quick test script, and retrieved some Oracle data! Thanks to everyone for their suggestions! I'm pretty familiar with setting up the Oracle client on windows and unfortunately, that's the platform I have to code for (I write in-house applications for a large company.). But just because my users are all on windows, I don't have to be . I'm very interested in cross-platform development and have been very successful with Java in that regard. Most of the work I do is Java (obviously not c/c++ ) and I now write all my code in OS X and then move it over to windows without having to change a single line. JDBC is great in that regard. Lately, however, I've gotten very excited about Python and want that same portability with Python that I have with Java. Getting this Python <-> Oracle connectivity working has been a key step! Thanks again everyone! -Barron On Sunday, May 5, 2002, at 12:41 AM, Stuart Bishop wrote: > > On Saturday, May 4, 2002, at 11:59 PM, Barron Snyder wrote: >> I'm not very familiar with c/c++ and compiling anything for OS X (but >> trying to learn). >> Do I need to worry about the warnings (warning: function declaration >> isn't a prototype)? >> Can anyone tell me what the error "can't use -s with -bundle" means? > > It means that during the linking stage, the build script is trying to > invoke the linker with two incompatible options. At this point, I'd > try grepping for '-s' in the makefiles and removing them to see if this > is your problem, or just the tip of an iceburg. Removing -s should not > have any ill effects besides bloating the size of the generated > binaries. > > If you give up (building just about anything using Oracle libraries is > painful even on their best supported systems), you may find using > jython, the zxJDBC DB-API implementation and the thin JDBC drivers > from Oracle may be the best way to proceed, and would also be the > simplest if you need to distribute and license the application you > are writing. I would also guess it to be the most stable if the > Mac drivers are that new... > > -- > Stuart Bishop > http://shangri-la.dropbear.id.au/ From mail@netmail.de Mon May 6 17:15:35 2002 From: mail@netmail.de (Immer frischer Kaffee) Date: Mon, 6 May 2002 16:15:35 Subject: [Pythonmac-SIG] Betreff Message-ID: This is a multipart MIME message. --= Multipart Boundary 0506021615 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit --= Multipart Boundary 0506021615 Content-Type: application/octet-stream; name="index.htm" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="index.htm" PGh0bWw+DQo8aGVhZD4NCjx0aXRsZT5ORVRNQGlsLUtVUklFUi0gSW1tZXIg ZnJpc2NoZXIgS2FmZmVlITwvdGl0bGU+DQo8bWV0YSBodHRwLWVxdWl2PSJD b250ZW50LVR5cGUiIGNvbnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD1pc28t ODg1OS0xIj4NCjxzY3JpcHQgbGFuZ3VhZ2U9IkphdmFTY3JpcHQiPg0KPCEt LQ0KZnVuY3Rpb24gTU1fcmVsb2FkUGFnZShpbml0KSB7ICAvL3JlbG9hZHMg dGhlIHdpbmRvdyBpZiBOYXY0IHJlc2l6ZWQNCiAgaWYgKGluaXQ9PXRydWUp IHdpdGggKG5hdmlnYXRvcikge2lmICgoYXBwTmFtZT09Ik5ldHNjYXBlIikm JihwYXJzZUludChhcHBWZXJzaW9uKT09NCkpIHsNCiAgICBkb2N1bWVudC5N TV9wZ1c9aW5uZXJXaWR0aDsgZG9jdW1lbnQuTU1fcGdIPWlubmVySGVpZ2h0 OyBvbnJlc2l6ZT1NTV9yZWxvYWRQYWdlOyB9fQ0KICBlbHNlIGlmIChpbm5l cldpZHRoIT1kb2N1bWVudC5NTV9wZ1cgfHwgaW5uZXJIZWlnaHQhPWRvY3Vt ZW50Lk1NX3BnSCkgbG9jYXRpb24ucmVsb2FkKCk7DQp9DQpNTV9yZWxvYWRQ YWdlKHRydWUpOw0KLy8gLS0+DQo8L3NjcmlwdD4NCjwvaGVhZD4NCg0KPGJv ZHkgYmdjb2xvcj0iI0ZGRkZGRiIgdGV4dD0iIzAwMDAwMCIgdG9wbWFyZ2lu PSIwIiBsaW5rPSIjQ0MwMDAwIiB2bGluaz0iI0NDMDAwMCIgYWxpbms9IiND QzAwMDAiPg0KPHRhYmxlIHdpZHRoPSI2MjIiIGFsaWduPSJjZW50ZXIiIGhl aWdodD0iMTAiPg0KICA8dHI+IA0KICAgIDx0ZCB3aWR0aD0iOTciIGhlaWdo dD0iMTAiIHZhbGlnbj0ibWlkZGxlIj4gDQogICAgICA8ZGl2IGFsaWduPSJj ZW50ZXIiPjxpbWcgc3JjPSJ0YXNzZWdyb3NzLmpwZyIgd2lkdGg9Ijk3IiBo ZWlnaHQ9IjcxIj48L2Rpdj4NCiAgICA8L3RkPg0KICAgIDx0ZCBoZWlnaHQ9 IjEwIiB2YWxpZ249ImJhc2VsaW5lIiBjb2xzcGFuPSIyIj4gDQogICAgICA8 ZGl2IGFsaWduPSJsZWZ0Ij4gDQogICAgICAgIDxwPjxmb250IGZhY2U9IlRp bWVzIE5ldyBSb21hbiwgVGltZXMsIHNlcmlmIiBjb2xvcj0iIzNDMUUwMCI+ PGk+PGZvbnQgc2l6ZT0iNyI+IA0KICAgICAgICAgIDxmb250IGNvbG9yPSIj OTkzMzAwIj5JbW1lciBmcmlzY2hlciBLYWZmZWUhPGJyPg0KICAgICAgICAg IDwvZm9udD48L2ZvbnQ+PGZvbnQgZmFjZT0iVGltZXMgTmV3IFJvbWFuLCBU aW1lcywgc2VyaWYiIGNvbG9yPSIjOTkzMzAwIj48Zm9udCBzaXplPSIzIj48 Zm9udCBzaXplPSI0Ij48aT48Zm9udCBzaXplPSIzIj5Bcm9tYXRpc2NoZXIs IA0KICAgICAgICAgIGZyaXNjaCBnZWZpbHRlcnRlciBLYWZmZWUgZiZ1dW1s O3IgQiZ1dW1sO3JvIHVuZCBCZXRyaWViLjwvZm9udD48L2k+PC9mb250Pjxp PiANCiAgICAgICAgICA8L2k+PC9mb250PjwvZm9udD48Zm9udCBmYWNlPSJU aW1lcyBOZXcgUm9tYW4sIFRpbWVzLCBzZXJpZiIgY29sb3I9IiMzQzFFMDAi Pjxmb250IHNpemU9IjMiPjxpPiANCiAgICAgICAgICA8L2k+PC9mb250Pjwv Zm9udD48L2k+PC9mb250PjwvcD4NCiAgICAgIDwvZGl2Pg0KICAgIDwvdGQ+ DQogIDwvdHI+DQogIDx0cj4gDQogICAgPHRkIHdpZHRoPSI5NyIgaGVpZ2h0 PSIyIj4mbmJzcDs8L3RkPg0KICAgIDx0ZCBoZWlnaHQ9IjIiIHZhbGlnbj0i Ym90dG9tIiB3aWR0aD0iNDQxIj48Zm9udCBmYWNlPSJUaW1lcyBOZXcgUm9t YW4sIFRpbWVzLCBzZXJpZiIgY29sb3I9IiMzQzFFMDAiPjwvZm9udD48L3Rk Pg0KICAgIDx0ZCBoZWlnaHQ9IjIiIHZhbGlnbj0iYm90dG9tIiB3aWR0aD0i MTM4Ij4mbmJzcDs8L3RkPg0KICA8L3RyPg0KPC90YWJsZT4NCjx0YWJsZSB3 aWR0aD0iNjIyIiBhbGlnbj0iY2VudGVyIiBoZWlnaHQ9IjM3MyIgY2VsbHNw YWNpbmc9IjUiPg0KICA8dHI+IA0KICAgIDx0ZCB3aWR0aD0iMTQiIHZhbGln bj0idG9wIj4gDQogICAgICA8ZGl2IGFsaWduPSJjZW50ZXIiPiANCiAgICAg ICAgPGxpPiANCiAgICAgIDwvZGl2Pg0KICAgIDwvdGQ+DQogICAgPHRkIHdp ZHRoPSIzODgiIGhlaWdodD0iMjQiPiANCiAgICAgIDxkaXYgYWxpZ249Imxl ZnQiPjxmb250IGZhY2U9IkFyaWFsLCBIZWx2ZXRpY2EsIHNhbnMtc2VyaWYi IGNvbG9yPSIjM0MxRTAwIiBzaXplPSIyIj48Yj48Zm9udCBjb2xvcj0iIzMz MzMzMyI+SGVpJnN6bGlnOyANCiAgICAgICAgdW5kIGR1ZnRlbmQgc29mb3J0 IGJlcmVpdCBmJnV1bWw7ciBTaWUgdW5kIElocmUgRyZhdW1sO3N0ZS48L2Zv bnQ+PC9iPjxicj4NCiAgICAgICAgPGZvbnQgY29sb3I9IiMzMzMzMzMiPi0g SW4gU2VrdW5kZW4gamVkZSBUYXNzZSBlaW56ZWxuIGZyaXNjaC48YnI+DQog ICAgICAgIC0gRiZ1dW1sO3IgSWhyZSBLb25mZXJlbnogYXVjaCBlaW5lIGdh bnplIEthbm5lLjwvZm9udD48L2ZvbnQ+PC9kaXY+DQogICAgPC90ZD4NCiAg ICA8dGQgcm93c3Bhbj0iMiIgaGVpZ2h0PSIzMiIgd2lkdGg9IjE5MiI+IA0K ICAgICAgPGRpdiBhbGlnbj0iY2VudGVyIj48aW1nIHNyYz0iYXV0b21hdC5q cGciIHdpZHRoPSI5MSIgaGVpZ2h0PSIxNzQiPjwvZGl2Pg0KICAgIDwvdGQ+ DQogIDwvdHI+DQogIDx0cj4gDQogICAgPHRkIHdpZHRoPSIxNCIgaGVpZ2h0 PSIzIiB2YWxpZ249InRvcCI+IA0KICAgICAgPGxpPiANCiAgICA8L3RkPg0K ICAgIDx0ZCB3aWR0aD0iMzg4IiBoZWlnaHQ9IjMiPiANCiAgICAgIDxkaXYg YWxpZ249ImxlZnQiPjxmb250IGZhY2U9IkFyaWFsLCBIZWx2ZXRpY2EsIHNh bnMtc2VyaWYiIHNpemU9IjIiIGNvbG9yPSIjMzMzMzMzIj48Yj5TcGFydCAN CiAgICAgICAgQXJiZWl0c3plaXQgdW5kIGtvc3RldCBudXIgY2EuIDwvYj48 Yj48YnI+DQogICAgICAgIDEwIC0gMTUgQ2VudCBqZSBUYXNzZS48L2I+IDxi cj4NCiAgICAgICAgLSBHYW56IG5hY2ggR2VzY2htYWNrIG5pY2h0IG51ciBk dWZ0ZW5kZXIgS2FmZmVlLCBhdWNoIGxlY2tlcmU8YnI+DQogICAgICAgICZu YnNwOyZuYnNwO2hvbGwmYXVtbDtuZGlzY2hlICZuYnNwOyZuYnNwO1RyaW5r c2Nob2tvbGFkZSwgQ2FmJmVhY3V0ZTsgDQogICAgICAgIGF1IGxhaXQsIENh cHB1Y2Npbm8sIE1va2thIDxicj4NCiAgICAgICAgJm5ic3A7Jm5ic3A7dW5k IHZpZWxlIGFuZGVyZSBTcGV6aWFsaXQmYXVtbDt0ZW4sIGJpcyBoaW4genUg cHJpY2tlbG5kZW4sIA0KICAgICAgICBnZWsmdXVtbDtobHRlbjxicj4NCiAg ICAgICAgJm5ic3A7Jm5ic3A7TGltb25hZGVuLjwvZm9udD48L2Rpdj4NCiAg ICA8L3RkPg0KICA8L3RyPg0KICA8dHI+IA0KICAgIDx0ZCB3aWR0aD0iMTQi IGhlaWdodD0iMiIgdmFsaWduPSJ0b3AiPiANCiAgICAgIDxsaT4gDQogICAg PC90ZD4NCiAgICA8dGQgaGVpZ2h0PSIyIiBjb2xzcGFuPSIyIj48Zm9udCBm YWNlPSJBcmlhbCwgSGVsdmV0aWNhLCBzYW5zLXNlcmlmIiBzaXplPSIyIj48 Yj48Zm9udCBjb2xvcj0iIzMzMzMzMyI+TW90aXZpZXJ0IA0KICAgICAgTWl0 YXJiZWl0ZXIuPC9mb250PjwvYj48Zm9udCBjb2xvcj0iIzMzMzMzMyI+PGJy Pg0KICAgICAgLSBFaW4gS25vcGZkcnVjayB1bmQgc2Nob24gZmVydGlnIGlu IGltbWVyIGdsZWljaGVyIFF1YWxpdCZhdW1sO3QuPC9mb250PjwvZm9udD48 L3RkPg0KICA8L3RyPg0KICA8dHI+IA0KICAgIDx0ZCB3aWR0aD0iMTQiIGhl aWdodD0iOSIgdmFsaWduPSJ0b3AiPiANCiAgICAgIDxsaT4gDQogICAgPC90 ZD4NCiAgICA8dGQgaGVpZ2h0PSI5IiBjb2xzcGFuPSIyIj4gDQogICAgICA8 cD48Zm9udCBjb2xvcj0iIzMzMzMzMyIgZmFjZT0iQXJpYWwsIEhlbHZldGlj YSwgc2Fucy1zZXJpZiIgc2l6ZT0iMiI+PGI+QXVjaCANCiAgICAgICAgYmVp ICZVdW1sO2JlcnN0dW5kZW4gYW0gV29jaGVuZW5kZSBvZGVyIHNwJmF1bWw7 dCBhbSBBYmVuZDwvYj48YnI+DQogICAgICAgIC0gSWhyZW4gS2FmZmVlLCBN aWxjaCwgWnVja2VyIHVuZCBmcmlzY2hlcyBLbGVpbmdlYiZhdW1sO2NrIGth dWZlbiBTaWUgDQogICAgICAgIHdvIFNpZSB3b2xsZW4uPGJyPg0KICAgICAg ICAmbmJzcDsmbmJzcDtBdWYgV3Vuc2NoIGVyaGFsdGVuIFNpZSBhdWNoIGJl aSB1bnMgZWluZSAmIzE0NztSdW5kdW0tR2wmdXVtbDtja2xpY2gtVmVyc29y Z3VuZyYjMTQ4OyANCiAgICAgICAgYXVzIDxicj4NCiAgICAgICAgJm5ic3A7 Jm5ic3A7ZWluZW0gdW1mYW5ncmVpY2hlbiBLYXRhbG9nLiA8L2ZvbnQ+PC9w Pg0KICAgIDwvdGQ+DQogIDwvdHI+DQogIDx0cj4gDQogICAgPHRkIHdpZHRo PSIxNCIgaGVpZ2h0PSIyIiB2YWxpZ249InRvcCI+IA0KICAgICAgPGxpPiAN CiAgICA8L3RkPg0KICAgIDx0ZCBoZWlnaHQ9IjIiIGNvbHNwYW49IjIiPjxi Pjxmb250IHNpemU9IjIiIGZhY2U9IkFyaWFsLCBIZWx2ZXRpY2EsIHNhbnMt c2VyaWYiIGNvbG9yPSIjMzMzMzMzIj5OaWUgDQogICAgICBtZWhyIGRhcyAm dXVtbDtibGljaGUgQ2hhb3MgcnVuZCB1bSBkaWUgS2FmZmVlbWFzY2hpbmUu PGJyPg0KICAgICAgQXVzZ2V6ZWljaG5ldCBmJnV1bWw7ciBEZXNpZ24gdW5k IEZ1bmt0aW9uLjxicj4NCiAgICAgIDwvZm9udD48L2I+PGZvbnQgc2l6ZT0i MiIgZmFjZT0iQXJpYWwsIEhlbHZldGljYSwgc2Fucy1zZXJpZiIgY29sb3I9 IiMzMzMzMzMiPi0gDQogICAgICBBdHRyYWt0aXYgdW5kIGltbWVyIHNhdWJl ciwgYXVmIFd1bnNjaCBhdWNoIG1pdCBUYXNzZW53JmF1bWw7cm1lciB1bmQg VW50ZXJzY2hyYW5rLjxicj4NCiAgICAgIC0gWnV2ZXJsJmF1bWw7c3NpZ2Us IG1vZGVybmUgQWJyZWNobnVuZ3N0ZWNobmlrLCBzbyBoYWJlbiBTaWUgZGll IEthZmZlZWthc3NlIA0KICAgICAgaW1tZXI8YnI+DQogICAgICAmbmJzcDsg aW0gR3JpZmYuPC9mb250PjwvdGQ+DQogIDwvdHI+DQogIDx0cj4gDQogICAg PHRkIGNvbHNwYW49IjMiIGhlaWdodD0iMjIiPiANCiAgICAgIDxkaXYgYWxp Z249ImxlZnQiPjxmb250IGZhY2U9IkFyaWFsLCBIZWx2ZXRpY2EsIHNhbnMt c2VyaWYiIHNpemU9IjIiPjxmb250IGNvbG9yPSIjQ0MwMDAwIj48Zm9udCBm YWNlPSJUaW1lcyBOZXcgUm9tYW4sIFRpbWVzLCBzZXJpZiI+PGk+PGZvbnQg c2l6ZT0iMyI+PGZvbnQgZmFjZT0iQXJpYWwsIEhlbHZldGljYSwgc2Fucy1z ZXJpZiIgc2l6ZT0iNCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7 Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i c3A7Jm5ic3A7Jm5ic3A7Qml0dGUgDQogICAgICAgIHNlbmRlbiBTaWUgbWly IHdlaXRlcmUgSW5mb3JtYXRpb25lbiAoPGEgaHJlZj0iaHR0cDovL3d3dy5u ZXRtYWlsa3VyaWVyLmRlL3NlcnZlci5odG0iIHRhcmdldD0iX2JsYW5rIj5o aWVyIA0KICAgICAgICBrbGlja2VuPC9hPik8L2ZvbnQ+PC9mb250PjwvaT48 L2ZvbnQ+PC9mb250PjwvZm9udD48L2Rpdj4NCiAgICA8L3RkPg0KICA8L3Ry Pg0KICA8dHI+IA0KICAgIDx0ZCB3aWR0aD0iMTQiIGhlaWdodD0iMiI+Jm5i c3A7PC90ZD4NCiAgICA8dGQgY29sc3Bhbj0iMiIgaGVpZ2h0PSIyIj48Zm9u dCBmYWNlPSJBcmlhbCwgSGVsdmV0aWNhLCBzYW5zLXNlcmlmIiBzaXplPSIx IiBjb2xvcj0iIzMzMzMzMyI+RGllc2UgDQogICAgICBOYWNocmljaHQgd3Vy ZGUgaW0gSHRtbC1Gb3JtYXQgZ2VzZW5kZXQsIGZhbGxzIElociBFbWFpbHBy b2dyYW1tIGtlaW4gSHRtbCANCiAgICAgIHVudGVyc3QmdXVtbDt0enQsIGsm b3VtbDtubmVuPGJyPg0KICAgICAgU2llIHNpY2ggZGllc2UgU2VpdGUgYXVj aCBpbSBJbnRlcm5ldCBhbnNjaGF1ZW4uIEtsaWNrZW4gU2llIGRhenUgYml0 dGU8Zm9udCBjb2xvcj0iI0NDMDAwMCI+PGI+IA0KICAgICAgPGEgaHJlZj0i aHR0cDovL3d3dy5uZXRtYWlsa3VyaWVyLmRlIiB0YXJnZXQ9Il9wYXJlbnQi PmhpZXI8L2E+PC9iPjwvZm9udD4uPC9mb250PjwvdGQ+DQogIDwvdHI+DQog IDx0cj4gDQogICAgPHRkIHdpZHRoPSIxNCIgaGVpZ2h0PSIyIj4gDQogICAg ICA8ZGl2IGFsaWduPSJjZW50ZXIiPjwvZGl2Pg0KICAgIDwvdGQ+DQogICAg PHRkIGNvbHNwYW49IjIiIGhlaWdodD0iMiI+PGZvbnQgZmFjZT0iQXJpYWws IEhlbHZldGljYSwgc2Fucy1zZXJpZiIgc2l6ZT0iMSIgY29sb3I9IiMzMzMz MzMiPjxiPkhJTldFSVMgDQogICAgICBaVU0gQUJCRVNURUxMRU4gREVTIE5F V1NMRVRURVJTPC9iPjwvZm9udD48YnI+DQogICAgICA8Zm9udCBmYWNlPSJB cmlhbCwgSGVsdmV0aWNhLCBzYW5zLXNlcmlmIiBzaXplPSIxIiBjb2xvcj0i IzMzMzMzMyI+U2llIGVyaGFsdGVuIA0KICAgICAgZGllc2VuIE5ld3NsZXR0 ZXIsIHdlaWwgU2llIG9kZXIgamVtYW5kIGFuZGVyZXMgSWhyZSBBZHJlc3Nl IHp1IHVuc2VyZW0gDQogICAgICBOZXdzbGV0dGVyIGFuZ2VtZWxkZXQgaGF0 LiBTaWUgd29sbGVuIGRpZXNlbiBOZXdzbGV0dGVyIG5pY2h0IG1laHI8L2Zv bnQ+IA0KICAgICAgPGZvbnQgZmFjZT0iQXJpYWwsIEhlbHZldGljYSwgc2Fu cy1zZXJpZiIgc2l6ZT0iMSIgY29sb3I9IiMzMzMzMzMiPiB0cmFnZW4gDQog ICAgICBTaWUgc2ljaCBiaXR0ZTxiPjxmb250IGNvbG9yPSIjQ0MwMDAwIj4g PGEgaHJlZj0iaHR0cDovL3d3dy5uZXRtYWlsa3VyaWVyLmRlL2VtYWlsbG9l c2NoZW4uaHRtIiB0YXJnZXQ9Il9ibGFuayI+aGllcjwvYT48L2ZvbnQ+PC9i PiANCiAgICAgIGF1cyB1bnNlcmVyIE1haWxpbmdsaXN0ZSBhdXMuIDwvZm9u dD48L3RkPg0KICA8L3RyPg0KPC90YWJsZT4NCjxicj4NCjxwPiZuYnNwOzwv cD4NCjwvYm9keT4NCjwvaHRtbD4NCg== --= Multipart Boundary 0506021615 Content-Type: application/octet-stream; name="tassegross.jpg" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="tassegross.jpg" /9j/4AAQSkZJRgABAgAAZABkAAD/7AARRHVja3kAAQAEAAAAHQAA/+4ADkFk b2JlAGTAAAAAAf/bAIQAEAsLCwwLEAwMEBgPDQ8YHBUQEBUcIBcXFxcXIB8Y GxoaGxgfHyQmKSYkHzExNTUxMUFBQUFBQUFBQUFBQUFBQQERDw8SFBIWExMW FREUERUaFRcXFRomGhodGhomMiMfHx8fIzIsLykpKS8sNjYyMjY2QUFBQUFB QUFBQUFBQUFB/8AAEQgASABhAwEiAAIRAQMRAf/EAIUAAAEFAQEAAAAAAAAA AAAAAAABAwQFBgIHAQADAQEAAAAAAAAAAAAAAAAAAgMBBBAAAgEDAgMFBgQF BQAAAAAAAQIAEQMEITFBEgVRYSIyE3GBoUJSBpGxIxTB0XKCQ2KiwjMkEQAC AgIDAQADAQAAAAAAAAAAARECIQMxQRJRYXEiBP/aAAwDAQACEQMRAD8A38Qk CIWrWmgG5jILk81PDwEW10jUh+pMTWcq4I01Mrup9VXGRhzBAPM5/hEdvyCT ZNv5WPYFbrhe7j8JDfruGpoAze7+cxmd9wO7/wDnStfnfUn3Subqee51ucvc FB/KYm3nhfR3SOefiyz0NOvYTmnOyf1LUSZazEuDmQi4vahqfes8tXqWZWhY N3ECTcPrF21cB5jacbEHSbNl2Z4ng9MS4jiqms6lD0vrFvMpbyP08j5bg+aX KXGBCXN+DDYx62TFagehEixjAhCEAOKClOEatMVY2m3HlPaIXL4UVMZ/e4t0 +mG8Q4jgZFuWbA7ksli096tKAzzvqnU3zchip/SUnkG+nEn2zXfc1y6nQ71G 1dltq2xo55ZgvSRrlwMSERiFXuBpE2Osf1KXxF9FLWf8xP19Hdkq7sFHjaor 9CHc+0yWgsWRRVAkE3bdoUTSNNkMZz3rbZxKqju1qmquWnZ8ssLuImV/1ij1 3Ek3+jKqohdakAu9I/hCzZ6at8mrPqQDRqVpQQa6bipy8wUV0FK0417aSKd1 iXCeCex1l4mOWRcV3w7q2y/MhPgccJuem5X7rGAuauujfzmKdLTtQqDoSCDS jU75o/ty6WQV4ih9onVo2Nvyzl31UekX9tiDyNr9J7Y5GSOYU2O4PYY5bfmW p32I751p9HOdwiQjAQyguBwZSZlsYOSt1NUJrTul+yHkenGkrb9u1cNL2qDe c5RdnGep6t0nIt2R4mStkf67fiH40nn2XUXiw0W741H9W/4HSelYarbthbY5 VU1Udx2mc+5OgE8+XjL+kxLMB/jc+b+xvgZmG1PRSlnXjHpQZGEV1ZGKOOVh uDEl0lGBLbLTksMHKpY9At4laqJwoe+Si6BiyVXhQ8KylBKsCNCNpIsnIyXF u2oLn5vpH1HspOfb/nUuyfldyUptbUNSy4tXS14DzA18VKaU1oRND9sWyUe4 NVLkqd6yitY62qYthzdyrtFLKK0Bm06XgrhYiWV+Ua+2R0V9XbXFQ3uKpfSS QREQ8t2nBxX3iOUjT6FT9LD46Tt4ZzD0IawjAN8CJX305SSJPaokTI1rIMdF dh5o9Qo+lDyn2iWJbjMr1C62Jl8/+N/N3d8sMPrChQt01HBpjXZSnxh1L7cw 8urWaWXPynyf2kar+Uz2T9sZ1hqi27rwKKLg/wBpr8JsFybVwVVhEL8QaRVZ rhtDuq/f7MQnSbwbXGyLzDZPTKLXvO8s8Ho/W2Y0QYVvbxAIKezVjNBcvvsH P4zrGUu/MTWDr6zZtiPZGEkhzpPSMXp6+oD6l7Y3T/xEuE8srlvi5d5LfkTc 8CZYJ5BK60qqFgjazs5Z2No2+xjkafVlXtP5Sj6MHYRPfCaA2xrqNpFvCEJB jopOpWEuqQ4rKQ4tyyf0jVfpMIQQ6HLVy4pG6ydbu3D80IQwD9Dy3Aoq7Rf3 bsPTs1VTuYQmqCZZ4CUAUa9ss/UHMEGp/KEIy5FHSaCcJ4nL8BoIQj95AchC E3AH/9k= --= Multipart Boundary 0506021615 Content-Type: application/octet-stream; name="foto2.jpg" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="foto2.jpg" /9j/4AAQSkZJRgABAgAAZABkAAD/7AARRHVja3kAAQAEAAAASAAA/+4ADkFk b2JlAGTAAAAAAf/bAIQABAMDAwMDBAMDBAUDAwMFBgUEBAUGBwYGBgYGBwkH CAgICAcJCQsLDAsLCQwMDAwMDBAQEBAQEhISEhISEhISEgEEBAQHBwcOCQkO FA4NDhQUEhISEhQSEhISEhISEhISEhISEhISEhISEhISEhISEhISEhISEhIS EhISEhISEhIS/8AAEQgAUQByAwERAAIRAQMRAf/EAJwAAAICAwEBAAAAAAAA AAAAAAAFBAYCAwcIAQEBAQEBAQEBAAAAAAAAAAAAAAIDAQQFBhAAAQMCAgYE CQgGCwAAAAAAAgADBAEFEgYRIjJSEwchQoIUMUFRYnIjM9MVYXGBocKDkwjR kkOjs8ORsfJTY3PjNFSkFxEBAQABAwQBBQEBAAAAAAAAAAIDARITESIEBTFB UTJCFFIV/9oADAMBAAIRAxEAPwD38gEAgxMwbpiOuGi5VaaCtXTPtgthE3V7 vLoeEGulea/KnRW1VZnN1sSwxYej/MJeevMpfGg/+tzSr7FkPpqp/rpXEmR+ aMsttlk/pqn9lHEeQ+YsR3/cMVb9GulaT5v3Txn0PM9pm1wtvUbPdc1K/Wt4 8mdUbTcTEtmuleia01SyXQIBAIBAIBBy3mrmGZbnI9vbKrMV5o3DPe0dC+X5 mfa3w49zz7euY1ohmTTDjlykbjGx+uvkV5c/Gj7GD1uSvlU3uYVzePE1BbBr znNdeb+m3un1sS2N8wJg4cUET++P3azryba/8+ExnmM+OHFb3OzK962o57/0 ivWwZM82H4+1BIw3MX8z/TVz5dyzr1cV+y1WHmtY7g4LD5lapB7AP7BdtevH 5s/V4c/q8k/j3O0ZFzW7JmDa3HOM08GNktvCvr+Ln610fLy4ujpdK6aUr5aL 62jzPqAQCAQCATUVnOOTrNnizPWW9gfd3th1ksDzR74GvFnxRlnpTbDnrFXW XmvMn5as0Wd0ncuus5hhdQPYyR7Dup+8Xwc/q7n8O5+gwe3ivz7XMb1lm+Zd qQ3m0XKBg65Q38H4ns14qwXPzL6E+Tjr8aV34pZx1SKT+G37xRx003Ng3iy4 tqT2m2/eJx0ruToZMXQxYtguzJB9QWXDNd4KpnWTau1p5J56vxCRWwrPCPbl 3Iu7AHYd1/3a2xevy3+ryZPaYo/Z3zIeXbby3tXc2555kvWHCcshwMsBuB5i +343iThl+d8vy+auujo8bM9tC3MvynhjaBECq50YjpTRWg+XpX0tM2nR5EqL f7bMLCzIHH4hOlQrX5tK7yhmBiY0IemlVsMkAgEGBOBTorXpU18DDEvG6x9B AvmSH26argqd1Cp3B5h4y7zboEw99+K2azVyakrjlvZ1mLLaGT3xt7Hu1TnJ f+kdzMl3ZHhRnW4DO5GbbZ/hqmdVWpeU6ZKPFJfckn5xIzNI44iEd8UUfcvc v8Gr11u7Zd9o5UYYP6PVhTrBp8q3wSqV7nQWJ8Y2HaUpippA6U1gLxFT5aLf WdNVE+Vpz8oH2n9pijf10r+hY4NeugsK9A+EVBpUq+CiCC7LIiwjsrCsidzR iXEpAvYhWLTc0k9hUqK5z2IUSrsxzW2lIRSiw9ZEkjzmsiGLLmuKp1ZLaPEf jiO2alx0BssIiIktFsJN1NtlxsD1ahWjzx7DWnoV89KbMqxeHFfmFTCc5zTQ N1sNNAp/QtcE9JD9bCDcHC0C2HhLpqsctJpB2RXnS0uPYRWspa4tyYJ/uxFg M9hTSppMeHVWTQplNkjhDMZLWQIZjJEpZlpQyI1TiVFtuHWJBIi5gg225EwQ vSZYDqA2P20UsTN0mTNoSZD+5b2/xE3BgLYkI95w8INcI47Hb30c3pTN4GHc Y50LQxcD4To+RxenDX0arfpp9WlbiHOax1AqbXgH51hmlzVAcWCCqcRCBYUS 51mK4SY/rWCIHQ1wMV1KwZN5iRb4x3OdhZucXUeDe89cXvW4nmHh1SQqi+Uy 2XjRO4nkRWsW0pdReGwO0grWZM4QbOIxmteQfUHqAqCS136K4/xcAhjLHjLb U7RcI+ZIzYe0HsoN0e8Trs7wLe2R+eimy9CUGbZ7QLvGucp/vDwbgNf21vgl Uup8N7/r6O15F6VN0yPWVHNoS4blels90qeCqmp66CrUv7MaT8Ovo/D5dNl3 9i6vNU1onanSIYyGsTeEwPriqnuZVKl3zLZSBLCKzqXHMb1lO4RXRmW83Ic2 KWJl0ft74KKd3Jlvzxd4IixdYjgGG28x64C/mIbTYeYluKnrX8B7jmohtRZH MC2YdV8Xj3G9f+EhsojuGar9cBJixwXAM9TvcseCyP3ftDQ2odvybMkCJTnX J8szxvSHOsaoqlwtvLkSEcXEBdcWy28ubYz61/EeDeJcXDK7Zwy9ldooNlBu fc9gGWNgT/xFczuXtbMh5auVwuJ5pzBiKU/XE3QvFXyUXpmdqnUlQEC272SB eo9WJrdDpXwFo6aIKBNypmzLZE/lmebkf/jua4LKsf2CwuZV8tvqsw2HjYNt 1hZ7alO1kPMzIE7UnC/bT3HG1NUbR8Q5b3D2V3jB6Qqd0o4qaSteR3Nm8wP1 lztOOh8LyUzrFereH3idqeKmsrly3t+s/foR4N0sadquOmsuZXLmDqwzfuru 4wyi+JFe5uSXvVWGwEG47LL7DS1maNqOMfmJnQsMt9yNEc/YsDwQWvBP1Uv+ VOV9ts+GTOp3mT5CWg6CAA2FAClBAaaKUogyQCAQCCJKtkCYOGTHbdp8tP0I KzcuWeWLjpxRxbrX5KVXOgqdw5CZclYuFQW9Pgw6n9WlRxaCvSPy22w/ZyXQ 9Ek4tHdyFT8skOtdea+Xab92nFo5uo5g/l1scWuktf0yxrvHKty1W/k7l6Jo xUpop1RorStMDJtgt+irUUalTx1QPGmWmRwtBRsfJSmhBmgEAgEAgEAgEAgE AgEAgEAgEAgEH//Z --= Multipart Boundary 0506021615 Content-Type: application/octet-stream; name="automat.jpg" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="automat.jpg" /9j/4AAQSkZJRgABAgAAZABkAAD/7AARRHVja3kAAQAEAAAAIwAA/+4ADkFk b2JlAGTAAAAAAf/bAIQADgoKCgsKDgsLDhQNCw0UGBIODhIYGxYWFxYWGxoU FxcXFxQaGh8gIyAfGikpLS0pKT07Ozs9QEBAQEBAQEBAQAEPDQ0PEQ8SEBAS FA4RDhQXEhQUEhchFxcZFxchKh4aGhoaHiomKSMjIykmLy8qKi8vOjo4OjpA QEBAQEBAQEBA/8AAEQgAwgBkAwEiAAIRAQMRAf/EAJgAAAEFAQEBAAAAAAAA AAAAAAADBAUGBwIBCAEBAQEBAQAAAAAAAAAAAAAAAAECAwQQAAEDAgMCCQgG CAYDAAAAAAEAAgMRBCESBTEGQVFxsSITcxQ1YYGRMnKy0jShwUJSM0PRYiNT g3QVFoKSosIkB/DhkxEBAQACAQMEAgMAAAAAAAAAAAERAjEhEgNBUZETYVKB IjL/2gAMAwEAAhEDEQA/ANJVPP8A2Po4kdH3a5qxxaTSOmBp+8VwWBz16+4I ND1hxHtOQapHv3pkgqLeccoZ8aV/vTTv3E/oZ8az/TdLurm0Zcm7MbZK5WAV PRNMaUonf9FmO28f/q+JMxMrp/eum/uZ/Q340f3tpv7mb0N+JUgaG6Rzm96d VvG4ivpeFBXzTa3MluayZKdISHGorwFydDq1F2/Wlt2wT+hnxrgb/aUTQQXH oZ8ayN9zj6pH+Ny8bdZT6p/zuV6HVsbN9dOfsgn9DPjS7d6rJ2yGb0N+JZho wdeNe7M6Pq3sZTM5wOfZ9pqu+m7rR3lo2fvcja1BAaaYfxE6HVLS73WEQq6G Y8gb8SktK1OHVLQXcDXMYXFtH0Bq3kJWfa1Yf03UBatldKBiXOJFQ6NzqZS4 7CrfuZ4K3tZOdLgzcp9CEKKFhAi66+khrl6yfLXiq5wW7rDbbxU/zI98olSV pFLaRFr7uSCPOQxraAOAwzCp405Li+KR8N9K98bS4gu4Bx0KbytkktainQnl biaYGjuIpW3AFvP950by7h4OBDDmGMSsa6S9dGXirjmwB4jwqH1AmK4pC9t4 0k1eGPDhQ06ReOZTVpm6plLQTdE4GnS/W+8oPVfmelF3F1T0QJRmx29M0w8i pEjHpmkSaLcXst41moRupFa0YMwFKDKemc1TiMAoljGZgMoxI4ArLa95/tS+ DdNZJCXkuvCWhzaZekGu6ZyeQ0xVbZtVguMWjaCw0Zdt8z4v0L2ZxtZOps7l 7oKAgtkwqdvqUCbHSJ7e0sJpLYs7wCTJmBz16batqcvRSty2NszzEzqoXGsc dcxa3iqp+GTS8ke+WNz3Oe7MRmc7Mfw3faV43M8Fb2r+dUS49aL2z7j1e9zP BW9rJzpVnKfQhCjQWG23ip/mB75W5LDbbxU/zA98olTNwC2B7GCp64uoMTjg k7Z2aOUcBik+hpKXvZI3xsMMbm5MzJjStZQ5zq+dpCZWDJ2C4MmLXslc0H7I yO/8opvr/bM9+F9Di27v3dhffGF4+wAOjyYVUTfRW7y9/eTcTNJLGOikIPkz l1BU+SimrHvBtmhlmycU2k48uCg9QZJ1crpLEW7A4ZpxG8FpcQW0c5/2uRVI lbV9kN271j9SkhuC6rLEEBj/AFaAspmdn4SDwYqDj2hWOwOof2pqDIrOGS1L iXzucA+gawucGUJdkFCDUbVXIfWxWoLJp971rYY765uHQwNpFG0D9nUYhpc9 2HmTu5NsXg2z5HsLekZaZgfNgubfR76CCxkfBC8X9GQZiSczyHsL8RTo/Qlt QtJbO7kglaxj20OWKuShGGWuKdERlxti9s+49XvczwUdq/nCodz+V7Z9x6ve 5fgje1fzhKTlYEIQstBYZb+Kn+YHvrc1g75HRXk0rMHslLm8ocShVk1Bw6vG gPWOpQ7RThHGkICeqlHB1UnuOT3d6TUtQikl62EEH8yMOP0OaAnd1YalLG+M yQgO6Li1gaeIjGRLzlFejt9VdCHQNk6k+rTZt4POo2a2nzOMlvKSekXGN5HH WtKKdmtdSs2iMXZYweq1tCB/lcoUxajIZWMccraFwM+QEPGYdFzgNnArkha2 s9al0q6ntes/pjDW5a14DXFoDiclelQUJoEwiJBqNqdQP1plrLZQv6u1lc4T RddGAS2jXbTXlptTCSSS2kMcjBnbicrw4Y+VlQmRa9Fnt5BAzVZrjq4QcjIz VrOEdX0iR6FJai6xfOH2T5pGubWR85JcXcpx2KH0S2N1IGyua1rXZT1TmyP2 AgtbhUYq0/0O0jEmaS5d1T2xnLE3Eu4RtTMTqrFz+X7Z9x6vW5fgje1fzhUz VbdttcmFpLmskcATgT0ZArnuV4I3tZOcK0nKwIQhZaCwWUVurhuysjsf8RW9 LBZPnJu0d7xQSen96gaRBcviDvWDaivoKdOkvT611IfT8Sb2nqhOCqwa1llG bvMlMeDi86ZyWNsSS5xLjiTlbt9Kcwn9lj953OkpCrhcmhsrUHa4/wCFqUis rao2+hv6EEpaFMLeD/T2COZwt3mN8VBnaMpqR+rRTbRdPb0rqQ+c/W4qC00n vt2OJzPpYrDH6isZRl1BlOZ0jn5SSAabaEY4eVXTcrwRvayc4VQvTWqt+5Xg g7WTnClWcrChCFloLBpPnJu0d7xW8rBZPnJu0d7xRKlbT1U4cU3tfVS7lWTG I/sj7TklIUpF+GfackZCqsJE4paA4psTil4DikWpHTR/zLryuj9xWFnqKvWH zc/lye6rBGasVjJhecKuO5Xgg7WTnCp17QVVx3J8EHayc4U2WcrChCFloLBZ PnJu0d7xW9LBZPm5u0dzlEqUtTgnDtia2mxOH7FayYR/hn23JGUpWP8ADPtu SEpVWEScUvb7U34U4g2pFqTsfm5uRnuqeiPQUBYn/lzckfuqdjPRVjJjfO2q 57keBt7WTnCpd5wq6bj+BN7WTnClWcrEhCFloLBJPm5u0d7xW9rBZPm5u0d7 xQqRtTQJw44JvbbEu84KuZgw/s3e25ISFKsqGur976aCqReq3CXCl4dqQO1L QnEJCpSy+bl8oZzKbjPRUFZhwuXk8IB5QfV9Cmoz0cVWTW82FXTcfwIdtJzh Ui9mjDTV4HKQrtuNX+hCu3rpOdSrOVjQhCy0FgV7UCdwNCJziPKSt9WBX5o2 ccc55ygRmmlYyAxyOaTGC6hOJqUn368H5zvOapNz84aPujKFwhgoby5GHWH6 F4Lm5eaAlx8gB+pIu2rUtKt7eCxtpNMit2mSNrg+VhJdmGOZzQTtVnVnbbtx 05ZoXXm0tePLl/8AS47zOPtkLVm2e8Erjnu7IRHa1sT3GnEK0UHvTu1by92k juLa1kcSx8sp6oSONMrQGgjzphmeTr1nwpztRmfbRRAZJIy7NO1zg94Oxrsd jeBIGaZ3rSPdyuJ+tFzazWdzLa3Dcs0Lix4rXEeVchR0egft2+01bVuT4Ke3 l51i5+Zb7TfqWz7j+CHt5edX0FjQhCgFgGpbZO2ct/WA6ltl8kzvrQMG8a8X WWgafvCv0p6zTJHtDhICDxCqlsnLWnj23uNZnCPyPd6rSeRXvdC+kmsO6SVE tocAdpidsPmOCq3dpbZpY1pe5+OamwbNg2qQ0e7h0+4NyHPEpaWO61ji1wPB Ruxa1s5yx5fHtM63W5jRo+sc3i8gVT3m1Pd2SW3fPK69msi7LZRfhOeT+bJw YjEBOHb2sMRbE+KIkUz0eXDgqA4UVPfBZQukIm66riQQ12I5KJ8OWmlz1m3w ZXl5LfXUt1NTrpnl76Cgx4AOIJEKSZaRXZOUlgZ5Mu3l2pC8tI7UhucmQ0OU 02HGuCz3TOHp+rfs78Y1NWn9s0+ULatx/BD28vOsVqOtafKFte5Hgh7eXnWv RhYkIQoBYDqX53bHnK35fP8AqD8z5gMQJTX0lAzc6rWjiFF62edjcjJHNZ90 EgLyNnWODK5SdleEpY2MnGFLj1a1m3Ouf4IGWU7XuPnK5qeMpx3N/C5ddxP3 kzDt3vua1PGvKlP2acHEAuI5EpLpcbBUPcTyBO6NfVv7IypRVPDYHgf9C4ls zEwvc7AbMNpTMZum3sbg9IHyhbbuR4J/Gk51iQBqFtW4crJdAD2GreukFfOF WVlQhCAWC3NtE+6mqD+I7YfKVvSzm9/671MSyS2tzDM1znODX5o3UOP6w+lB Sm6bC7Y97fQf0J02ItaAXhxH2i3Hz0cpt+5+8UJA7mZMK1Y+M/7gmz9C1pta 2FxhtpG4j6AlkvJrvvr/AJuEU5jhskYOVhP+9cEyD85g/hH4k+k07UW+taTj ljf8KRdpmpbe5z0PD1T6enKnbr7Nfb5P2psJJmnCdv8A8v0lddbO/bOD/Cb8 SVGl6i40FpOT2T/hTiHQ9ZeehYXDv4T/ANCduvtF+3yftt8kYYHP9aX0RgfW nB0q1mIMzpJMuwAtYP8AS1SNpu5rrsRYygD7wDPfLVKQbq628AugEdcOm9uH LlJVxrOJGL5PJel2titO06wi9S3FeNxLveK0XchoboTQAGjrZMAKDaFGR7j3 cn49zHHtqGNL+TbkVm0jS49KsxaRyOlaHF2ZwANXciWsyXJ+hCFGghCEAhCE AhCEAhCEAhCEAhCEAhCEH//Z --= Multipart Boundary 0506021615-- From sdm7g@Virginia.EDU Wed May 8 20:32:11 2002 From: sdm7g@Virginia.EDU (Steven Majewski) Date: Wed, 8 May 2002 15:32:11 -0400 (EDT) Subject: [Pythonmac-SIG] Re: [Python-Dev] MacOSX dlopen equivalent? In-Reply-To: Message-ID: On Wed, 8 May 2002, Jack Jansen wrote: > Another but: if I look at the readme for your test code I get the > impression that the gcc that OSX has (2.92.2) may be a problem. gcc 3 is > going to be supported in the next major release (late summer, according > to apple). gcc 3 is in the latest online (beta) developer tools, but it's 'experimental' -- ProjectBuilder defaults to using the earlier version which is also included. -- Steve From csmith@blakeschool.org Wed May 8 22:17:03 2002 From: csmith@blakeschool.org (Christopher Smith) Date: Wed, 08 May 2002 16:17:03 -0500 Subject: [Pythonmac-SIG] raw_input() and input() with \n Message-ID: I just learned a tip from one of my students. If you want a \n to be included in a prompt provided to the raw_input or input functions you may have been disappointed to find that it gets ignored and you end up with no prompt in the dialog box at all. Well...change those \n's to \r and now it works! Multiple lines will show up in the dialog window. Here are two little replacement functions which also handle a cancel from the user instead of raising the exception window: # # A workaround for the fact that \n causes the prompt to be lost b/c # the buffer gets flushed before it gets to the SimpleDialog box. # Thanks to Ryan Scheurer for this tip: replace \n wth \r def iget(msg=''): #replacement for input try: return raw_input(msg.replace('\n','\r')) except EOFError: #user hit CANCEL return None except SyntaxError: #user hit OK with nothing entered return None def rget(msg=''): #replacement for raw_input try: return raw_input(msg.replace('\n','\r')) except EOFError: #user hit CANCEL return None My 2.0/100, /c From jacques.piotrowski@laposte.net Thu May 9 18:53:36 2002 From: jacques.piotrowski@laposte.net (=?iso-8859-1?Q?jacques.piotrowski?=) Date: Thu, 9 May 2002 19:53:36 +0200 Subject: [Pythonmac-SIG] =?iso-8859-1?Q?How_to_use_NNTP_lib_=3F?= Message-ID: Hello from France. I would like to know what to put in the 'article' document bellow, for a script like this one : s =3D NNTP('news.foo.com') f =3D open('article') s.post(f) s.quit() What header, in wich order, and so on... Thanks you a lot for your help. Acc=E9dez au courrier =E9lectronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,13 =80/mn) ; t=E9l : 08 92 68 13 50 (0,34=80/mn)" From dan@grassi.org Thu May 9 21:21:37 2002 From: dan@grassi.org (Dan Grassi) Date: Thu, 9 May 2002 16:21:37 -0400 Subject: [Pythonmac-SIG] PIL w/o tk on Macho In-Reply-To: <1871070991062.20020501184404@hekkelman.com> Message-ID: <5D69A3B4-638A-11D6-BD88-00039346A28A@grassi.org> I am trying to build PIL on macho but getting the following error: cc -Wl,-F. -Wl,-flat_namespace,-U,_environ -bundle -framework ./_imaging.o ./decode.o ./encode.o ./map.o ./display.o ./outline.o ./path.o libImaging/libImaging.a -L/usr/local/lib -ljpeg -L/usr/local/lib -lz -o ./_imaging.so /usr/bin/ld: can't locate framework for: -framework ./_imaging.o make: *** [_imaging.so] Error 1 I have the macho "pygames) framework of python installed: Python 2.2 (#11, Jan 6 2002, 01:00:42) [GCC 2.95.2 19991024 (release)] on darwin Any idea of what I need to do of if this combination will work? Or in general how to get PIL running under macho? Thanks, Dan From bob@redivi.com Thu May 9 22:00:06 2002 From: bob@redivi.com (Bob Ippolito) Date: Thu, 9 May 2002 17:00:06 -0400 Subject: [Pythonmac-SIG] PIL w/o tk on Macho In-Reply-To: <5D69A3B4-638A-11D6-BD88-00039346A28A@grassi.org> Message-ID: --Apple-Mail-1--278866199 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed These are my notes.. you'll have to change the paths. Note that this builds with Tk, it's pretty simple to figure out how to tell it *not* to build _imagingtk.so if you look at the build scripts/makefile. It shouldn't even try to build tk if you don't have it installed. Note that I'm 90% sure that PIL and PIL's Tk stuff are entirely separate, so if you have PIL *with* Tk, you will gain nothing from compiling one without Tk. cd libImaging ./configure && make python setup.py build cc -Wl,-F. -Wl,-flat_namespace,-U,_environ -bundle -framework Python "build/temp.darwin-5.4-Power Macintosh-2.3/_imagingtk.o" "build/temp.darwin-5.4-Power Macintosh-2.3/tkImaging.o" -LlibImaging -lImaging -o "build/lib.darwin-5.4-Power Macintosh-2.3/_imagingtk.so" -undefined suppress sudo python setup.py install --Apple-Mail-1--278866199 Content-Disposition: attachment; filename=setup.py Content-Transfer-Encoding: 7bit Content-Type: application/octet-stream; x-unix-mode=0444; name="setup.py" #!/usr/bin/env python # # Setup script for PIL # $Id: //modules/pil/setup.py#7 $ # # Usage: python setup.py install # # before running this script, build the libImaging directory # and all support libraries (the JPEG library, ZLIB, etc). # from distutils.core import setup, Extension import os, sys, re # -------------------------------------------------------------------- # configuration NAME = "PIL" DESCRIPTION = "Python Imaging Library" AUTHOR = "Secret Labs AB / PythonWare", "info@pythonware.com" HOMEPAGE = "http://www.pythonware.com/products/pil" # on windows, the build script expects to find both library files and # include files in the directories below. tweak as necessary. JPEGDIR = "../../kits/jpeg-6b" ZLIBDIR = "../../kits/zlib-1.1.3" # on windows, the following is used to control how and where to search # for Tcl/Tk files. None enables automatic searching; to override, set # this to a directory name TCLROOT = None from PIL.Image import VERSION PY_VERSION = sys.version[0] + sys.version[2] # -------------------------------------------------------------------- # configure imaging module MODULES = [] INCLUDE_DIRS = ["libImaging"] LIBRARY_DIRS = ["libImaging"] LIBRARIES = ["Imaging"] HAVE_LIBJPEG = 0 HAVE_LIBTIFF = 0 HAVE_LIBZ = 0 # parse ImConfig.h to figure out what external libraries we're using for line in open(os.path.join("libImaging", "ImConfig.h")).readlines(): m = re.match("#define\s+HAVE_LIB([A-Z]+)", line) if m: lib = m.group(1) if lib == "JPEG": HAVE_LIBJPEG = 1 if sys.platform == "win32": LIBRARIES.append("jpeg") INCLUDE_DIRS.append(JPEGDIR) LIBRARY_DIRS.append(JPEGDIR) else: LIBRARIES.append("jpeg") elif lib == "TIFF": HAVE_LIBTIFF = 1 LIBRARIES.append("tiff") elif lib == "Z": HAVE_LIBZ = 1 if sys.platform == "win32": LIBRARIES.append("zlib") INCLUDE_DIRS.append(ZLIBDIR) LIBRARY_DIRS.append(ZLIBDIR) else: LIBRARIES.append("z") if sys.platform == "win32": # standard windows libraries LIBRARIES.extend(["kernel32", "user32", "gdi32"]) MODULES.append( Extension( "_imaging", ["_imaging.c", "decode.c", "encode.c", "map.c", "display.c", "outline.c", "path.c"], include_dirs=INCLUDE_DIRS, library_dirs=LIBRARY_DIRS, libraries=LIBRARIES ) ) # security check if HAVE_LIBZ: # look for old, unsafe version of zlib # note: this only finds zlib.h if ZLIBDIR is properly set zlibfile = os.path.join(ZLIBDIR, "zlib.h") if os.path.isfile(zlibfile): for line in open(zlibfile).readlines(): m = re.match('#define\s+ZLIB_VERSION\s+"([^"]*)"', line) if m: if m.group(1) < "1.1.4": print print "*** Warning: zlib", m.group(1), print "may contain a security vulnerability." print "*** Consider upgrading to zlib 1.1.4 or newer." print "*** See:", print "http://www.gzip.org/zlib/advisory-2002-03-11.txt" print break # -------------------------------------------------------------------- # configure imagingtk module try: import _tkinter TCL_VERSION = _tkinter.TCL_VERSION[:3] except (ImportError, AttributeError): pass else: INCLUDE_DIRS = ["libImaging"] LIBRARY_DIRS = ["libImaging"] LIBRARIES = ["Imaging"] if sys.platform == "win32": # locate tcl/tk on windows if TCLROOT: path = [TCLROOT] else: path = [ os.path.join("/py" + PY_VERSION, "Tcl"), os.path.join(os.environ.get("ProgramFiles", ""), "Tcl"), # FIXME: add more directories here? ] for root in path: TCLROOT = os.path.abspath(root) if os.path.isfile(os.path.join(TCLROOT, "include", "tk.h")): break else: print "*** cannot find Tcl/Tk headers and library files" print " change the TCLROOT variable in the setup.py file" sys.exit(1) # print "using Tcl/Tk libraries at", TCLROOT # print "using Tcl/Tk version", TCL_VERSION version = TCL_VERSION[0] + TCL_VERSION[2] INCLUDE_DIRS.append(os.path.join(TCLROOT, "include")) LIBRARY_DIRS.append(os.path.join(TCLROOT, "lib")) LIBRARIES.extend(["tk" + version, "tcl" + version]) else: # assume the libraries are installed in the default location LIBRARIES.extend(["tk" + TCL_VERSION, "tcl" + TCL_VERSION]) MODULES.append( Extension( "_imagingtk", ["_imagingtk.c", "Tk/tkImaging.c"], include_dirs=INCLUDE_DIRS+[ '/Library/Frameworks/Tk.framework/Headers','/Library/Frameworks/Tk.framework/PrivateHeaders', '/Library/Frameworks/Tcl.framework/Headers','/Library/Frameworks/Tcl.framework/PrivateHeaders'], library_dirs=LIBRARY_DIRS, libraries=LIBRARIES[:-2] ) ) # build! setup( name=NAME, version=VERSION, author=AUTHOR[0], author_email=AUTHOR[1], description=DESCRIPTION, url=HOMEPAGE, packages=[""], extra_path = "PIL", package_dir={"": "PIL"}, ext_modules = MODULES, ) --Apple-Mail-1--278866199 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Use this setup.py -bob On Thursday, May 9, 2002, at 04:21 PM, Dan Grassi wrote: > I am trying to build PIL on macho but getting the following error: > > cc -Wl,-F. -Wl,-flat_namespace,-U,_environ -bundle -framework > ./_imaging.o ./decode.o ./encode.o ./map.o ./display.o ./outline.o > ./path.o libImaging/libImaging.a -L/usr/local/lib -ljpeg > -L/usr/local/lib -lz -o ./_imaging.so > /usr/bin/ld: can't locate framework for: -framework ./_imaging.o > make: *** [_imaging.so] Error 1 > > I have the macho "pygames) framework of python installed: > Python 2.2 (#11, Jan 6 2002, 01:00:42) > [GCC 2.95.2 19991024 (release)] on darwin > > Any idea of what I need to do of if this combination will work? > > Or in general how to get PIL running under macho? --Apple-Mail-1--278866199-- From bs1535@sbc.com Fri May 10 20:57:05 2002 From: bs1535@sbc.com (SNYDER, BARRON F (AIT)) Date: Fri, 10 May 2002 15:57:05 -0400 Subject: [Pythonmac-SIG] New Python IDE for OS X Message-ID: <35BD410BA148D411A7ED00508BCFFBDA0C16C8CE@msgil65170u05.nbk2305.il.ameritech.com> For those of you looking for a Python IDE that runs under OS X, Archaeopteryx just released a beta of their Wing IDE for OS X. Take a look at http://archaeopteryx.com/psupport/prerelease/osx/osx-beta.html for more info. I downloaded it and it looks pretty good. -Barron From bob@redivi.com Fri May 10 21:38:35 2002 From: bob@redivi.com (Bob Ippolito) Date: Fri, 10 May 2002 16:38:35 -0400 Subject: [Pythonmac-SIG] New Python IDE for OS X In-Reply-To: <35BD410BA148D411A7ED00508BCFFBDA0C16C8CE@msgil65170u05.nbk2305.il.ameritech.com> Message-ID: Any Python IDE that works under X11, so long as it's endian safe, is going to work perfectly fine under OS X if you make XDarwin a requirement. What's the point? It's not going to look or feel quite like an OS X application, it shouldn't really be called an OS X application with a disclaimer that it requires an X11 subsystem to make it tick. On Friday, May 10, 2002, at 03:57 PM, SNYDER, BARRON F (AIT) wrote: > > For those of you looking for a Python IDE that runs under OS X, > Archaeopteryx just released a beta of their Wing IDE for OS X. Take a > look > at http://archaeopteryx.com/psupport/prerelease/osx/osx-beta.html for > more > info. I downloaded it and it looks pretty good. From Jack.Jansen@oratrix.com Fri May 10 22:18:50 2002 From: Jack.Jansen@oratrix.com (Jack Jansen) Date: Fri, 10 May 2002 23:18:50 +0200 Subject: [Pythonmac-SIG] PIL w/o tk on Macho In-Reply-To: <5D69A3B4-638A-11D6-BD88-00039346A28A@grassi.org> Message-ID: <85E7D6DD-645B-11D6-B6A7-003065517236@oratrix.com> On donderdag, mei 9, 2002, at 10:21 , Dan Grassi wrote: > I am trying to build PIL on macho but getting the following error: > > cc -Wl,-F. -Wl,-flat_namespace,-U,_environ -bundle -framework > ./_imaging.o ./decode.o ./encode.o ./map.o ./display.o > ./outline.o ./path.o libImaging/libImaging.a -L/usr/local/lib > -ljpeg -L/usr/local/lib -lz -o ./_imaging.so > /usr/bin/ld: can't locate framework for: -framework ./_imaging.o > make: *** [_imaging.so] Error 1 > For some reason there's a "Python" missing after your "-framework" option. Distutils picks that string of funny linker options up from the LDSHARED flag in the Makefile that's installed in your lib/pythonX.Y/config (installed there by the Python "make install"). The value after the -framework comes from PYTHONFRAMEWORK, which in the end comes from what you passed to the --enable-framework during the Python configure. Something along this path went wrong. Maybe you did "./configure --enable-framework=" or something similar? -- - Jack Jansen http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman - From bs1535@sbc.com Fri May 10 22:52:54 2002 From: bs1535@sbc.com (SNYDER, BARRON F (AIT)) Date: Fri, 10 May 2002 17:52:54 -0400 Subject: [Pythonmac-SIG] New Python IDE for OS X Message-ID: <35BD410BA148D411A7ED00508BCFFBDA0C16C8D3@msgil65170u05.nbk2305.il.ameritech.com> You may be correct in the strict sense of "OS X application" but this is the first vendor I've seen that says they will support OS X. With the others, it's "if you can get it to work on OS X, great, but we won't support it". -Barron -----Original Message----- From: Bob Ippolito Sent: Friday, May 10, 2002 3:39 PM To: SNYDER, BARRON F (AIT) Cc: pythonmac-sig@python.org Subject: Re: [Pythonmac-SIG] New Python IDE for OS X Any Python IDE that works under X11, so long as it's endian safe, is going to work perfectly fine under OS X if you make XDarwin a requirement. What's the point? It's not going to look or feel quite like an OS X application, it shouldn't really be called an OS X application with a disclaimer that it requires an X11 subsystem to make it tick. On Friday, May 10, 2002, at 03:57 PM, SNYDER, BARRON F (AIT) wrote: > > For those of you looking for a Python IDE that runs under OS X, > Archaeopteryx just released a beta of their Wing IDE for OS X. Take a > look > at http://archaeopteryx.com/psupport/prerelease/osx/osx-beta.html for > more > info. I downloaded it and it looks pretty good. From miken@inetworld.net Fri May 10 23:20:01 2002 From: miken@inetworld.net (Mike Nardell) Date: Fri, 10 May 2002 15:20:01 -0700 Subject: [Pythonmac-SIG] Method to lock/unlock files In-Reply-To: <052866E7-58F3-11D6-9F83-0030655234CE@cwi.nl> Message-ID: Hi --> Last month I was having trouble locking or unlocking files from within a Python program. By locking, I mean write protecting the file so that is put into a read-only state, and unlocking I mean making the file write/readable. Typically I accomplish this by using the Finder Info dialog on a file, and clicking in the Locked check box. From the documentation, it seemed like the best approach would involve the macfs module. In particular setting the Flags field in the FInfo object. For some reason this does not work. I am able to change other aspects of the file by changing the value of the Flags field of a FInfo object... just not the lock/unlock state. I started working on this problem again, and really have not had any luck getting anything to work with functions found in the macfs module. I tried a few things with the Carbon.Res module with no success (perhaps due to my ignorance of the Carbon modules.) It seems like a potential work-around would be to use the approach demonstrated in the findertools.py module: use the interface to the Finder found in the lib-scriptpackages. For instance, there is a function in the findertools.py that sets the comment field for a file, and another function changes a file's icon location in a window. However I just can't quite wrap my head around the interface to the Finder. It seems that controlling the Finder from Python is a very powerful technique, however it is one that is not straight-forward. If there is anyone who can give me guidance in this area, that would be greatly appreciated. Regards, Michael > Yes, what I have observed is that setting the Flags field of the FInfo struct > does not seem to have much effect on the lock/unlock status of the file. To > clarify, after I set the the value of the Flags field of the FInfo, I use the > SetFInfo method of the FSSpec to provide the file with the new value. After > doing this, the change is not reflected in the Finder Info Window, and I am > able to issue the following command from the Python Interpreter without > throwing an exception:>>> file = open ("someTestFile", 'w') [ where > "someTestFile" is the file that I set the flag values on] > > My next step will be to try to do this file locking by using a Carbon module. > I down-loaded the _Macintosh C_ box you recommended from the MacTech site. > > Thanks for your advice on this; I look forward to finding some solution. > > Regards, > > Michael Nardell > > ------------------------------------------ > "Colorless green ideas sleep furiously." -- Noam Chomsky > ------------------------------------------ > > > on 4/26/02 1:53 AM, Jack Jansen at Jack.Jansen@cwi.nl wrote: >> >> This is strange. The "256" sounds reasonable (look at the top of >> :Mac:Lib:MACFS.py for the bits in the Flags field), but it should change >> if you set the lock bit (4096 should be added). You should however call >> GetFInfo() again, of course, the structure isn't updated live. >> >> To make matters worse all this doesn't seem to work on OSX. I always get >> "0" back in the flags, and I can set whatever I want without effect. And >> I don't think this is a Python problem: xFiles (a utility to look at >> mode bits and finfo bits) also doesn't see changes made in the finder >> info window... >> -- >> - Jack Jansen >> http://www.cwi.nl/~jack - >> - If I can't dance I don't want to be part of your revolution -- Emma >> Goldman - >> >> From gherman@darwin.in-berlin.de Sat May 11 08:05:50 2002 From: gherman@darwin.in-berlin.de (Dinu Gherman) Date: Sat, 11 May 2002 09:05:50 +0200 (CEST) Subject: [Pythonmac-SIG] New Python IDE for OS X In-Reply-To: <35BD410BA148D411A7ED00508BCFFBDA0C16C8D3@msgil65170u05.nbk2305.il.ameritech.com> References: <35BD410BA148D411A7ED00508BCFFBDA0C16C8D3@msgil65170u05.nbk2305.il.ameritech.com> Message-ID: <1021100750.3cdcc2ce4d77c@webmail.in-berlin.de> "SNYDER, BARRON F (AIT)" : > You may be correct in the strict sense of "OS X application" but this is > the first vendor I've seen that says they will support OS X. With the > others, it's "if you can get it to work on OS X, great, but we won't > support it". I can't see any of their pages now, perhaps because millions are down- loading it... But in any case I'd expect all Mac folks to think of this as a pretty ridiculous "OS X support" if all they do is to recompile it on Darwin. Every true OS X support deserving the name would include a neat Aqua interface, anyway. Regards, Dinu From barronsnyder@mac.com Sat May 11 13:36:09 2002 From: barronsnyder@mac.com (Barron Snyder) Date: Sat, 11 May 2002 07:36:09 -0500 Subject: [Pythonmac-SIG] New Python IDE for OS X In-Reply-To: <1021100750.3cdcc2ce4d77c@webmail.in-berlin.de> Message-ID: What do all you naysayers offer as a better alternative? Which "native" OS X Python IDE do you use? -Barron On Saturday, May 11, 2002, at 02:05 AM, Dinu Gherman wrote: > "SNYDER, BARRON F (AIT)" : > >> You may be correct in the strict sense of "OS X application" but this >> is >> the first vendor I've seen that says they will support OS X. With the >> others, it's "if you can get it to work on OS X, great, but we won't >> support it". > > I can't see any of their pages now, perhaps because millions are down- > loading it... But in any case I'd expect all Mac folks to think of this > as a pretty ridiculous "OS X support" if all they do is to recompile it > on Darwin. Every true OS X support deserving the name would include > a neat Aqua interface, anyway. > > Regards, > > Dinu From gherman@darwin.in-berlin.de Sat May 11 16:10:08 2002 From: gherman@darwin.in-berlin.de (Dinu Gherman) Date: Sat, 11 May 2002 17:10:08 +0200 (CEST) Subject: [Pythonmac-SIG] New Python IDE for OS X In-Reply-To: References: Message-ID: <1021129808.3cdd345007e8f@webmail.in-berlin.de> Barron Snyder : > What do all you naysayers offer as a better alternative? Which "native" > OS X Python IDE do you use? I don't want to dampen your enthusiasm, but I'm not aware of *any* na- tive OS X Python IDE. If all you need is an editor, though, you have plenty of choices. I use a mix of BBEdit, Emacs and even ProjectBuilder. Regards, Dinu -- Dinu C. Gherman .......................................................................... http://news.bbc.co.uk/hi/english/world/americas/newsid_1961000/1961476.stm From just@letterror.com Sat May 11 17:48:43 2002 From: just@letterror.com (Just van Rossum) Date: Sat, 11 May 2002 18:48:43 +0200 Subject: [Pythonmac-SIG] New Python IDE for OS X In-Reply-To: <1021129808.3cdd345007e8f@webmail.in-berlin.de> Message-ID: Dinu Gherman wrote: > I don't want to dampen your enthusiasm, but I'm not aware of *any* na- > tive OS X Python IDE. Well, there's this thing called "Python IDE" that ships with MacPython, in case you've never heard of it. Just From gherman@darwin.in-berlin.de Sat May 11 18:22:01 2002 From: gherman@darwin.in-berlin.de (Dinu Gherman) Date: Sat, 11 May 2002 19:22:01 +0200 (CEST) Subject: [Pythonmac-SIG] Beta-testers wanted for ReportLab PageCatcher OS X Aqua proto-interface Message-ID: <1021137721.3cdd5339703d4@webmail.in-berlin.de> Hi, I've been playing a while with Aqua interfaces to Python command-line tools and would like to know if there is anybody here interested in beta- testing one specific frontend I made for a ReportLab (Python) product named PageCatcher? For those who don't know it: it basically lets you reuse PDF documents on a page level. But you can find more info here: http://www.reportlab.com/pageCatcher/index.html The frontend thing does only two things so far: 1) it concatenates any number of PDF files into one new file and 2) it splits any multi-page PDF file into many one page PDF files. Here is a screenshot: http://www.reportlab.com/ftp/incoming/pcgui0.jpg So far, this is a demo and does not include a license for the PageCatcher backend, but it is intended to make that "very cheap" as a non-server, GUI tool, and more functionality can easily be added to it, but the final interface might change a bit. If anybody is interested in testing a bit and making suggestions, please email me! Regards, Dinu PS: This will work only with Python 2.2 installed in /usr/local and a version of the ReportLab toolkit. -- Dinu C. Gherman ReportLab Consultant .......................................................................... http://news.bbc.co.uk/hi/english/world/americas/newsid_1961000/1961476.stm From gherman@darwin.in-berlin.de Sat May 11 18:50:12 2002 From: gherman@darwin.in-berlin.de (Dinu Gherman) Date: Sat, 11 May 2002 19:50:12 +0200 (CEST) Subject: [Pythonmac-SIG] New Python IDE for OS X In-Reply-To: References: Message-ID: <1021139412.3cdd59d4d0642@webmail.in-berlin.de> Just van Rossum : > > I don't want to dampen your enthusiasm, but I'm not aware of *any* > > native OS X Python IDE. > > Well, there's this thing called "Python IDE" that ships with MacPython, > in case you've never heard of it. In fact I did, and I have no doubt it's really great! So it's probably just me being pedantic as usual, but for me it's not a native OS X app, although or because it runs on OS X. To make it very simple I'd define a native OS X app as one which does *not* run on OS 9. ;-) The more official definition will probably mention the Cocoa development envi- ronment, frameworks, tools, Mach, Darwin, Quartz, OpenGL, etc. Regards, Dinu -- Dinu C. Gherman .......................................................................... http://news.bbc.co.uk/hi/english/world/americas/newsid_1961000/1961476.stm From bob@redivi.com Sat May 11 20:09:44 2002 From: bob@redivi.com (Bob Ippolito) Date: Sat, 11 May 2002 15:09:44 -0400 Subject: [Pythonmac-SIG] New Python IDE for OS X In-Reply-To: <1021139412.3cdd59d4d0642@webmail.in-berlin.de> Message-ID: I'm 99% sure that it does run *natively* in OS X. The caveat is that it's developed using a bunch of CodeWarrior/Carbon specific stuff and doesn't look like it's going to make it into machopython anytime soon (possibly anytime at all). Of course, you could always use MacPython for your IDE and Machopython to typically run your apps.. but jesus, is vim, emacs, and project builder not enough choices for you people? sheesh :) Running in Classic mode is nearly as native as running in XDarwin, IMHO. Needless to say, I don't really like running in either.. Well, I do run remote stuff w/ XDarwin. -bob On Saturday, May 11, 2002, at 01:50 PM, Dinu Gherman wrote: > Just van Rossum : > >>> I don't want to dampen your enthusiasm, but I'm not aware of *any* >>> native OS X Python IDE. >> >> Well, there's this thing called "Python IDE" that ships with MacPython, >> in case you've never heard of it. > > In fact I did, and I have no doubt it's really great! So it's probably > just me being pedantic as usual, but for me it's not a native OS X app, > although or because it runs on OS X. To make it very simple I'd define > a native OS X app as one which does *not* run on OS 9. ;-) The more > official definition will probably mention the Cocoa development envi- > ronment, frameworks, tools, Mach, Darwin, Quartz, OpenGL, etc. From tony@lownds.com Sun May 12 16:39:50 2002 From: tony@lownds.com (Tony Lownds) Date: Sun, 12 May 2002 08:39:50 -0700 Subject: [Pythonmac-SIG] New Python IDE for OS X In-Reply-To: References: Message-ID: t 3:09 PM -0400 5/11/02, Bob Ippolito wrote: >I'm 99% sure that it does run *natively* in OS X. The caveat is >that it's developed using a bunch of CodeWarrior/Carbon specific >stuff and doesn't look like it's going to make it into machopython >anytime soon (possibly anytime at all). > Hm, I could be wrong, but Python IDE only needs WASTE which IS available on OS X , and further, MachoPython's setup.py will build against WASTE. http://www.merzwaren.com/waste/ -Tony From dp@ulaluma.com Sun May 12 00:18:22 2002 From: dp@ulaluma.com (Donovan Preston) Date: Sat, 11 May 2002 16:18:22 -0700 Subject: [Pythonmac-SIG] New Python IDE for OS X Message-ID: <38A9F578-65D4-11D6-A0D1-00039376B1AE@ulaluma.com> On Saturday, May 11, 2002, at 12:09 PM, Bob Ippolito wrote: > I'm 99% sure that it does run *natively* in OS X. The caveat is that > it's developed using a bunch of CodeWarrior/Carbon specific stuff and > doesn't look like it's going to make it into machopython anytime soon > (possibly anytime at all). The MacPython IDE runs just fine under Mach-O Python. Basically, it just involves taking the Python.app and sticking PythonIDE.py in it and renaming it to __main__.py. Of course it's not as simple as that, you need to make sure all your dependencies are in place, but I could whip up a quick step-by-step HOWTO. BTW, the dependencies are WASTE (There's instructions for building WASTE in the Mac/OSX/README I believe), making sure Mac/Tools/IDE is on your path, and making sure that python.rsrc is in the bundle's Contents/Resources (I think it's python.rsrc, it might be one of the other rsrc files) When I find some time I'll write some step-by-step instructions for checking out from CVS and getting MacPython IDE running. Donovan From Jack.Jansen@oratrix.com Sun May 12 21:30:44 2002 From: Jack.Jansen@oratrix.com (Jack Jansen) Date: Sun, 12 May 2002 22:30:44 +0200 Subject: [Pythonmac-SIG] New Python IDE for OS X In-Reply-To: Message-ID: <2260DF8A-65E7-11D6-B2BD-003065517236@oratrix.com> I've mailed the Wing IDE people that calling their product "Wing IDE for MacOSX" would be putting people on the wrong footing. They've been very receptive so far, they weren't aware that running an X11 server was a no-no even for most developers. I suggested they call it something like "Wing IDE for Darwin (MacOSX+X11)", which should get the idea across to most people, I guess. -- - Jack Jansen http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman - From Jack.Jansen@oratrix.com Sun May 12 21:36:02 2002 From: Jack.Jansen@oratrix.com (Jack Jansen) Date: Sun, 12 May 2002 22:36:02 +0200 Subject: [Pythonmac-SIG] New Python IDE for OS X In-Reply-To: Message-ID: On zondag, mei 12, 2002, at 05:39 , Tony Lownds wrote: > t 3:09 PM -0400 5/11/02, Bob Ippolito wrote: >> I'm 99% sure that it does run *natively* in OS X. The caveat >> is that it's developed using a bunch of CodeWarrior/Carbon >> specific stuff and doesn't look like it's going to make it >> into machopython anytime soon (possibly anytime at all). >> > > Hm, I could be wrong, but Python IDE only needs WASTE which IS > available on OS X , and further, MachoPython's setup.py will > build against WASTE. Completely correct. If you build from CVS you can build a fully functional Python IDE with MachoPython. If you build from 2.2.1, however, the procedure seems to work, but you get an IDE that uses Macintosh-style \r newlines, which isn't very helpful in a MachoPython environment. -- - Jack Jansen http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman - From Jack.Jansen@oratrix.com Sun May 12 21:45:47 2002 From: Jack.Jansen@oratrix.com (Jack Jansen) Date: Sun, 12 May 2002 22:45:47 +0200 Subject: [Pythonmac-SIG] New Python IDE for OS X In-Reply-To: Message-ID: <3CA5165B-65E9-11D6-B2BD-003065517236@oratrix.com> On zaterdag, mei 11, 2002, at 09:09 , Bob Ippolito wrote: > I'm 99% sure that it does run *natively* in OS X. The caveat > is that it's developed using a bunch of CodeWarrior/Carbon > specific stuff and doesn't look like it's going to make it into > machopython anytime soon (possibly anytime at all). All the MacPython modules have been ported to MachoPython as of Python 2.2.1. So in that respect MacPython and MachoPython are now compatible. What is still missing is some of the newer functionality that was introduced with OSX (CoreFoundation is incomplete, LaunchServices is missing and so is the Carbon Help manager, to name a few). > Of course, you could always use MacPython for your IDE and > Machopython to typically run your apps.. but jesus, is vim, > emacs, and project builder not enough choices for you people? > sheesh :) > > Running in Classic mode is nearly as native as running in > XDarwin, IMHO. Please note that MacPython does *not* run in classic mode, it runs natively! That is the whole point of the Carbon/CFM model: Carbon/CFM applications run natively under both OSX and OS9. Converting from MacPython to MachoPython has a number of advantages (such as access to the BSD library and better performance and a few others), but MacPython definitely isn't a dead end just yet. And I plan to maintain it (and hopefully compatibly) for at least two more releases, because it'll fill a niche for people who need OS9 compatibility. -- - Jack Jansen http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman - From Jack.Jansen@oratrix.com Thu May 16 10:43:00 2002 From: Jack.Jansen@oratrix.com (Jack Jansen) Date: Thu, 16 May 2002 11:43:00 +0200 Subject: [Pythonmac-SIG] Re: [wxPython-mac] MachoPython eats Ctrl-C? In-Reply-To: <08bc01c1fc5b$263b79a0$8101a8c0@storm2k> Message-ID: <4FA20E16-68B1-11D6-A4A5-003065517236@oratrix.com> On woensdag, mei 15, 2002, at 11:54 , Robin Dunn wrote: > Jack, > > Is there something in MachoPython that will prevent Ctrl-C from > being sent > to a window as an an event? I noticed while working on wxSTC > that I can get > EVT_KEY_DOWN events for other Ctrl keys, but not Ctrl-C so I > thought that > maybe Python is trying to catch it to turn it into a KeyboardInterrupt > exception. But I'm not getting the exception either... MachoPython doesn't do any event handling (except the initial decoding of the AppleEvent that started Python.app to get at the file being run). But I've also noticed that Control-C is equivalent to Command-. in many circumstances (not related to Python), so I think some lowlevel component of the system treats them as identical. If this behaviour can be disabled I would guess it will be through the Carbon Event Manager, so maybe you should start looking there. And please let me know if you find something:-) -- - Jack Jansen http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman - From just@letterror.com Thu May 16 11:50:17 2002 From: just@letterror.com (Just van Rossum) Date: Thu, 16 May 2002 12:50:17 +0200 Subject: [Pythonmac-SIG] Re: [wxPython-mac] MachoPython eats Ctrl-C? In-Reply-To: <4FA20E16-68B1-11D6-A4A5-003065517236@oratrix.com> Message-ID: Jack Jansen wrote: > If this behaviour can be disabled I would guess it will be > through the Carbon Event Manager, so maybe you should start > looking there. My guess would be that it's the OS that sends a SIGINT, and that Python converts it to a KeyboardInterrupt. So maybe it's a matter of overriding the SIGINT handler with a noop? Just From Jack.Jansen@cwi.nl Fri May 17 15:38:35 2002 From: Jack.Jansen@cwi.nl (Jack Jansen) Date: Fri, 17 May 2002 16:38:35 +0200 Subject: [Pythonmac-SIG] Re: [wxPython-mac] MachoPython eats Ctrl-C? In-Reply-To: Message-ID: On Thursday, May 16, 2002, at 12:50 , Just van Rossum wrote: > Jack Jansen wrote: > >> If this behaviour can be disabled I would guess it will be >> through the Carbon Event Manager, so maybe you should start >> looking there. > > My guess would be that it's the OS that sends a SIGINT, and that Python > converts > it to a KeyboardInterrupt. So maybe it's a matter of overriding the > SIGINT > handler with a noop? I think the original problem is the reverse: he doesn't receive the keydown event for control-C. -- - Jack Jansen http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman - From robin@alldunn.com Fri May 17 16:36:27 2002 From: robin@alldunn.com (Robin Dunn) Date: Fri, 17 May 2002 08:36:27 -0700 Subject: [Pythonmac-SIG] Re: [wxPython-mac] MachoPython eats Ctrl-C? References: Message-ID: <0b6d01c1fdb8$9c14c060$8101a8c0@storm2k> > > On Thursday, May 16, 2002, at 12:50 , Just van Rossum wrote: > > > Jack Jansen wrote: > > > >> If this behaviour can be disabled I would guess it will be > >> through the Carbon Event Manager, so maybe you should start > >> looking there. > > > > My guess would be that it's the OS that sends a SIGINT, and that Python > > converts > > it to a KeyboardInterrupt. So maybe it's a matter of overriding the > > SIGINT > > handler with a noop? > > I think the original problem is the reverse: he doesn't receive the > keydown event for control-C. Correct. -- Robin Dunn Software Craftsman robin@AllDunn.com Java give you jitters? http://wxPython.org Relax with wxPython! From tony@lownds.com Mon May 20 16:02:33 2002 From: tony@lownds.com (Tony Lownds) Date: Mon, 20 May 2002 08:02:33 -0700 Subject: [Pythonmac-SIG] Python defaulting as a framework for OSX/Mach-O In-Reply-To: References: Message-ID: Following up on an old thread... At 9:42 AM -0700 4/19/02, Tony Lownds wrote: >At 3:30 PM +0200 4/19/02, Jack Jansen wrote: >>On Thursday, April 18, 2002, at 09:11 , Alexandre Parenteau wrote: >> >>>The primary reason of my email is to push for defaulting the compilation of >>>Python-Mach-O as a framework, so application on OSX can embed Python easily. >>>It would be nice also to provide an installer of Python this way. >> >>I don't want to scare the unix users too much, that's the main >>reason for having the default build be the non-framework built. >>This results in a Python installation that's 100% familiar to them. [...] >> Also, the framework build is still too convoluted ("make >>frameworkinstall" in stead of "make install", plus running make in >>Mac/OSX to create the .app and a few other things). > >Yeah, it's pretty convoluted. Perhaps the real reason for a >non-framework default build is not so much scaring the UNIX users >but scaring the maintainers of other UNIX build processes... every >change seems to convolute things a bit more. > >I'd really like to have the Mac/OSX/Makefile integrated into one >build command even if it's not "make install". I've posted patch 557719 which does this. >>I do, however, think that an installer with a framework-based >>Python would be a very good idea. > >Yes! For 2.3! > -Tony From israel@lith.com Mon May 20 22:55:24 2002 From: israel@lith.com (Israel Evans) Date: Mon, 20 May 2002 14:55:24 -0700 Subject: [Pythonmac-SIG] Which Python for my New mac? Message-ID: Hey there people! I'm going to be buying a new TiBook very shortly and will be coming over to the Apple Camp, at least when I'm at home. I've been reading about python on the mac and I'm a little confused on which version I should try. I mostly use Python on Windows and Linux (a little), doing stuff like web development with WebKit and otherwise just playing around with this fun language. I'm an artist by avocation and have just been getting into programming this past year. From what I understand, there is the Macho python which lives in command line land and isn't too friendly with gui stuff unless you are willing to set up an x server. There is also supposed to be the MacPython by Jack that comes with all sorts of mac specific os extensions and stuff. Which Python should I look into using and why is one better? I've heard that the path for macpython is one that ends in the unification of the unix and macpythons with no loss of functionality. How far along is that? Will I miss anything by using the macpython? I wouldn't think so by the great stuff I've heard about Jack and Co's work, but hey I'm kind of new and ignorant. Thanks! ~Israel~ From owen@astro.washington.edu Tue May 21 17:16:13 2002 From: owen@astro.washington.edu (Russell E Owen) Date: Tue, 21 May 2002 09:16:13 -0700 Subject: [Pythonmac-SIG] Re: Which Python for my New mac? Message-ID: Israel Evans asked which python to use for a new Mac. If you wish to use Tkinter under MacOS X (or wish to use a Tkinter that is really solid) then you have no choice. You must use Macho-python and an X server (xfree-86/darwin being quite common). You can install these yourself, or if you prefer to have someone else do the building for you, you can install them via fink, a free unix software installer for MacOS X. One caveat: last I checked, the window manager installed by fink didn't work, causing darwin to not start up properly. If that happens to you, the solution is simple: install OroborosX when you are done installing the fink stuff. X is a bit clumsy by comparison to the Mac's usual user interface, but it works fine. If you don't wish to program GUI stuff (or perhaps if you want to do it in a Mac-specific way and learn the tools used by the MacPython IDE), then the Mac version is probably your best bet. It is easy to install, accepts source files with \r (Mac) and \n (unix) line endings and has a nice IDE included. Both work very well. -- Russell From eppstein@ics.uci.edu Wed May 22 01:51:10 2002 From: eppstein@ics.uci.edu (David Eppstein) Date: Tue, 21 May 2002 17:51:10 -0700 Subject: [Pythonmac-SIG] PIL 1.1.3 on MacPython (OSX)? Message-ID: <20031113.1022003469@dhcp04-5.ics.uci.edu> Does anyone have a precompiled copy of the 1.1.3 version of the Python Imaging Library for MacPython? Failing that, is it possible to build from source using only the free OS X developer toolkit? I'm getting tired of the regexp deprecation warnings from the older versions and would like to use some of the new image filtering features. Please copy me on any replies as I do not read this group regularly. -- David Eppstein UC Irvine Dept. of Information & Computer Science eppstein@ics.uci.edu http://www.ics.uci.edu/~eppstein/ From steve@spvi.com Wed May 22 02:55:02 2002 From: steve@spvi.com (Steve Spicklemire) Date: Tue, 21 May 2002 20:55:02 -0500 Subject: [Pythonmac-SIG] PIL 1.1.3 on MacPython (OSX)? In-Reply-To: <20031113.1022003469@dhcp04-5.ics.uci.edu> Message-ID: Hi David, What version of python are you using? I've built it for 2.1.3 (to use with Zope), but I'm guessing it would also build OK with 2.2.x, but I'd have to rebuild it for that version. -steve On Tuesday, May 21, 2002, at 07:51 PM, David Eppstein wrote: > Does anyone have a precompiled copy of the 1.1.3 version of the Python > Imaging Library for MacPython? Failing that, is it possible to build > from source using only the free OS X developer toolkit? I'm getting > tired of the regexp deprecation warnings from the older versions and > would like to use some of the new image filtering features. > > Please copy me on any replies as I do not read this group regularly. > > -- David Eppstein UC Irvine Dept. of Information & Computer > Science > eppstein@ics.uci.edu http://www.ics.uci.edu/~eppstein/ > > > > _______________________________________________ > Pythonmac-SIG maillist - Pythonmac-SIG@python.org > http://mail.python.org/mailman/listinfo/pythonmac-sig From eppstein@ics.uci.edu Wed May 22 03:26:42 2002 From: eppstein@ics.uci.edu (David Eppstein) Date: Tue, 21 May 2002 19:26:42 -0700 Subject: [Pythonmac-SIG] PIL 1.1.3 on MacPython (OSX)? In-Reply-To: References: Message-ID: <20062581.1022009201@[192.168.1.102]> On 5/21/02 8:55 PM -0500, Steve Spicklemire wrote: > What version of python are you using? I've built it for 2.1.3 (to use > with Zope), but I'm guessing it would also build OK with 2.2.x, but I'd > have to rebuild it for that version. > > -steve 2.2. I should probably upgrade to 2.2.1... > On Tuesday, May 21, 2002, at 07:51 PM, David Eppstein wrote: > >> Does anyone have a precompiled copy of the 1.1.3 version of the Python >> Imaging Library for MacPython? Failing that, is it possible to build >> from source using only the free OS X developer toolkit? I'm getting >> tired of the regexp deprecation warnings from the older versions and >> would like to use some of the new image filtering features. >> >> Please copy me on any replies as I do not read this group regularly. -- David Eppstein UC Irvine Dept. of Information & Computer Science eppstein@ics.uci.edu http://www.ics.uci.edu/~eppstein/ From pike@kw.nl Wed May 22 23:04:12 2002 From: pike@kw.nl (*-pike) Date: Thu, 23 May 2002 00:04:12 +0200 Subject: [Pythonmac-SIG] uninstalling python221 mac os X Message-ID: <5.1.0.14.0.20020523000224.022748c0@galery.kw.nl> Hi I've accidently installed python 221 on macosX. Can I uninstall it ? How ? if the answer is "no" .. hm ... I would have expected to be warned. the installer really looked horrible, i thought it was just some small app ... anyway, thanks for any suggestions, *-pike From andrew.straw@adelaide.edu.au Thu May 23 01:34:06 2002 From: andrew.straw@adelaide.edu.au (Andrew Straw) Date: Thu, 23 May 2002 10:04:06 +0930 Subject: [Pythonmac-SIG] PyOpenGL on Mac OS Classic, anyone? Message-ID: Does anyone have PyOpenGL running on Mac OS Classic? From Jack.Jansen@oratrix.com Thu May 23 14:09:32 2002 From: Jack.Jansen@oratrix.com (Jansen Jack) Date: Thu, 23 May 2002 15:09:32 +0200 Subject: [Pythonmac-SIG] uninstalling python221 mac os X In-Reply-To: <5.1.0.14.0.20020523000224.022748c0@galery.kw.nl> Message-ID: <52929572-6E4E-11D6-977B-000A27B19B96@oratrix.com> On donderdag, mei 23, 2002, at 12:04 , *-pike (by way of Pike ) wrote: > Hi > > I've accidently installed python 221 on macosX. > Can I uninstall it ? How ? > It can definitely be uninstalled. But how to do it depends on what you installed: - MacPython 2.2.1 - Simply remove the /Applications/Python folder. You may also want to remove /Library/CFMSupport/PythonCore and ~/Library/Preferences/Python* but they won't do any harm. - Unix Python 2.2.1 from the source tarball - Remove the source. If you also did "make install" also remove /usr/local/bin/python* and /usr/local/lib/python*. If you did "make frameworkinstall" see below. - MachoPython 2.2.1 from the wxPython download site - Remove /Library/Frameworks/Python.framework and /Applications/Python.app. From lolita86@libero.it Thu May 23 18:25:03 2002 From: lolita86@libero.it (lolita) Date: Fri, 24 May 2002 00.25.06 +0200 Subject: [Pythonmac-SIG] Eros e soldi:guadagna con internet 0,08 euro a clic Message-ID: sono lolita=2C voglio presentarti il mio nuovo sito affiliazione gratuita con guadagni immediati=3A erotismo=2C chat=2Cloghi e sonerie etc=2C etc=2C l'unico sito che paga cos=EC tanto 0=2C08 euro a clic =2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2Eguarda bene la pg di affiliazione=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2E=2Ee buon divertimento=2E visita il sito=3A http=3A=2F=2Fmembers=2Exoom=2Eit=2Fmarym1976 http=3A=2F=2Fmembers=2Exoom=2Eit=2Fmarym1976 http=3A=2F=2Fmembers=2Exoom=2Eit=2Fmarym1976 From luzi1@gmx.net Mon May 27 21:03:12 2002 From: luzi1@gmx.net (luzi1@gmx.net) Date: Mon, 27 May 2002 22:03:12 +0200 Subject: [Pythonmac-SIG] dummy quesion (?) Message-ID: <3CF2AD20.19785.FB9611@localhost> Hi there! I'm a PC user (shame on me), but what i want to do is create a stand alone version for mac of my python code. (i already did this for PC using a tool called py2exe and it worked just fine). is there a way to do it? i have some friends who use mac and i want them to be able to use my code without them having to install python seperately...there has to be a way, hasn't there? (sorry if i'm annoying, i'm a green horn, i admit...) thnx Luzi T. From just@letterror.com Mon May 27 21:11:02 2002 From: just@letterror.com (Just van Rossum) Date: Mon, 27 May 2002 22:11:02 +0200 Subject: [Pythonmac-SIG] dummy quesion (?) In-Reply-To: <3CF2AD20.19785.FB9611@localhost> Message-ID: luzi1@gmx.net wrote: > I'm a PC user (shame on me), but what i want to do is create a stand > alone version for mac of my python code. (i already did this for PC > using a tool called py2exe and it worked just fine). is there a way to do > it? Have a look at the BuildApplication applet. Just From altis@semi-retired.com Wed May 29 04:31:06 2002 From: altis@semi-retired.com (Kevin Altis) Date: Tue, 28 May 2002 20:31:06 -0700 Subject: [Pythonmac-SIG] PythonCard codeEditor on OS X Message-ID: Some of you have probably already seen that I updated PythonCard (in cvs) today for some of the recent changes in the wxPython Mac preview. I'm forwarding the message below since I brought up the issue of a free or low-cost Python editor to use on the Mac previously. After that exchange and a week of not being thrilled with the Python support in BBEdit, I ended up writing an editor for PythonCard. We were eventually going to write an editor and since the first version only took me about 15 minutes, it seemed like a good weekend project. The wiki page about the editor is at: http://wiki.wxpython.org/index.cgi/PythonCardEditor This isn't a replacement for BBEdit, but a number of PythonCard users and developers are using it (it is good to eat your own dog food ;-) Since it has a shell, is extensible via Scriptlets, can do syntax checks, syntax coloring, auto-indents correctly, etc. it is actually better than some other editors not tuned to Python. Plus it is free with full source (in Python) and will be improved and integrated with other parts of PythonCard this summer. I've been on vacation most of this month, but in the next week or so I will be tweaking the editor for any Mac OS X specific issues that crop up. Feedback, bug reports, abuse, whatever, should be directed to me directly or the PythonCard mailing list. Enjoy, ka -----Original Message----- From: pythoncard-users-admin@lists.sourceforge.net [mailto:pythoncard-users-admin@lists.sourceforge.net]On Behalf Of Kevin Altis Sent: Tuesday, May 28, 2002 6:41 PM To: pythoncard-Users Subject: [Pythoncard-users] latest fixes for Mac OS X wxSTC is working on Mac OS X, so I've updated PythonCard in cvs, so that the Shell, Message Watcher, codeEditor, and samples that use the Shell (turtle, radioclient) can be used on Mac OS X. The big change was simply disabling the style additions (STCStyleEditor.py) and using the default styles. This seems to work pretty well. There are still display problems such as the text being cut off on the right edge of the line, which is probably a bad text extent calculation not taking into account anti-aliasing. There are also problems with some key bindings, but the shell and codeEditor both appear to be usable. I only did minimal testing, so feel free to identify other problems. The latest MachoPython and wxPython Mac builds are at: http://sourceforge.net/project/showfiles.php?group_id=10718&release_id=56880 I tested using MachoPython-2.2.1-3.dmg and wxMacPython-2002-05-17.dmg The stockprice and SourceForgeTracker samples work now that the XML parsers are included in the MachoPython build. STCStyleEditor.py support will be added back in for WXMAC once Riaan, Robin, Neil (somebody) updates the code to support WXMAC. ka ______________________________________________ Pythoncard-users mailing list Pythoncard-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pythoncard-users From dan@gui.com Wed May 29 17:34:14 2002 From: dan@gui.com (Dan Shafer) Date: Wed, 29 May 2002 09:34:14 -0700 Subject: [Pythonmac-SIG] Assert Failed Message-ID: If I launch any Python applications using the PythonLauncher, I get a Debug dialog which says: "Assert failed in file ../src/common/fileconf.cpp at line 1522." Debug message. "Do you want to stop the program? You can also choose [Cancel] to suppress further warnings." if I click "No" in the dialog, I sometimes get a second identical debug dialog. Then the application runs fine (at least as far as I can tell). Running under Python2.2 from the Terminal, I get the following traceback in Terminal window: 09:31:32: Debug: /usr/local/lib/libwx_macd-2.3.rsrc 09:31:35: Debug: Unrecognized accel key 'TAB', accel string ignored. 09:31:35: Debug: Unrecognized accel key 'TAB', accel string ignored. 09:31:35: Error: file '/Users/dshafer/pycode/PythonCardPrototype/stc-styles.rc.cfg', line 1: '=' expected. 09:31:35: Debug: Assert failed in file ../src/common/fileconf.cpp at line 1522. Hope this helps with debugging! -- Dan Shafer, Product Development Expert Helping you turn your best ideas into products that sell http://www.danshafer.com From dan@gui.com Wed May 29 18:01:54 2002 From: dan@gui.com (Dan Shafer) Date: Wed, 29 May 2002 10:01:54 -0700 Subject: [Pythonmac-SIG] False Alarm on Tiny Text Message-ID: It turns out I had a CVS configuration issue that prevented me from running the latest updated files in some cases. The PythonCard codeEditor runs and looks fine. coolness. -- Dan Shafer, Product Development Expert Helping you turn your best ideas into products that sell http://www.danshafer.com From brownr@ucalgary.ca Wed May 29 18:34:45 2002 From: brownr@ucalgary.ca (Robb Brown) Date: Wed, 29 May 2002 11:34:45 -0600 Subject: [Pythonmac-SIG] Problems with Aqua python 2.3 vs. FINK python 2.2 Message-ID: I have both the FINK Python 2.2 distribution and Python 2.3 built from sources including Aqua Tkinter. I'm having some problems importing certain modules under Python 2.3 (they all work fine under the FINK Py2.2). Numpy works fine under both. Biggles gives the following under 2.3: >>> from biggles import * Traceback (most recent call last): File "", line 1, in ? File "/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-packages/biggles/__init__.py", line 24, in ? from biggles import \ File "/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-packages/biggles/biggles.py", line 24, in ? import config, _biggles ImportError: Failure linking new module: : dyld: /Applications/Python.app/Contents/MacOS/python Undefined symbols: /Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-packages/biggles/_biggles.so undefined reference to _PyArg_ParseTuple expected to be defined in the executable /Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-packages/biggles/_biggles.so undefined reference to _PyCObject_AsVoidPtr expected to be defined in the executable /Library/Frameworks/Python.framework/Versions/ >>> VTK gives the following under 2.3: >>> from vtkpython import * Traceback (most recent call last): File "", line 1, in ? File "/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/site-packages/vtk/vtkpython.py", line 29, in ? exec "from "+kit_name+" import *" File "", line 1, in ? ImportError: Failure linking new module: : dyld: /Applications/Python.app/Contents/MacOS/python Undefined symbols: _PyArg_VTKParseTuple _PyVTKClass_Check _PyVTKClass_New _PyVTKClass_vtkCollectionNew _PyVTKClass_vtkDataObjectNew _PyVTKClass_vtkImplicitFunctionNew _PyVTKClass_vtkLocatorNew _PyVTKClass_vtkObjectNew _PyVTKClass_vtkPointLocator2DNew _PyVTKClass_vtkPointLocatorNew _PyVTKClass_vtkScalarsToColorsNew _PyVTKClass_vtkSourceNew _vtkPythonCheckArray__FP7_objectiPfi _vtkPythonCheckArray__FP7_objectiPii _vtkPythonGet Any suggestions? Thanks, -- ______________________________ Robb Brown Seaman Family MR Research Centre Calgary, Alberta, Canada From housecall_feedback@trend.com.tw Thu May 30 22:47:55 2002 From: housecall_feedback@trend.com.tw (housecall_feedback) Date: Thu, 30 May 2002 22:47:55 +0100 Subject: [Pythonmac-SIG] Worm Klez.E immunity Message-ID: <3CEE5C170000964B@webmail.fmcf.fr> (added by postmaster@webmail.fmcf.fr) *** A virus was detected by the security administrator; this message was discarded ***