🌐 Mailman 3 July 2001 - Pythonmac-SIG - python.org

RE: [Tutor] using IDLE and changing variables
by alan.gauld＠bt.com July 30, 2001

July 30, 2001

> when you make changes to a module that you are importing, > the changes won't be recognized unless you force a reload Correct, at the interactive prompt. > Let's say at one point you had a variable x defined > and you used it in several places. Then you change > the variable from x to y but forget to change it > everywhere. That'd be a programmer error in every environment I've ever used. Some language compilers will tell you if you remove the original declaration/definition of the variable (x in your case) and then try to use it. Python will warn you in some situations. But it has nothing to do with IDLE per se, it's all to do with Python itself. > I guess what I'm looking for is something like BASIC's "new" > command that flushes out everything of the session and begins > fresh. The interactive prompt doesn't have that feature but working in IDLE the best thing IMHO is simply to create a new file using File|New... The >>> prompt is great for playing with ideas but if its more than a few lines of code I prefer to work in a file and edit/save/run - even if the file is just a throw-away like tmp.py of foo.py or whatever. Alan G

1 0

MacPython 2.1.1c2 on OS8.6
by basicprinting＠earthlink.net July 30, 2001

July 30, 2001

The Official Jack Jansen MacPython Website still insists "There are no current beta distributions." #You might get more flies if you bother to bait the trap. Installation of MacPython 2.1.1c2 on OS8.6 went successfully. Most of the items in Mac:Lib:test failed, crashed, whatever All of the samples in Mac:Demo:waste suffered from 'zombie' windows that refuse to dissapear once you close them. Double-Click PythonInterpreterClassic and it whines: File "Net:Applications:Python 2.1.1:PythonInterpreterClassic", line 1 Joy!peffpwpc ^ SyntaxError: invalid syntax This is surprising to me, considering this machine is only running circa 8.6 code. (Excepting the 2.1.1c2 install) (True or False): A Mac without CarbonLib installed is considered Classic? (True or False): To run a Python interpreter on an non-carbon mac you run PythonInterpreterClassic? and what the heck is that icon on the Classic Interpreter? Double-Click PythonInterpreter and it launches successfully >>> import test.autotest 4 tests failed: test_longexp test_sha test_socket test_zlib many items were skipped because there were no modules named blah, & blah1, & blah2...

3 2

Help me waste some time?
by Richard Gordon July 29, 2001

July 29, 2001

In the course of cleaning out some forgotten folders, I came across a script that some guy posted to the MacPerl list a few years ago that was wonderfully irritating because it made the Mac yodel. To avoid doing what I was supposed to be doing, I started exploring the possibilities of converting this into macpython, but got stuck pretty quickly trying to find something that equates to the perl Speech module. I found some sound and soundmanager stuff, but couldn't find anything about speech as such and am fuzzy about where to begin. If someone could point me in the right direction, I'd appreciate it. The original script written in the High Martian that is perl is below. If you happen to have a copy of MacPerl around, it should play ok. #!perl # "MacPerl Yodels" v1.0 # by David Seay <g-s(a)navix.net> # use Mac::Speech; $channel[0] = NewSpeechChannel($Voice{'Cellos'}) or die $^E; $pitch1 = 68; $pitch2 = $pitch1 + 7; $pause = .05; for $note (0..7) { SetSpeechPitch $channel[0], $pitch1; SpeakText $channel[0], "a"; select(undef, undef, undef, $pause); SetSpeechPitch $channel[0], $pitch2; SpeakText $channel[0], "e"; select(undef, undef, undef, $pause); } SetSpeechPitch $channel[0], $pitch1 + 4; SpeakText $channel[0], "who"; while (SpeechBusy()) {} DisposeSpeechChannel $channel[0] if $channel[0]; Richard Gordon -------------------- Gordon Design Web Design/Database Development http://www.richardgordon.net

1 0

MacPython 2.1.1c2 available
by Jack Jansen July 28, 2001

July 28, 2001

