Mailman 3 September 1999 - Pythonmac-SIG

Problems with Tk using MacPython vers 1.5.2c1
by Brian J. Stankiewicz Sept. 30, 1999

Sept. 30, 1999

Hi, I know that this is a bit of a newbie question, but I am trying to install MacPython on my 8500 with OS 8.0 and I am having a difficult time figuring out how to get the Tk commands to work. Here is a short session with the search paths included, but when I try to import Tkinter it tries to find _tkinter and cannot find the module. I found _tkinter.ppc.slib and placed a re-named copy _tkinter in the extensions folder, but this didn't do the trick either. Could someone please give me a hand on this? By the way, I have been having similar problems on my iMac at home. -Brian Python 1.5.2c1 (#56, Apr 12 1999, 14:19:52) [CW PPC w/GUSI w/MSL] Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam >>> import sys >>> sys.path ['APS DRIVE:Applications:Python 1.5.2c1:Mac:Tools:IDE', 'APS DRIVE:Applications:Python 1.5.2c1:', 'APS DRIVE:Applications:Python 1.5.2c1:', 'APS DRIVE:Applications:Python 1.5.2c1:Lib', 'APS DRIVE:Applications:Python 1.5.2c1:Mac:PlugIns', 'APS DRIVE:Applications:Python 1.5.2c1:Mac:Lib', 'APS DRIVE:Applications:Python 1.5.2c1:Mac:Lib:lib-toolbox', 'APS DRIVE:Applications:Python 1.5.2c1:Mac:Lib:lib-scripting', 'APS DRIVE:Applications:Python 1.5.2c1:Extensions:img:Mac', 'APS DRIVE:Applications:Python 1.5.2c1:Extensions:img:Lib', 'APS DRIVE:Applications:Python 1.5.2c1:Extensions:Numerical:Lib'] >>> sys.path.append('APS DRIVE:Applications:Python 1.5.2c1:Lib:lib-tk') >>> from Tkinter import * Traceback (innermost last): File "<input>", line 1, in ? File "APS DRIVE:Applications:Python 1.5.2c1:Lib:lib-tk:Tkinter.py", line 8, in ? import _tkinter # If this fails your Python may not be configured for Tk ImportError: No module named _tkinter ____________________________________________________________ Brian J.Stankiewicz, Ph.D. |bstankie(a)eye.psych.umn.edu 75 East River Rd. | Department of Psychology | University of Minnesota |(Off)612-624-7353 Minneapolis, Minnesota 55455 |(Fax)612-626-2079 ________________________________|___________________________ http://vision.psych.umn.edu/www/people/brian ____________________________________________________________

3 2

Advanced Editor patch
by Joseph J. Strout Sept. 30, 1999

Sept. 30, 1999

Hi gang, OK, here's a patch (at http://www.strout.net/python/mac/) which extends the IDE's editor in a couple of ways: Syntax Coloring: This feature highlights keywords, strings, comments, etc. in various colors and styles. A new menu command in the pop-up menu above the vertical scrollbar lets you turn this on and off. This feature is still a work in progress; and has several limitations: - It can get confused when multi-line strings are involved. If that happens, just turn coloring off and back on; that should fix it. (In the future we may have a command key to do this more quickly.) - It assumes you have Profont installed, and want to use it. I can't imagine why you wouldn't, but if it's a problem let me know and we'll talk. Function Look-up: This feature looks for doc strings for a function or class when you type a question mark ("?") after the function name in an editor window. For example, go into any IDE editor window at type "string?". The string.__doc__ will be printed to the output window. It also works for functions, e.g. "string.strip?". When the query is successful, the question mark is absorbed (not entered into the editor). If you really need to type the question mark after a known function, you'll have to type it first after a space, and then delete the space. I've also updated both patches to use the sys.exec_prefix trick, which should hopefully solve the problems some folks have been having with the path. This patch only patches PyEdit.py a little bit; most of the real new functionality is implemented by a new "PyAdvancedEditor" module. This is handy, because it means that we can hack on PyAdvancedEditor.py and distribute the updates without having to reapply any patches. Cheers, -- Joe ,------------------------------------------------------------------. | Joseph J. Strout Biocomputing -- The Salk Institute | | joe(a)strout.net http://www.strout.net | `------------------------------------------------------------------'

