Comment #10 on issue 1641 by smichr: doctests require newline only when run  
for single file
http://code.google.com/p/sympy/issues/detail?id=1641

An additional clarification: those function decorated with @vectorize() do  
not have
their doctests run when the tests are initiated from the command line:

python.exe bin/doctest core/function.p

These tests are also not run when intiated from the command line:

>>> import sympy
>>> sympy.doctest('core/function.py')

I tested this by deliberately doubling a closing paren in one of def  
diff()'s
docstring tests. In neither case was an error raised with the def diff() was
decorated with @vectrize. If I commented out the decoration then the error  
was flagged.

This is in contrast to how python's docstring behaves. In comment 4 above I  
said that
the interpreter caught the vectorized functions...if you look at how I ran  
it in the
interpreter you will see that I was running python's doctest not sympy's  
doctest.

SO....here are the issues (on Windows):

1) @vectorize'ed functions are skipped no matter how the sympy doctest is  
initiated
2) the results can vary if the tests are done after an "import sympy"  
versus "from
sympy import *"

The newline issue does not seem to be raised (with my runtest branch) from  
either the
command line nor the interpreter. I have seen the error, however...I'll try  
pay
attention to when it starts happening.

/c

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"sympy-issues" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/sympy-issues?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to