Bug? PyScripter using old version of file, even though it was updated and saved

[GoogleCodeExporter]

I'm having a small problem which I think might be some sort of bug:

Portable Python 1.1 based on Python 2.6.1 "installed" on a sandisk
cruzer 2gb pen drive (disk on key/flash drive).
Connected to XP machine.

using PyScripter, I opened multiple files via:
"File > Open" and selected multiple files

script_a imports script_b
I run script_a which errors because of a function in script_b
I fix the function in script_b and run script_a
it still errors out (even though the file has been saved).
If I save all scripts, close pyscripter and open it again (script_b
has the corection I made) it works fine and uses the new version of
script_b.

This is very weird... Looks to me like the import function isn't
working properly (using data from a cache of some sort?)

Let me know if you need more info... the problem is definitely
reproducible!

-Leav

P.S.
Portable Python developer dude indicated that it's not on his end... 

Original issue reported on code.google.com by lea...@gmail.com on 24 Nov 2009 at 10:26

• Merged into: Seems like pyscripter 1.9.9.2 is not picking up code changes #256

[GoogleCodeExporter]

Sorry, forgot to indicate I was using version 1.9.9.6

I'll download the latest version and verify.

Original comment by lea...@gmail.com on 24 Nov 2009 at 10:30

[GoogleCodeExporter]

Yup, still happens with version 1.9.9.7

Seems unlikely to me that such a bug would creep so far into development... I'm 
much
more inclined to think it has something to do with how I'm doing things - but 
since
this was the behaviour out of the box... not sure what to think.

Original comment by lea...@gmail.com on 24 Nov 2009 at 10:57

[GoogleCodeExporter]

I can confirm this behaviour (I'm on a clean install of 1.9.9.7).
It has been present for some time (made me switch away from pyScripter, but I 
forgot
why ;-))

This makes multi-module projects a pain to work with...

Original comment by michael.bech.hansen@gmail.com on 23 Dec 2009 at 11:54

[GoogleCodeExporter]

a workaround is to use the rpyc external python engine and to restart the engine
(ctrl+f2) after every change...

I would have already switched to something else, but I really like the debugger 
in
pyscripter...

please fix this soon... this is annoying!!!

Original comment by lea...@gmail.com on 23 Dec 2009 at 12:23

[GoogleCodeExporter]

I also see this issue.
Seems OK if only editing without running in pyscipter.

Original comment by unicor...@gmail.com on 25 Dec 2009 at 7:51

[GoogleCodeExporter]

Original comment by pyscripter on 2 Jan 2010 at 4:45

• Changed state: Duplicate