# Revision history [back]

### Doctesting a cython file

Bonjour à tous,

I have a cython file stab.pyx, which uses a C file libstab.c, located in the same directory. Everything works fine with:

sage: load stab.pyx
Compiling ./stab.pyx...


and I can use classes, methods and so on defined in my file. It works fine too in notebook, I just need giving the full access path for loading (compiling) this file.

Today I had the strange idea of adding some documentation (wow) and doctests. Again the notebook displays my doc with nice formatting when I use the usual '?'. The problem is that I can't verify doctests with:

sage -t stab.pyx


Sage complains ggc fails because it does'nt find libstab.c. What's a simple way for automatic doctesting this file ?

Amitiés [JB]

### Doctesting a cython file

Bonjour à tous,

I have a cython file stab.pyx, which uses a C file libstab.c, located in the same directory. Everything works fine with:

sage: load stab.pyx
Compiling ./stab.pyx...


and I can use classes, methods and so on defined in my file. It works fine too in notebook, I just need giving to give the full access path for loading (compiling) this file.

Today I had the strange idea of adding some documentation (wow) and doctests. Again the notebook displays my doc with nice formatting when I use the usual '?'. The problem is that I can't verify doctests with:

sage -t stab.pyx


Sage complains ggc gcc fails because it does'nt find libstab.c. What's a simple way for automatic doctesting this file ?

Amitiés [JB]