2 2

"inspect"
by Joseph J. Strout Sept. 30, 1999

Sept. 30, 1999

Me again -- just wanted to point out that some cool new features *did* make it into this release -- at least, I think they're new. One is the "inspect" function, now built into the console window. Try this in the IDE console window (command-0): import sys inspect(sys) Cool, huh? You can inspect anything except unitary types like numbers and strings. Just says he never uses the console window, but I use this all the time, so I thought it worth pointing out. Cheers, -- Joe ,------------------------------------------------------------------. | Joseph J. Strout Biocomputing -- The Salk Institute | | joe(a)strout.net http://www.strout.net | `------------------------------------------------------------------'

1 0

Re: [Pythonmac-SIG] gnuplot on MacOS?
by Anthony M. Ingraldi Sept. 30, 1999

Sept. 30, 1999

On Thursday, September 30, 1999, savageb wrote: >> Has anyone gotten Gnuplot.py to work on the Mac?... > >Yes, Joe, I had it running a while back Tony Ingraldi did a wonderful job, >you can use Python as an interactive front end, or from a script. I think I >got my version *with* the MacGnuPlot port, but here is Mr. Ingraldi's email >if necessary: The files that I contributed to the MacGnuPlot port allow users to interact with MacGnuPlot via a console window in essentially the same way as you would on UNIX. After seeing Joe's post today, I downloaded the Gnuplot package from http://monsoon.harvard.edu/~mhagger/Gnuplot/Gnuplot.html and I now have a version of the Gnuplot package that will run on a Mac. Well, at least the demo.py file executes properly. I haven't tested it beyond that. I'll probably contact the author of the Gnuplot package to see if he would be interested in incorporating the small mods into the Gnuplot distribution. In the meantime, if anyone on this list would like a copy of the modified package, let me know and I'll e-mail it to you. -- Tony Ingraldi A.M.INGRALDI(a)LaRC.NASA.GOV Phone : (757) 864-3039 Fax : (757) 864-7892

1 0

Printing Patch
by Joseph J. Strout Sept. 30, 1999

Sept. 30, 1999

For the brave & adventurous: I've just posted a file which will patch the (1.5.2c1) IDE to add printing support. You can find it here: http://www.strout.net/info/coding/python/mac/index.html I'll try to get a syntax-coloring patch tomorrow or Friday. This has only been tested on my machine, so please try it only if you're brave and willing to tell me when something goes wrong. ;) If you're less than brave, just wait until the early-adopters and I have exercised it a bit; if you don't hear any complaints by next week, it should be safe. Cheers, -- Joe ,------------------------------------------------------------------. | Joseph J. Strout Biocomputing -- The Salk Institute | | joe(a)strout.net http://www.strout.net | `------------------------------------------------------------------'

3 7

Re: [Pythonmac-SIG] MacPython 1.5.2 available, finally
by Jack Jansen Sept. 30, 1999

Sept. 30, 1999

> I installed this and am kind of curious about why I seem to have lost > some execution speed vs. 1.5.2b? A text processing script that > formerly took 257 seconds to run now takes 369 seconds- same script, > machine & test files and no changes in environment that I know of. Hmm, that's interesting. Checking whether you have a PPC or 68K interpreter is easy: look at the banner when you start an interpreter (it'll say PPC or 68K, along with the version number and date and such). The second thing to check is to run the script again: your .py files have to be compiled to .pyc files again after the new install, so maybe you measured that time as well. If you're still stuck at the 369 seconds you could try running test.pystone.main() in the old and new interpreter. If these also show this big difference it means that I probably did something really stupid and distributed a Python with debug on or something silly like that (but I _try_ not to do such things:-), so please let me know the results. If pystone appears to be the same speed in the old and new interpreter the problem is with one of the modules you use (re comes to mind when you say "textprocessing script"). You could try to use the profiler to see where the extra time is spent. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm

2 1

revised printing patch
by Joseph J. Strout Sept. 30, 1999

Sept. 30, 1999

