It's not the empty string: ggeorg@maschke% echo $PYTHONPATH /usr/lib64/python2.7/site-packages/mpich:/u/ggeorg/data/sync/software/python:/tmp/pytex:/u/ggeorg/data/sync/.system/extensions/python/lib:/u/ggeorg/data/sync/.system/extensions/python/external_modules:/u/ggeorg/data/sync/software/python:/tmp/pytex:/u/ggeorg/data/sync/.system/extensions/python/lib:/u/ggeorg/data/sync/.system/extensions/python/external_modules ggeorg@maschke% sage -sh
Starting subshell with Sage environment variables set. Don't forget to exit when you are done. Beware: * Do not do anything with other copies of Sage on your system. * Do not use this for installing Sage packages using "sage -i" or for running "make" at Sage's root directory. These should be done outside the Sage shell. Bypassing shell configuration files... Note: SAGE_ROOT=/scratch/userdata/.software/sage (sage-sh) ggeorg@maschke:ggeorg$ echo $PYTHONPATH :/u/ggeorg/data/sync/software/python:/u/ggeorg/data/sync/software/python:/scratch/userdata/.software/sage/local/lib/python Georg On Thursday, January 23, 2014 9:07:27 PM UTC+1, Volker Braun wrote: > > Obvious question would be: what is your Python path? I guess set to the > empty string. Unset variables that if you don't want, don't set them to the > empty string. > > Cleaning up PYTHONPATH: > Old: > ":/u/ggeorg/data/sync/software/python:/scratch/userdata/sage-6.0/local/lib/python" > New: > "/u/ggeorg/data/sync/software/python:/scratch/userdata/sage-6.0/local/lib/python" > > > On Thursday, January 23, 2014 6:32:18 PM UTC, Georg Grafendorfer wrote: >> >> I just want to confirm that removing /usr/local64.hg/bin from the path >> solves the problem. >> >> But there is still one doctest failure: >> >> sage -t --long src/sage/tests/cmdline.py >> ********************************************************************** >> File "src/sage/tests/cmdline.py", line 204, in >> sage.tests.cmdline.test_executable >> Failed example: >> print out >> Expected: >> Found local metadata for sqlalchemy-... >> = SQLAlchemy = >> ... >> SQLAlchemy is the Python SQL toolkit... >> Got: >> Cleaning up PYTHONPATH: >> Old: >> ":/u/ggeorg/data/sync/software/python:/scratch/userdata/sage-6.0/local/lib/python" >> New: >> "/u/ggeorg/data/sync/software/python:/scratch/userdata/sage-6.0/local/lib/python" >> Found local metadata for sqlalchemy-0.5.8 >> = SQLAlchemy = >> <BLANKLINE> >> == Description == >> <BLANKLINE> >> SQLAlchemy is the Python SQL toolkit and Object Relational Mapper >> that gives application developers the full power and flexibility of SQL. >> <BLANKLINE> >> It provides a full suite of well known enterprise-level persistence >> patterns, designed for efficient and high-performing database access, >> adapted into a simple and Pythonic domain language. >> <BLANKLINE> >> Website: http://www.sqlalchemy.org/ >> <BLANKLINE> >> == License == >> <BLANKLINE> >> MIT >> <BLANKLINE> >> == SPKG Maintainers == >> <BLANKLINE> >> * Mike Hansen >> * Mitesh Patel >> <BLANKLINE> >> == Upstream Contact == >> <BLANKLINE> >> * http://www.sqlalchemy.org/community.html >> <BLANKLINE> >> == Dependencies == >> * python >> * setuptools >> <BLANKLINE> >> == Build Notes == >> <BLANKLINE> >> Use the standard sources. No changes from the official sources. >> <BLANKLINE> >> == Changelog == >> <BLANKLINE> >> === SQLAlchemy-0.5.8.p0 (Mitesh Patel, March 4, 2010) === >> * Upgrade to 0.5.8. >> * Tweak removal of previous versions. >> * Disable tests in spkg-check, since they now require nose. >> <BLANKLINE> >> === SQLAlchemy-0.4.6.p0 (Yi Qiang, June 25, 2008) === >> * version bump >> * make sure to delete the old SQLAlchemy install directories >> (Michael Abshoff) >> <BLANKLINE> >> === SQLAlchemy-0.4.3.p1 (Michael Abshoff, March 14th, 2008) === >> * add hg repo >> * add .hgignore >> * make sure SAGE_LOCAL is installed (#633) >> * use /usr/bin/env bash shebang (#1638) >> <BLANKLINE> >> === SQLAlchemy-0.4.3.p0 (Yi Qiang) === >> * Initial version >> <BLANKLINE> >> <BLANKLINE> >> ********************************************************************** >> 1 item had failures: >> 1 of 210 in sage.tests.cmdline.test_executable >> [209 tests, 1 failure, 76.12 s] >> >> >> >> Georg >> >> >> On Monday, January 20, 2014 10:41:08 PM UTC+1, Volker Braun wrote: >>> >>> Just to answer my own question, >>> src/sage/combinat/root_system/coxeter_group.py calls gap3 if it finds one >>> in the path. So there is the reason. It seems that Georg's gap3 install is >>> broken, which is outside of our control. As a workaround, remove >>> /usr/local64.hg/bin from the path before running Sage. >>> >>> >>> >>> On Monday, January 20, 2014 9:37:26 PM UTC, Volker Braun wrote: >>>> >>>> I'm willing to bet that gap3 is a shell script that >>>> runs gap-static-linux-i686 under the hood. >>>> >>>> The question is, who is calling gap3? >>>> >>>> >>>> >>>> On Monday, January 20, 2014 9:09:50 PM UTC, Simon King wrote: >>>>> >>>>> Also no surprise, since the local Sage-version of GAP is called gap >>>>> and >>>>> not gap3. >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "sage-release" 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-release. For more options, visit https://groups.google.com/groups/opt_out.
