constructive critisism on pythonwin IDE

Kragen Sitaker kragen at pobox.com
Sun Jun 9 04:07:30 CEST 2002


Chris Barker <Chris.Barker at noaa.gov> writes:
> > sameer wrote:
> > > The thing I hate about PythonWin
> > > is, that despite the fact that it's a development environment, there
> > > is a lot of caching done of modules, and the cached copy is not
> > > checked against a potentialy modified copy.  Whenever I change the
> > > contents of a file and try to run a module that depends on that file,
> > > I always end up with the old copy.  I have to then import and then
> > > reload the changed module in the interactive window for it to refresh.
> 
> This is how Python works, it's not anything specific to PythonWin. It
> works this way because a given module might be imported dozens of times
> in a given Python program, and you would want that to be done fresh each
> time.

                                    VVV
I think you might mean, "you would *not* want that to be done fresh".
                                    ^^^
Is that right?




More information about the Python-list mailing list