Internal engine does not reset and reload modules on each run

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Choose options for internal engine execution

2.Enter this program
import string

print(string.punctuation)
string.punctuation = 'abc'
print(string.punctuation)

3. Run it twice. 

What is the expected output? What do you see instead?
Expect 
*** Python 3.1.3 (r313:86834, Nov 27 2010, 18:30:53) [MSC v.1500 32 bit 
(Intel)] on win32. ***
>>> 
!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~
abc
>>>

*** Python 3.1.3 (r313:86834, Nov 27 2010, 18:30:53) [MSC v.1500 32 bit 
(Intel)] on win32. ***
>>> 
!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~
abc
>>>

but on the second run I get

>>>
abc
abc
>>>

What version of the product are you using? On what operating system?

PyScripter 2.4.3.0, python version shown above, Windows 7.

Please provide any additional information below.

I don't usually use the internal engine so this was my mistake that I do not 
require a fix for.  However, I think PyScripter would be a more stable product 
if the internal engine was not ever made available for users to execute their 
scripts.  Crashing the internal engine or doing stupid things like I did here 
can destabilize PyScripter.   

Original issue reported on code.google.com by cspwc...@gmail.com on 9 Feb 2012 at 6:35

[GoogleCodeExporter]

This a documented behavior and the help file and FAQ says clearly that the 
remote engine (which is the default) should be used in all circumstances.  By 
default also the remote engine is reinitialized before each run to avoid the 
issue you describe.

The correct title for this issue is "Hide completely the internal engine from 
the users" and that is something I would be inclined to consider.  I am closing 
this issue and if you want resubmit another issue with the suggested title or 
something similar.

Original comment by pyscripter on 9 Feb 2012 at 1:18

• Changed state: As-Designed