On 10/23/2014 10:49 PM, Sébastien Labbé wrote:
>
> 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 ?
>
It used to be loaded even with `sage -t`, but I think the current
default is probably safer (i.e. will produce fewer false positives).
However, I'd like it to be optional, maybe with a flag to sage -t?
I have a local library of sage code that was affected by the change.
It's easy to workaround now (none of my modules import one another), but
could get rather annoying in the future. Right now the failing module is
all.py:
$ cat ~/src/sage.d/mjo/all.py
"""
Import all of the other code, so that the user doesn't have to do it
in his script. Instead, he can just `from mjo.all import *`.
"""
from interpolation import *
from misc import *
from orthogonal_polynomials import *
from plot import *
from symbol_sequence import *
from symbolic import *
My init.sage sets the path so that the above works:
import os
import site
# Add '~/src/sage.d' to our path.
sitedir = os.path.expanduser('~/src/sage.d')
site.addsitedir(sitedir)
from mjo.all import *
I'd like to keep those working with a minimum of noise. Right now I just
avoid testing all.py, but like I said, if one of my modules begins to
import another, I'll need some other solution.
--
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.
