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 "sage:" examples. But if my_module.py contains "import my_other_module" a problem came up because "my_other_module.py" is not going to be moved to the .sage/tmp directory. What design principle am I missing? Thank you, Pedro -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
