[sage-devel] Re: Which docstrings should be doctested

2013-05-09 Thread Simon King
On 2013-05-09, leif wrote: > Simon King wrote: >> PS: >> >> On 2013-05-09, Simon King wrote: >>> The disadvantage of this approach: It will only test stuff that can be >>> imported by Python---cdef methods do not appear in dir(O). >> >> And the worse disadvantage: This will only test importable m

[sage-devel] Re: Which docstrings should be doctested

2013-05-09 Thread leif
Simon King wrote: PS: On 2013-05-09, Simon King wrote: The disadvantage of this approach: It will only test stuff that can be imported by Python---cdef methods do not appear in dir(O). And the worse disadvantage: This will only test importable modules. It will not test files. Well, you jus

[sage-devel] Re: Which docstrings should be doctested

2013-05-08 Thread Simon King
PS: On 2013-05-09, Simon King wrote: > The disadvantage of this approach: It will only test stuff that can be > imported by Python---cdef methods do not appear in dir(O). And the worse disadvantage: This will only test importable modules. It will not test files. -- You received this message be

[sage-devel] Re: Which docstrings should be doctested

2013-05-08 Thread Simon King
Hi! On 2013-05-08, Nicolas M. Thiery wrote: > I just made some tests (see attached file). Clearly Python uses > introspection. In spkg-check of my group cohomology spkg, I use the following basic approach, also relying on introspection: 1. Start with a list of items (initially: The modules of t

[sage-devel] Re: Which docstrings should be doctested

2013-05-08 Thread Travis Scrimshaw
Hey, Also I'd also like to add that things like class Foo: __doc__ = \ """ EXAMPLES:: sage: 1/0 """ are not tested (which is why anything in a global options documentation is not being tested). Best, Travis -- You received this message because you are subscribed to