On Mon, 11 Dec 2006, William Stein wrote:
> I don't know.  I'd like to get feedback from more people.  Already
> requiring
> JAVA is an obstacle, but it's a reasonable one.   What does sage-devel
> think?

Fork? Sage, Sage+Java.

>From a previous email of yours, which follows below: "Obviously, java is
something we'll only be able to ignore for so long, since there is some
relevant software written in it...."

Ifti.

---------- Forwarded message ----------
Date: Wed, 11 Oct 2006 08:23:37 -0700
From: William Stein <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: [sage-devel] Re: Flexiprovider crypto lib


On Wed, 11 Oct 2006 07:48:21 -0700, Iftikhar Burhanuddin
<[EMAIL PROTECTED]> wrote:
> Do we have any candidates for crypto libraries to be bundled along with
> Sage?

Yes.  There is pyssl, which we'll need for securing the notebook.  We'll
have to bundle some SSL implementation too, maybe YASSL.  There is also
a python package called pycrypto, which would seem like a canonical
choice.

> At the IPAM.UCLA Crypto/# Theory workshop, Johannes Buchmann mentioned a
> Java based toolkit which his group has developed -- Flexiprovide.
>
> Curious to know how Python integrates with Java libs and if there are
any
> issues pushing/pulling data, efficiency, etc.

Java programs are not suitable for inclusion in SAGE, because Java is
too proprietary.  Since the beginning the dependencies for installing
"SAGE core" has been
     GCC, flex, bison, perl, make, m4, tar, ranlib, libstdc++*-dev.

Optional packages may have more dependencies...

Obviously, java is something we'll only be able to ignore for so long,
since there is some relevant software written in it....




--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to