Dear Maarten Derickx (and Sage developers)
thank you for reply.
Using:
sage -t /home/jpedro/sage/local/lib/python2.6/site-packages/
meg/paramparse.py
causes "ImportError" as before but if I use
sage -python -m doctest paramparse.py
using ">>>" instead of "sage:" everything works on each modul
What happens when you do:
sage -t
/home/jpedro/sage/local/lib/python2.6/site-packages/meg/paramparse.py
sage -t forcelib
/home/jpedro/sage/local/lib/python2.6/site-packages/meg/paramparse.py
I don't know why, but maybe the testing framework gets confused because of
the path to the file that y
Dear William and Sage developers,
I request help once more about testing "sage -t" a package that was not
installed on Sage using "sage -i".
The package name we are developing is named "meg" and is almost ready.
Testing ("sage -t") is this last step.
All of the package code is on "/home/jpedro
The "-force_build" did not work and I believe it's a problem of "how to use
import" on new Sage packages.
Recalling first message, I want to build a new optional package based on
*.py modules.
It seems that
sage -t my_module.py
moves my_module.py to a .sage/tmp folder and there executes the
On Fri, Aug 19, 2011 at 6:29 AM, Pedro Cruz wrote:
>
> I am creating a new package in python separated from Sage tree (following
> [1]) but depends entirely on Sage Math library (and also on Sage Notebook),
> However
> sage -t somemodule.py
> is not working because of imports. ==> But using thi
I am creating a new package in python separated from Sage tree (following
[1]) but depends entirely on Sage Math library (and also on Sage Notebook),
However
sage -t somemodule.py
is not working because of imports. ==> But using this package normally
causes no problems with imports!
I'm f
