doctest x idle problem?

[Steve Holden]

"Jon Schull" <jonschull at yahoo.com> wrote in message
news:b8c015b9.0107271956.3661a8a0 at posting.google.com...
> "Tim Peters" <tim.one at home.com> wrote in message
> > ...I have no idea why you're doing "Run Script" on doctest to begin
> > with.  That's not a sensible thing to do -- doctest is a library module
in
> > 2.1, and you shouldn't need to load it into IDLE at all, let alone ever
run
> > it on itself.
> >
>
> Well, I was hoping to develop and test some modules within the idle
> environment.  (I'm wondering how well IDLE serves as a primary
> Interactive Development Environment.)
>
> I ran into this "problem" (it's not unique to doctest) and thought I
> was doing something wrong.  I figured doctest's use of docstrings for
> testing would be exemplary, so I tried doctest.
>
> In a way, doctest *was* exemplary...
>
> But it seems that its going to be awkward to do interactive
> development in IDLE of modules that employ doctest.  That seems a
> shame; routine use of doctest and IDLE would be a good practice.

Well, it really doesn't seem excessively demanding to test in a separate
process when you want to run doctest. Surely you don't do that except when
you want to be sure you have a stable new version which is compatible (as
dictated by regression tests) with the previous one?

regards
 Steve
--
http://www.holdenweb.com/