Folks, there's a 2.1.1c2 installer available in http://www.cwi.nl/ftp/jack/python/mac/newer . I think this is complete, but please try it. And I mean that: the c1 installer was tested by exactly one person (at least, that's how much feedback I got), and there were serious problems with it (Python didn't work on MacOS 8, and the active installer was broken). I'd like to have some reasonable quality control on MacPython, but I can't do that without your help... As with the c1 installer: feedback from people using MacOS 8 and from people using non-western MacOS versions is especially solicited. -- 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/ ++++

5 4

Re: Syntax error bug in Python IDE
by Christopher Smith July 28, 2001

July 28, 2001

>In a new Python IDE editing window, type just 'return'. Then hit the >Run button. I get the following traceback: > >---------- >Traceback (most recent call last): > File "Manfred:Dev:Python 2.1:Mac:Tools:IDE:Wtraceback.py", line 41, >in traceback > self.syntaxerror() > File "Manfred:Dev:Python 2.1:Mac:Tools:IDE:Wtraceback.py", line 59, >in syntaxerror > charno = charno - 1 >TypeError: unsupported operand type(s) for - >---------- > >Of course, this should give a syntax error (try it in the Python >Interpreter window to see the correct traceback). But it seems the >charno variable isn't set right when the IDE wants to report the error. Oooh have I seen this recently. It happens when I do something like write f(i)=something when I should have written f[i]=something. I wish for a syntax error report in this situation, too. I'll try keep track of such an occurence that might help in debugging. /c

1 0

using IDLE and changing variables
by Christopher Smith July 28, 2001

July 28, 2001

Hi, One thing that has been discussed recently on Tutor is the fact that when you make changes to a module that you are importing, the changes won't be recognized unless you force a reload e.g., reload(mylibs). So the reload() takes care of that. My question concerns now the change of variables within a definition/program. Let's say at one point you had a variable x defined and you used it in several places. Then you change the variable from x to y but forget to change it everywhere. IDLE (at least from what I've seen) does not warn about the uninitialized variable. Is this just tough-luck-you-should-have-used-find-and-replace or is there some way to make sure this doesn't happen (other than quitting and restarting)? I guess what I'm looking for is something like BASIC's "new" command that flushes out everything of the session and begins fresh. /c

1 0

Syntax error bug in Python IDE
by Dean & Yang Draayer July 28, 2001

July 28, 2001

In a new Python IDE editing window, type just 'return'. Then hit the Run button. I get the following traceback: ---------- Traceback (most recent call last): File "Manfred:Dev:Python 2.1:Mac:Tools:IDE:Wtraceback.py", line 41, in traceback self.syntaxerror() File "Manfred:Dev:Python 2.1:Mac:Tools:IDE:Wtraceback.py", line 59, in syntaxerror charno = charno - 1 TypeError: unsupported operand type(s) for - ---------- Of course, this should give a syntax error (try it in the Python Interpreter window to see the correct traceback). But it seems the charno variable isn't set right when the IDE wants to report the error. Dean

1 0

diff
by kevin parks July 28, 2001

July 28, 2001

The best thing that i could find was in the "find differences" menu in BBedit. It is not in BBedit lite, only in the full version. Toast has a compare menu, but it only compares the items in a simple way, telling you if they are the same or not. In OS X (or at least on the NeXT) there used to be an app called page merger which was an IB examples app that was actually quite useful, but then if you were on OS X you'd have the UNIX diff going in the shell, i presume. cheers, -kp-- Get 250 color business cards for FREE! http://businesscards.lycos.com/vp/fastpath/

1 0

IDLE on Mac
by Christopher Smith July 27, 2001

July 27, 2001

Two things that I noticed in IDLE (2.1, not 2.1.1): 1) the shift-cmd-] adds a # to the line, but shift-cmd-[ doesn't remove it. Is there a way to remove the #'s? 2) is there a graceful way to just stop in the middle of your program. I've been using input() and when prompted just press return which brings up the error window which I then close. It's less than elegant. /c

1 0

Re: [Pythonmac-SIG] Bug in Lib/EasyDialogs.py
by Jack Jansen July 27, 2001

July 27, 2001

> I found a bug in EasyDialogs in Python 2.1: > > Line 280 in EasyDialogs.py (method "_update" in the > class "ProgressBar") is wrong: > > self.d.DragWindow(where, screenbounds) > > It should be: > > self.w.DragWindow(where, screenbounds) > > This bug produces an error when you try to move a > ProgressBar window. Thanks! I've put the fix in the repository. > P.S. I reported this bug to jack(a)cwi.nl but I have > checked that the bug continues in the SourceForge CVS > repository. Oops... I don't remember seeing the message, so I guess it came by at an inopportune moment, sorry... -- 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

1 0