Dr. David Kirkby wrote:
Robert Bradshaw wrote:
On Feb 6, 2010, at 3:58 AM, Dr. David Kirkby wrote:
I've noticed an issue at
http://t2nb.math.washington.edu:8000/
where something fails when using the GUI, but which works at the
command line.
import haslib
Are you sure that's not a typo? You probably want hashlib (which
should work regardless of OpenSSL being found). I'd be really
surprised if "import haslib" (missing h) worked anywhere.
Hi Robert,
yes, you are correct, it was a typo. It is actually
"import _hashlib"
which causes the problem. It works at the command line, but not in the
browser.
Just checking python's spkg-install, it is hashlib, not _hashlib which is
checked.
-------------------------------------------
# Make sure sufficient crypto support is available in the built python.
# This is critical.
python -c "import hashlib"
if [ $? -eq 0 -a -f "$SAGE_LOCAL/bin/python" ]; then
echo "hashlib module imported"
exit 0
else
echo "hashlib module failed to import"
exit 1
fi
-----------------------------------------------
Either way, this fails unless those libraries are in the search path. Sage will
simply build python, then exit with the message
"hashlib module failed to import"
and terminate the build.
I can't see anything wrong with adding /usr/sfw/lib to the search path in
python. It can't break anything, and will allow Sage to build on Solaris.
Whether it will be 100% functional at run-time is another matter.
Dave
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
