On 6/8/13, Ethan Furman <et...@stoneleaf.us> wrote:
> On 06/08/2013 03:09 AM, Serhiy Storchaka wrote:
>> 08.06.13 11:47, Ethan Furman написав(ла):
[...]
>
> Fair point. But I suppose that if the end-user is running a doc test, it is
> not too much to require that the other
> tests be installed as well. Plus, we definitely have the other tests. :)
>
>
>> Is it possible to add "invisible" code which doesn't displayed in the
>> resulting documentation, but taken into account by
>> doctest?
>
> I have no idea. This is my first time using doctest.
>
<ot>
No ... if using doctest . To get such things done you'll need
something like dutest [1]_ [2]_ , but that's not an option for testing
docs in stdlib .
</ot>
.. [1] dutest @ PyPI
(https://pypi.python.org/pypi/dutest)
.. [2] Purpose of Doctests [Was: Best practices for Enum]
(http://goo.gl/F7Afy)
--
Regards,
Olemis.
Apache™ Bloodhound contributor
http://issues.apache.org/bloodhound
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
