Simon King wrote: > Dear Burcin, > > On Nov 18, 11:46 am, Burcin Erocal <[EMAIL PROTECTED]> wrote: >>> Do I understand correctly that this will be fixed in Sage 3.2? >> Yes, it will be fixed in 3.2. > > Good! > >>> Do you mean "better approach for Sage" or "better approach for my >>> writing doc-tests"? By the way, what is SAGE_PATH? It isn't defined, >>> and even search_src('SAGE_PATH') fails. >> SAGE_PATH is one of the many undocumented environment variables Sage >> uses [1], which I found in the list archives when I was trying to solve >> this problem. > > It still seems to me that it is *less* than undocumented: > It is not defined in Sage (commandline), search_src fails, and also it > is not defined when I run "sage -sh".
At the sage prompt, you can type "%env" to get the environment variables as a dictionary, or "!env" to actually run the env command to get the environment variables. For the SAGE variables, I get: SAGE_TESTDIR SAGE_LOCAL SAGE_ORIG_LD_LIBRARY_PATH_SET SAGE_STARTUP_FILE SAGE_ROOT SAGE_ORIG_LD_LIBRARY_PATH SAGE_DATA SAGE64 SAGE_SERVER SAGE_PACKAGES Huh, no SAGE_PATH. Jason --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---