How do you develop in Python?

[Louis M. Pecora]

[[ This message was both posted and mailed: see
   the "To," "Cc," and "Newsgroups" headers for details. ]]

In article <9fjfer$gt0$1 at nereid.worldonline.nl>, Gerrit Muller
<gmuller at worldonline.nl> wrote:

> "Lou Pecora" <pecora at anvil.nrl.navy.mil> schreef in bericht
> news:050620011516094693%pecora at anvil.nrl.navy.mil...
> > I program in Python occassionally and would like to do more of it.  But
> > here's a development conundrum I run into a lot (there are more complex
> > examples, but I'll give an easy one).  I am developing module A.py
> > which imports B.py in the IDE.  I am running test code which is also in
> > A.py as I incrementally develop A.py.  Then I need to change B.py and,
> > of course, the import does not import the new changes since import only
> > works once.  Hence,  to "refresh" B.py I have to quit the IDE and
> > restart, open A.py and run.  This is clumsy.  However, the above
> > scenario is not uncommon and more complex interdependencies of modules
> > appear to make it unavoidable.  Anyone know a way to get around this
> > "import" problem?   I know there is a "reload", but then I have to
> > import and change my modules' code to "reload" or something each time I
> > work with them.  Any help appreciated.
> >
> > I use Python on a Macintosh.  Nice IDE, otherwise.
> 
> I certainly recognize your problem. Occasionaly I have used reload() to
> "solve" this behavior. However for more "naive" programmers (CP4E-like) this
> behavior can give many unexpected results. I do recognize the power of the
> current dynamic loader behavior, but I think that a more "cold" runscript
> command in IDLE, which imports/reloads anything again (and maybe clears the
> rest of the environment as well) would make IDLE even more accessible for
> this type of programmers.
> 
> Regards Gerrit

Good point.  I agree.