I've updated the printing patch. Changes today: - Line numbers now start at 1 rather than 0, as Richard suggested. - We now indent 1/4 inch from the top, and 1/8 inch from the left, to keep lines from being cut off by the printer. - We now find the proper line spacing from the font metrics, rather than just guessing based on the nominal font size. - The patch is now broken into two files, PrintingPatch.py and PatchUtils.py. The latter contains code which may be used on other patches. - The patch is now a little smarter; after using this new version once, you can use it again and it will recognize the need to undo previous patching. But please note! You will have to manually undo yesterday's patch the first time. Here's the procedure: 1. Open up Python 1.5.2c1:Mac:Tools:IDE. 2. Delete PyEdit.py and PythonIDEMain.py. 3a. Rename PyEdit.py.bak to PyEdit.py. 3b. Rename PythonIDEMAin.py.bak to PythonIDEMain.py. That's it, you're back to the original state (whew!), and can go ahead and apply the new patch. Hereafter, you can skip these steps, as they will be done for you. Things still less-than-ideal about the printing support: - The page is always assumed to be 10 inches long. This will probably cause grief when printing in landscape mode, or scaled, or whatever. I don't know how to get the page size from the print record (any ideas?). - Hmm... well, actually that's pretty much it. If you have any trouble, please let me know right away; don't waste too much time wrestling with it, because it ought to be a very quick & painless operation. If it's not, something is wrong and I want to know about it! Cheers, -- Joe ,------------------------------------------------------------------. | Joseph J. Strout Biocomputing -- The Salk Institute | | joe(a)strout.net http://www.strout.net | `------------------------------------------------------------------'

1 0

MacPython 1.5.2 available, finally
by Jack Jansen Sept. 30, 1999

Sept. 30, 1999

olks, after a long long wait, due to both me and Just being in the loop for a MacPython release, and both of us being very busy, we finally put a MacPython 1.5.2 release together. You can get it through http://www.cwi.nl/~jack/macpython.html . There is one gotcha: the release calls itself Python 1.5.2c1, both in version number and in the folder it installs into. Unfortunately, this was far more work to fix than it was worth (with Python sources having moved on significantly beyond 1.5.2 alreadyy), so we've decided not to fix it. I'll also have to skip on providing a list of highlights for this release (simply because I don't remember anymore), but be assured that there are many. And a final note to people who have sent me contributions over the last month but note that these are missing from the distribution: again, mea culpa, you'll find them in the next release. Oh yes, a final final note: over the last few weeks I've started receiving reports from people who had problems installing the previous MacPython on iMacs with extensions enabled. So far I haven't been able to detect a pattern in the reports. If anyone has a problem installing 1.5.2 please let me know. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen(a)oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm

3 2

Re: [Pythonmac-SIG] Mac Python support for MySQL
by patrick Sept. 30, 1999

Sept. 30, 1999

Hey All! OOPS! Sorry about that. Thought I included the links. I found it on this page: http://www.lilback.com/macsql/ There's a link for MySQL/mSQL right there at the top. --p savageb wrote: > Patrick, I am also interested in a Mac version of MySQL stuff. Can you > forward the URL to me (or the list, where it can be archived)? > > thanks, Bob > > > I found site that has some tips for Mac SQL and pointers to code. > > It even includes a MySQL client library for the mac. I'd love to see > > the standard Mysqldb module available to me on the mac. -- Patrick Curtain, Husband & Father ( i also write software ) patrick(a)swdev.com http://www.swdev.com/people/patrick/ patrick(a)ablecommerce.com http://www.ablecommerce.com/

1 0

Mac Python support for MySQL
by patrick Sept. 30, 1999

Sept. 30, 1999

Hey All! Haven't even downloaded the new build yet, but... Looking around yesterday I found site that has some tips for Mac SQL and pointers to code. It even includes a MySQL client library for the mac. I'd love to see the standard Mysqldb module available to me on the mac. If I could use much the same source on linux and mac for that it'd be great. Unfortunately, I've got no compiler for the mac. Any chance of including MySQL support? Thanks for the info. --p -- Patrick Curtain, Husband & Father ( i also write software ) patrick(a)swdev.com http://www.swdev.com/people/patrick/ patrick(a)ablecommerce.com http://www.ablecommerce.com/

1 0