Stale code/objects between runs

[GoogleCodeExporter]

What steps will reproduce the problem?
Debug a program a several times, making changes to different modules between 
runs, especially introducing and removing errors.

What is the expected output? What do you see instead?
Each run should be running the latest code with fresh objects, not a stale 
version that no longer exists.

For example, I had a class constructor calling a method with a typo in the name 
but no matter what edits I made, I couldn't get it to stop trying to call the 
old version with the typo.

What version of the product are you using?
2.5.3.0

Please provide any additional information below.
Changing the engine from internal to remote fixes the problem temporarily.
Restarting PyScripter fixes the problem temporarily.

Original issue reported on code.google.com by ar1083...@gmail.com on 3 Dec 2012 at 12:45

[GoogleCodeExporter]

Hi,
I got the same problem on latest version (2.5.3.0 *64 Windows7) but not before. 
Modification in source file is not take in account by debugger.
I have to restart PyScripter and every thing works correctly until next modif. 
It's look like if during first debug session, context is saved and not reset 
for the second one.

Many thanks if somebody has an idea.
Frederic

Original comment by berger.f...@gmail.com on 21 Jan 2014 at 10:00

[GoogleCodeExporter]

Please use the remote python engine, which for some time has beeen the default 
and strongly recommended to avoid the issues you describe.  Run, Python engine 
remote.   See https://code.google.com/p/pyscripter/wiki/RemoteEngine for more 
info.  The remote engine is reinitialized before each run (default IDE option), 
so you have a fresh Python environment in every script run.

Original comment by pyscripter on 28 Mar 2015 at 7:39

• Changed state: As-Designed