From glingl at aon.at  Fri Aug  4 15:38:37 2006
From: glingl at aon.at (Gregor Lingl)
Date: Fri, 04 Aug 2006 15:38:37 +0200
Subject: [Idle-dev] Why: IDLE internal error?
Message-ID: <44D34DDD.50506@aon.at>

Hi,
 Running IDLE1.2 I get the usual Error messages, e.g.

IDLE 1.2b3     
 >>> name

Traceback (most recent call last):
  File "<pyshell#0>", line 1, in <module>
    name
NameError: name 'name' is not defined
 >>>

When running IDLE in -n mode I get:

IDLE 1.2b3      ==== No Subprocess ====
 >>> name
IDLE internal error in runcode()
Traceback (most recent call last):
  File "<pyshell#0>", line 1, in <module>
    name
NameError: name 'name' is not defined
 >>>

This form does occur not only in the Shell but also
when executing a script (which contains an error).

(1) Why does this additional line

IDLE internal error in runcode()

occur?

(2) What does it mean? (Are there important
conclusions I have to draw from it?)
(3) Under which other circumstances does it occur?

Regards,
Gregor
 



From kbk at shore.net  Wed Aug  9 20:31:51 2006
From: kbk at shore.net (Kurt B. Kaiser)
Date: Wed, 09 Aug 2006 14:31:51 -0400
Subject: [Idle-dev] Why: IDLE internal error?
In-Reply-To: <44D34DDD.50506@aon.at> (Gregor Lingl's message of "Fri, 04 Aug
	2006 15:38:37 +0200")
References: <44D34DDD.50506@aon.at>
Message-ID: <871wrpn4ko.fsf@hydra.bayview.thirdcreek.com>

Gregor Lingl <glingl at aon.at> writes:

> (1) Why does this additional line
>
> IDLE internal error in runcode()
>
> occur?
>
> (2) What does it mean? (Are there important
> conclusions I have to draw from it?)
> (3) Under which other circumstances does it occur?

The message was intended to draw attention to IDLE internal errors.  But
as you noted, it appeared before all exceptions when running without the
subprocess.  I have corrected that, it no longer appears when running
w/o the subprocess.  In that mode, it's not possible to separate IDLE
exceptions from user code exceptions.

-- 
KBK

From kbk at shore.net  Thu Aug 10 19:23:27 2006
From: kbk at shore.net (Kurt B. Kaiser)
Date: Thu, 10 Aug 2006 13:23:27 -0400
Subject: [Idle-dev] A possible bug in IDLE 1.2b2
In-Reply-To: <7afdee2f0607300108y2e13115fnd801a1c0cd7b4e5@mail.gmail.com> (Tal
	Einat's message of "Sun, 30 Jul 2006 11:08:31 +0300")
References: <20060729072747.91624.qmail@web38915.mail.mud.yahoo.com>
	<7afdee2f0607300108y2e13115fnd801a1c0cd7b4e5@mail.gmail.com>
Message-ID: <87vep0ld2o.fsf@hydra.bayview.thirdcreek.com>

"Tal Einat" <taleinat at gmail.com> writes:

> Several days ago I submitted a patch which addresses this issue: SF patch
> 1528468<http://sourceforge.net/tracker/index.php?func=detail&aid=1528468&group_id=5470&atid=305470>
> .
>
> This will probably be included in Python 2.6.

I decided to push this back to 2.5c1, it's a bug raised in 2.5a1 which should be fixed.

Thanks for the patch!   And thanks for the reports on the problem.

-- 
KBK