I disagree with the sentiment that we should make python package X a standard package because it is useful for Y. At that rate, every (compatibly licensed) mathematics and science python package will be a standard part of sage. Because pycrypto is not truly a dependency of the sage library (i.e. used in a non-trivial manner), nor is it nicely integrated into to sage (you have to `from pycrypto import foo`), to me it clearly falls into this boat.
-- Andrew -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
