On Sunday, June 8, 2014 9:23:27 PM UTC+1, leif wrote: > > Hmmm, so this should get fixed upstream sagenb? >
We probably should have a better way of distributing the sagenb dependencies ;-) > While one could simply copy-paste those two functions and use them from > elsewhere (patching Flask-OpenID), it's unclear to me why pycrypto > issues the warning when importing /that/ module; Agree. Both: * pycrypto should split its utility module in ones that are harmless and ones that are potentially vulnerable to timing attacks * python-openid shouldn't use the helpers from pycrypto; its all pretty stale code in the name of Python 2.3 support anyways. python3-openid is essentially a fork. -- 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 sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
