[Pythonmac-SIG] MacPython IDE -- Is this a bug?

Schollnick, Benjamin Benjamin.Schollnick@usa.xerox.com
Wed, 20 Mar 2002 11:26:22 -0500


Opps...

Missed the "IDE" part....

I don't use the Mac IDE....  I use IDLE on the PC, but I haven't
checked to see if it'll work on the Mac...

(Does anyone know if the IDLE fork is usable on the Mac?  The Mac
IDE is nice, but I prefer the color syntaxing, etc, that is in 
IDLE...)

		- Benjamin


-----Original Message-----
From: Schollnick, Benjamin 
Sent: Tuesday, March 19, 2002 1:27 PM
To: 'Bruce Robbins'; pythonmac-sig@python.org
Subject: RE: [Pythonmac-SIG] MacPython IDE -- Is this a bug?
Importance: High


You can fix, I presume...

Turn off the Caching of the MacPython display...

		- Benjamin

-----Original Message-----
From: Bruce Robbins [mailto:brobbins333@shaw.ca]
Sent: Tuesday, March 19, 2002 1:22 PM
To: pythonmac-sig@python.org
Subject: [Pythonmac-SIG] MacPython IDE -- Is this a bug?


This runs as expected as a script in the PythonWin IDE, so I guess there
would be
disagreement whether it constitutes a "bug." If I were the author of the
MacPython IDE,
I think I would try to fix it.

BR

On Mon, 18 Mar 2002, Bruce Robbins wrote:

> Try running this AS A SCRIPT in the MacPython IDE v.1.0.1:
>
> list = [33, 44, 55, 66]
>
> for each in list:
>   print each,
>
>
> Make sure you include the comma after the print each statement.
> Then try it without the comma.
>
> No output in the output window when run with the comma -- until
> the script is run again without the comma!
>

  If you append either:


print

  or

import sys; sys.stdout.flush()


  after your two lines above, you'll get the output. (The first with a
  trailing newline, the latter without.)

  I'm guessing that sys.stdout.close() would also work, but wouldn't
  be very useful to you.

  That should make the reason for the behaviour obvious.
  ( You don't get it in the interpreter window, because the line gets
    flushed when it prints out a '>>>' prompt for the next input line.)

  Is it a bug?
  I'ld vote no -- it matches exactly what would happen if you had a
  script writing to a file, or executed a script on the unix command line
  (so you wouldn't get any prompts to the terminal) except that sys.stdout
  would get flushed and closed at program termination.


-- Steve Majewski




_______________________________________________
Pythonmac-SIG maillist  -  Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig