On 1 Apr., 08:43, Simon King simon.k...@uni-jena.de wrote:
...
It states that this may depend on possible previous computations. Is
there really no work around? Such as, using an object that is not
considered in any other doc test? Is the new result correct? Shouldn't
both tests better be
On 2 Apr., 08:39, Simon King simon.k...@uni-jena.de wrote:
On 1 Apr., 08:43, Simon King simon.k...@uni-jena.de wrote:
...
It states that this may depend on possible previous computations. Is
there really no work around? Such as, using an object that is not
considered in any other doc
On Sat, Apr 02, 2011 at 12:12:09AM -0700, Simon King wrote:
It states that this may depend on possible previous computations. Is
there really no work around? Such as, using an object that is not
considered in any other doc test? Is the new result correct? Shouldn't
both tests better be
Hi Nicolas,
On 2 Apr., 18:31, Nicolas M. Thiery nicolas.thi...@u-psud.fr
wrote:
Well, I guess the right thing to do would be to change the doctest to
not show the full cache of this function, but only those pieces that
should be there at this point. Do you feel comfortable doing it, or
would