On Sun, 31 Jan 2010 at 10:15AM +0000, Dr. David Kirkby wrote: > 3) Change Sage so that the hashlib module of python is not essential > for a functioning Sage. That is I suspect the easiest option. I > don't claim to understand how Sage builds fully, but I would have > thought crypto support was not a requirement.
People in this thread have been discussing this issue only in terms of encryption, but hashlib also does...well, hashing, such as MD5 and SHA1. We make a big deal out of Sage being Python-based, and Python in turn says that the "batteries are included" -- these batteries typically include being able to easily take hashes of strings, so I would strongly prefer that the hashlib module stay the way it is. (Also, SageTeX needs md5 hashing support in its current state, and I'd be unhappy if, just after getting it merged, some of its functionality needs to be changed!) Dan -- --- Dan Drake ----- http://mathsci.kaist.ac.kr/~drake -------
signature.asc
Description: Digital signature
