PythonWin IDE sucks!

Dale Strickland-Clark dale at out-think.NOSPAMco.uk
Sat Oct 28 04:52:14 EDT 2000


"Prateep Siamwalla" <teep at inet.co.th> wrote:

>Dale,
>
>Since I didn't catch the beginning of this thread, I'm assuming you are
>talking about how after a reload(module), and you run your tests on the
>interactive window, Python still manages to catch your old code errors.
>Even after editting the offending code and reloading.
>
>I've been there before, and as a novice, all I can offer you is this:
>1. After making changes/correction on the offending module, click the "run"
>while that module's window is active.
>2. Then go back into the interactive module and do the reload.
>3. Try your tests again.
>
>this seems to work for me.
>
><novice speculation>
>I think what happens is that the offending bits of your code are still stuck
>inside .pyc files which, is the one that is reloaded from your interactive
>prompt.  By clicking "run" on your module, you forcefully overwrite the
>module's pyc file with your new code, so that the next reload is of the
>newly editted code.
></novice speculation>
>
>Hope this helps,
>teep
>
Thanks. I'll give it a try.
--
Dale Strickland-Clark
Out-Think Ltd
Business Technology Consultants





More information about the Python-list mailing list