Does this perhaps explain $ ls .sage/init.sage Display all 205 possibilities? (y or n) init.sage init.sageNmWQYm init.sagek93xb1.py init.sage055VVK init.sageNmWQYm.py init.sageknxNEa init.sage055VVK.py init.sagePbawHw init.sageknxNEa.py init.sage0OD1dD init.sagePbawHw.py init.sagelLffOi init.sage0OD1dD.py init.sageQ2ytvz init.sagelLffOi.py init.sage2Bz1iC init.sageQ2ytvz.py init.sageleKfOW ...
which is really more such files than necessary. Hi sage-devel, > > I would like that when sage -t is run on a local_file.sage, then it first > loads $DOT_SAGE/init.sage. The part of code related to "-t" in the script > src/bin/sage actually checks that the init.sage file exists: > > if [ ! -f "$DOT_SAGE"/init.sage ]; then > echo >&2 "init.sage does not exist ... creating" > touch "$DOT_SAGE"/init.sage > fi > > but it seems that init.sage is not loaded afterwards before tests. Do we > agree that init.sage should be loaded by sage -t when run on local files ? > > My motivation is the following. I would like to run tests on my optional > package slabbe-0.1.spkg by simply adding "from slabbe import *" in the > init.sage file. > > Thanks, > Sébastien > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
