Bugs item #1206232, was opened at 2005-05-21 12:46 Message generated for change (Comment added) made by kbk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1206232&group_id=5470
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: IDLE Group: Python 2.3 >Status: Closed >Resolution: Wont Fix Priority: 5 Submitted By: Torsten Bronger (bronger) >Assigned to: Kurt B. Kaiser (kbk) Summary: IDLE 1.0.5 (Python 2.3.5) crashes under Windows Initial Comment: Using Win2k or XP, IDLE 1.0.5 and Python 2.3.5, the attached source produces a fatal error and IDLE and the Python Shell are closed. In order to reproduce the issue, start IDLE, open the attached file and press "F5". ---------------------------------------------------------------------- >Comment By: Kurt B. Kaiser (kbk) Date: 2005-06-05 01:02 Message: Logged In: YES user_id=149084 Probably not worth fixing in 2.3 branch at this point. ---------------------------------------------------------------------- Comment By: Torsten Bronger (bronger) Date: 2005-05-26 15:26 Message: Logged In: YES user_id=442234 Oops, I think I should add my further findings nevertheless: It was indeed the hex constants and their implicit conversion to signed values. An attached "L" solved the problem. Could it be that the warning messages cause possible errors with IDLE on Windows? With Linux, I see those "future warnings" on the console when I try to import my file. With IDLE, these things are supressed, of course. 2.4 doesn't show warnings, too. ---------------------------------------------------------------------- Comment By: Torsten Bronger (bronger) Date: 2005-05-26 15:20 Message: Logged In: YES user_id=442234 No, I had tested it also with 2.4.x and had no problem. I didn't know whether there would be another 2.3.x, so I submitted it. In case the 2.3 branch is closed, do the same with this bug. ;) ---------------------------------------------------------------------- Comment By: Terry J. Reedy (tjreedy) Date: 2005-05-26 11:23 Message: Logged In: YES user_id=593130 Does this still happen with 2.4.1 and the corresponding IDLE? Besides numerous bug fixes, I believe 2.4 changed the interpretation of unsigned hex constants from sometimes negative to always positive. From a glance at your file, this seems likely relevant. If you also find a bug with current Python/IDLE, please reduce your file to the minimum necessary to produce the bug. Also include the error message and traceback you get. (As far as I know, there is currently no prospect of a 2.3.6, but there should at least be a 2.4.2) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1206232&group_id=5470 _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
