moohaad / pyscripter

Automatically exported from code.google.com/p/pyscripter
0 stars 0 forks source link

Module changes not reflected in the main script #231

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. load a module in a main script
2. run the main script by printing a variable of the module
3. change the variable in the module and save it
4. run the main script again

What is the expected output? What do you see instead?
The changed variable should be visible from the main script. Instead you
see the old value.

What version of the product are you using? On what operating system?
PyScripter 1.9.9.2 on Win Vista. I experienced the same on Win XP or Win
Server 2003. 

Please provide any additional information below.
An older version of PyScripter (1.7.2.0) doesn't show this problem.

Original issue reported on code.google.com by r...@uni-freiburg.de on 16 Jun 2008 at 9:47

GoogleCodeExporter commented 9 years ago
Changes to the main module should take effect in a new run. To make sure that 
changes
in files imported by the main module are taking effect in a new run the best 
way is
to use the remote interpreter
(http://pyscripter.googlepages.com/remotepythonengines) and reinitialize before 
each
run.  The new Run Configurations that can be created in the Project Explorer 
allow
you to automatically reinitialize before each run.

Alternatively, you can manually reload the changed modules. This can also be 
done
using the Run, Import command. 

There have been quite a few discussions on this topic at
http://groups.google.com/group/PyScripter?hl=en.

Original comment by pyscripter on 17 Jun 2008 at 3:36

GoogleCodeExporter commented 9 years ago

Original comment by pyscripter on 31 Jul 2010 at 11:23