>> I'm using Windows XP, using IDLE (which was mentioned already)
> in the context of editing/displaying code, not executing it. Does the
> problem occur before or after you edit a file with IDLE?
Actually, neither. I'm not editing the code. I open it in IDLE in 2.5
and attempt to run it through
On Jan 5, 8:05 am, [EMAIL PROTECTED] wrote:
> On Jan 4, 2:06 pm, John Machin <[EMAIL PROTECTED]> wrote:
>
> > On Jan 5, 3:56 am, [EMAIL PROTECTED] wrote:
>
> > > Hi,
>
> > > When Python 2.5 first came out, I eagerly downloaded it and
> > > immediately had issues with getting it to run my 2.4 code.
On Jan 4, 2:06 pm, John Machin <[EMAIL PROTECTED]> wrote:
> On Jan 5, 3:56 am, [EMAIL PROTECTED] wrote:
>
> > Hi,
>
> > When Python 2.5 first came out, I eagerly downloaded it and
> > immediately had issues with getting it to run my 2.4 code. So I just
> > stuck to 2.4. However, I decided this week
On Jan 5, 3:56 am, [EMAIL PROTECTED] wrote:
> Hi,
>
> When Python 2.5 first came out, I eagerly downloaded it and
> immediately had issues with getting it to run my 2.4 code. So I just
> stuck to 2.4. However, I decided this week that I really should try to
> get 2.5 to work. Does anyone know why c
