Thanks ! I have a file called common.py and that screws up something related to Sage documentation. After renaming that file everything seems to work well again.
On Friday, March 8, 2013 10:52:07 AM UTC-7, John H Palmieri wrote: > > > > On Friday, March 8, 2013 8:46:19 AM UTC-8, tvn wrote: >> >> Still same problem after doing that. This makes me think that it won't >> work when SAGE_PATH is set to anything other than empty (By default >> SAGE_PATH is not set to anything at all) >> > > This is not a general problem; I'm guessing that it is specific to your > particular setup. You are adding some directories to SAGE_PATH; maybe some > of the file names in those directories are conflicting with Sage files, so > various imports in the Sage library don't work anymore (because they are > importing the wrong file). For example, if I put a file called "conf.py" in > a directory in my SAGE_PATH, then I can't read documentation any more. So > maybe you have a problematic file name. You could list the files here and > we could try to troubleshoot it, or you could prefix all of your files with > "tvn_", for instance, and try again. > > -- > John > > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-support?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
