As a quick example (that is not minimal), you can go to your (David) OMS
repository (https://github.com/roed314/OMS). I just pushed a change that
adds a failing doctest to sage/modular/pollack_stevens/distributions.py .
Note that there are doctests in that file that run the TestSuite and they
p
Are these files in the Sage library? If not, the doctesting code executes
the file, thus overwriting the factory. But it should be done before
calling anything, so I wouldn't think it would cause this problem. As
Volker says, can you post a testcase somewhere?
David
On Mon, Apr 22, 2013 at 9:3
I figured out what the difference was between the class that works and the
one that doesn't: nothing! The only difference is that for the class that
works I had a leftover "from ... import WorkingFactory" statement at the
beginning of my doctest (leftover in that I had put it there before
inclu
Do you have some minimal testcase? Its hard to say anything for sure
without some code. If your class does complicated things it is sometimes
necessary to implement __reduce__, though.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscri
Addendum: re the "last paragraph" (which begins with "Now, here's one
thing"), it's not just m and loads(dumps(m)) that have different types, but
also the factories that produce them. That certainly explains why m is not
loads(dumps(m)), but isn't it a bug in the doctesting?
On Sunday, April 21
