Dear Sage support,
I am a bit puzzled since very similar things worked in the past.
- I have a Cython extension module in a package that is installed in
SAGE_LOCAL/lib/python2.5/site-packages/ and can be imported when
starting sage, doing
sage: from pGroupCohomology import mtx
- I want to test the corresponding mtx.pyx
- Doing
sage -t -long -optional mtx.pyx
in the directory where mtx.pyx sits failed badly!
The errors that I get have nothing to do with the doc tests.
Apparently, when doing sage -t ... mtx.pyx, it is tried to compile
mtx.pyx, which fails since the compilation depends on external C-
sources.
Why is it attempted to compile? I thought that sage -t just scans the
file for doc tests?
Note that things worked in the past, when I had the following:
- mtx.so was in the current directory
- I set SAGE_PATH to the current directory
- I did sage -t -long -optional mtx.pyx
What is the difference?
Best regards,
Simon
--~--~---------~--~----~------------~-------~--~----~
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/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
