From noreply at sourceforge.net Sat Oct 4 18:42:23 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Sun Oct 5 01:23:52 2003 Subject: [Idle-dev] [ idlefork-Bugs-817898 ] Threads and output Message-ID: Bugs item #817898, was opened at 2003-10-05 00:42 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109579&aid=817898&group_id=9579 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Noam Raphael (noamr) Assigned to: Nobody/Anonymous (nobody) Summary: Threads and output Initial Comment: Hello, If a thread writes output (into sys.stdin) while a command should be executed, the command you tried to execute never finishes executing, so you are stuck. For example, type this: >>> from threading import Thread >>> def f(): for i in range(200): print i, >>> t = Thread(target=f) >>> t.start() Now, while the numbers are showing, type Enter. After the numbers stopped showing, you'll notive that you can't execute anything, until you restart the shell. I noticed this because I wrote a function which executes at a seperate thread and writes to sys.stderr. If I try to execute something while the output is being printed, I get stuck. Bye, Noam ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109579&aid=817898&group_id=9579 From noreply at sourceforge.net Thu Oct 16 02:33:09 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Oct 16 02:33:18 2003 Subject: [Idle-dev] [ idlefork-Bugs-824595 ] filename .idlerc crashes windows98 Message-ID: Bugs item #824595, was opened at 2003-10-15 23:33 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109579&aid=824595&group_id=9579 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: filename .idlerc crashes windows98 Initial Comment: Windows 98 crashes in horrible ways when filenames start with a dot. Even deleting the file is difficult! Crashes take place at totally unexpected moments, without any idle activity. Apparently the filesystem crashes when it gives the wrong interpretation to the starting dot. The file .idlerc should be renamed in something without a dot, for instance typical windows would be idle.ini Any name without a starting dot is OK. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109579&aid=824595&group_id=9579 From noreply at sourceforge.net Thu Oct 16 02:33:58 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Oct 16 02:34:00 2003 Subject: [Idle-dev] [ idlefork-Bugs-824595 ] filename .idlerc crashes windows98 Message-ID: Bugs item #824595, was opened at 2003-10-15 23:33 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109579&aid=824595&group_id=9579 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: filename .idlerc crashes windows98 Initial Comment: Windows 98 crashes in horrible ways when filenames start with a dot. Even deleting the file is difficult! Crashes take place at totally unexpected moments, without any idle activity. Apparently the filesystem crashes when it gives the wrong interpretation to the starting dot. The file .idlerc should be renamed in something without a dot, for instance typical windows would be idle.ini Any name without a starting dot is OK. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-10-15 23:33 Message: Logged In: NO e-mail address of submitter: gerrit.muller@embeddedsystems.nl ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109579&aid=824595&group_id=9579 From noreply at sourceforge.net Thu Oct 16 11:09:05 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Thu Oct 16 11:09:13 2003 Subject: [Idle-dev] [ idlefork-Bugs-824595 ] filename .idlerc crashes windows98 Message-ID: Bugs item #824595, was opened at 2003-10-16 02:33 Message generated for change (Comment added) made by gvanrossum You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109579&aid=824595&group_id=9579 Category: None Group: None Status: Open >Resolution: Works For Me >Priority: 1 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: filename .idlerc crashes windows98 Initial Comment: Windows 98 crashes in horrible ways when filenames start with a dot. Even deleting the file is difficult! Crashes take place at totally unexpected moments, without any idle activity. Apparently the filesystem crashes when it gives the wrong interpretation to the starting dot. The file .idlerc should be renamed in something without a dot, for instance typical windows would be idle.ini Any name without a starting dot is OK. ---------------------------------------------------------------------- >Comment By: Guido van Rossum (gvanrossum) Date: 2003-10-16 11:09 Message: Logged In: YES user_id=6380 We need to know more about how your system was configured. Do you have a network filesystem or something like that? Virus scanner tools installed? I'm asking because I have used IDLE with this file without trouble for years on my own win98 box, so I doubt that it's win98 itself that causes the crashes. Filenames of this form have always been legal in win98. But some other software you've installed may be buggy. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-10-16 02:33 Message: Logged In: NO e-mail address of submitter: gerrit.muller@embeddedsystems.nl ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109579&aid=824595&group_id=9579 From noreply at sourceforge.net Fri Oct 17 21:11:32 2003 From: noreply at sourceforge.net (SourceForge.net) Date: Fri Oct 17 21:11:52 2003 Subject: [Idle-dev] [ idlefork-Bugs-824595 ] filename .idlerc crashes windows98 Message-ID: Bugs item #824595, was opened at 2003-10-16 01:33 Message generated for change (Comment added) made by kbk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109579&aid=824595&group_id=9579 Category: None Group: None Status: Open Resolution: Works For Me Priority: 1 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: filename .idlerc crashes windows98 Initial Comment: Windows 98 crashes in horrible ways when filenames start with a dot. Even deleting the file is difficult! Crashes take place at totally unexpected moments, without any idle activity. Apparently the filesystem crashes when it gives the wrong interpretation to the starting dot. The file .idlerc should be renamed in something without a dot, for instance typical windows would be idle.ini Any name without a starting dot is OK. ---------------------------------------------------------------------- >Comment By: Kurt B. Kaiser (kbk) Date: 2003-10-17 20:11 Message: Logged In: YES user_id=149084 Duplocate of #678343 originally submitted 31Jan2003. Cllosed as 'works for me' on 05Sep2003. I have also been using IDLE and IDLEfork on W98 without problems. It's unlikely that a crash when not accessing the file system can be caused by a filename. Are you the same person who submitted the previous bug? ---------------------------------------------------------------------- Comment By: Guido van Rossum (gvanrossum) Date: 2003-10-16 10:09 Message: Logged In: YES user_id=6380 We need to know more about how your system was configured. Do you have a network filesystem or something like that? Virus scanner tools installed? I'm asking because I have used IDLE with this file without trouble for years on my own win98 box, so I doubt that it's win98 itself that causes the crashes. Filenames of this form have always been legal in win98. But some other software you've installed may be buggy. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-10-16 01:33 Message: Logged In: NO e-mail address of submitter: gerrit.muller@embeddedsystems.nl ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=109579&aid=824595&group_id=9579 From p.magwene at snet.net Tue Oct 21 13:45:48 2003 From: p.magwene at snet.net (Paul M) Date: Tue Oct 21 13:56:47 2003 Subject: [Idle-dev] IDLE, ps2, and doctest Message-ID: <3F9570CC.9000401@snet.net> [also posted to comp.lang.python] Pythoneers, IDLE doesn't use the ps2 prompt ("..." in the command line interpreter) because it supports multiline editing. This issue has been discussed before, for example see Guido's explanation in this thread: http://mail.python.org/pipermail/idle-dev/2002-February/000863.html Unfortunately the lack of the ps2 prompt makes IDLE inappropriate for writing multi-line routines that can be used in doctest readable docstrings: As an example, doctest want's something like this: >>> for each in cuppertri: ... if each >= 0.0: ... ct += 1 ... >>> Whereas IDLE gives this: >>> for each in cuppertri: if each >= 0.0: ct += 1 >>> Doctest kept failing on text I cut-and-pasted from IDLE and it took me a good 15 minutes to figure out what was going on. Has anybody else run into this problem? The "solution" of course is to revert to the command line when including examples in docstrings, but then you lose all the convenience of the IDLE environment.... Would it be possible to have the option of including the ps2 prompt in IDLE? Alternately, can anybody think of a clever way to get doctest to recognize text pasted from IDLE (I've looked at the doctest.py source myself but wasn't able to come up with a non-ugly solution). Thanks, Paul Magwene