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 
pass, but they all include a "from bla import factory" statement in them. 
So, someone knew to put those import statements in in order for the tests 
to pass.

As for being in the Sage library: I have it set up the way we did at 
overconvergent sage days: there are symbolic links in the sage directory to 
the files, so I think that means that they "are" in the sage library (but 
maybe I'm wrong and maybe this is the problem). 

I've been meaning to write a smaller testcase, but haven't had the time yet.

Thanks,

Rob

On Monday, April 22, 2013 4:15:13 PM UTC-5, David Roe wrote:
>
> 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:34 AM, Rob H. <robert...@gmail.com <javascript:>
> > wrote:
>
>> 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 
>> including the factory in the system by which sage loads a bunch of things 
>> into the global namespace). So, I just added the command "from ... import 
>> MFactory" to the beginning of the doctests that weren't working and all the 
>> doctests are now happy. This seems like a bug in the doctesting, no? The 
>> doctesting is creating its own separate instance of the factory.
>>
>> Rob
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to sage-devel+...@googlegroups.com <javascript:>.
>> To post to this group, send email to sage-...@googlegroups.com<javascript:>
>> .
>> Visit this group at http://groups.google.com/group/sage-devel?hl=en.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to