On Mon, Dec 30, 2013 at 1:04 PM, William Stein wrote:
> On Mon, Dec 30, 2013 at 12:47 PM, Nils Bruin wrote:
> > On Monday, December 30, 2013 12:35:37 PM UTC-8, R. Andrew Ohana wrote:
> >>
> >> Moreover, I don't think we have to force the switch, it should be
> >> perfectly possible to support bo
On Mon, Dec 30, 2013 at 12:47 PM, Nils Bruin wrote:
> On Monday, December 30, 2013 12:35:37 PM UTC-8, R. Andrew Ohana wrote:
>>
>> Moreover, I don't think we have to force the switch, it should be
>> perfectly possible to support both python 2 and python 3 for a period of
>> time.
>
>
> What's the
On Monday, December 30, 2013 12:35:37 PM UTC-8, R. Andrew Ohana wrote:
> Moreover, I don't think we have to force the switch, it should be
> perfectly possible to support both python 2 and python 3 for a period of
> time.
>
What's the benefit of that? The sage process itself will be running on
On Mon, Dec 30, 2013 at 10:14 AM, William Stein wrote:
> This discussion on Hacker News is relevant to "The Annual Sage on
> Python 3 Thread"
>
>https://news.ycombinator.com/item?id=6985207
>
>http://alexgaynor.net/2013/dec/30/about-python-3/
>
> 1. Argument against switching now:
>
> One
This discussion on Hacker News is relevant to "The Annual Sage on
Python 3 Thread"
https://news.ycombinator.com/item?id=6985207
http://alexgaynor.net/2013/dec/30/about-python-3/
1. Argument against switching now:
One quote from the HN discussion: "My last few Python projects have
started
On Wednesday, December 25, 2013 8:40:27 PM UTC+1, Jean-Pierre Flori wrote:
>
> On a slightly unrelated topic, currently the only function of pycrypto
> used in the Sage library is indeed in the monoid stuff and that's the
> byte_to_long function.
> Although I don't feel we should remove pycrypt
On Wed, Dec 25, 2013 at 11:46 AM, R. Andrew Ohana
wrote:
> 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. Becau
On Wed, Dec 25, 2013 at 10:58 AM, Martin Albrecht
wrote:
> On Wednesday 25 Dec 2013 09:09:58 Jean-Pierre Flori wrote:
>> I think having pycrypto in Sage is cool for ... cryptographers :)
>
> I am not sure this is true. PyCrypto is quite high-level, it gives you RSA,
> AES, SHA256 and sutff like th
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. us
On a slightly unrelated topic, currently the only function of pycrypto used
in the Sage library is indeed in the monoid stuff and that's the
byte_to_long function.
Although I don't feel we should remove pycrypto from standard packages, I
feel we could implement this ourselves if this prevents a
On Wednesday, December 25, 2013 7:58:27 PM UTC+1, Martin Albrecht wrote:
>
> On Wednesday 25 Dec 2013 09:09:58 Jean-Pierre Flori wrote:
> > I think having pycrypto in Sage is cool for ... cryptographers :)
>
> I am not sure this is true. PyCrypto is quite high-level, it gives you
> RSA,
> AES
On Wednesday 25 Dec 2013 09:09:58 Jean-Pierre Flori wrote:
> I think having pycrypto in Sage is cool for ... cryptographers :)
I am not sure this is true. PyCrypto is quite high-level, it gives you RSA,
AES, SHA256 and sutff like that. At such a high level I guess it would be
useful for testing/
On Wednesday, December 18, 2013 6:24:40 AM UTC+1, R. Andrew Ohana wrote:
>
> I've made #15530 to track the progress on supporting python3 (and there is
> already a good amount there that is up for review).
>
>
> Also, other than the trivial usage in
> sage.monoids.string_monoid(_element), I'm n
I've made #15530 to track the progress on supporting python3 (and there is
already a good amount there that is up for review).
Also, other than the trivial usage in sage.monoids.string_monoid(_element),
I'm not finding any real usage of pycrypto. Am I missing something? If not,
I would elect to m
On Wed, 11 Dec 2013 at 02:53AM -0800, R. Andrew Ohana wrote:
> But this time with a report!
>
> Broken spkgs:
>
> sagetex (maybe?)
Why the "maybe"? What happens if you try to use Py3?
In January I might be able to update SageTeX to Python 3. It should be
easy. (Famous last words?)
Dan
--
On Wed, 11 Dec 2013 12:55:10 Volker Braun wrote:
> On Wednesday, December 11, 2013 8:37:15 PM UTC, François wrote:
> > > (almost certainly polybori -- it depends on scons)
> >
> > Polybori: ask Alexander Drier
>
> Not exactly fair if its via the scons dependency ;-)
>
> http://scons.org says tha
On Wednesday, December 11, 2013 8:37:15 PM UTC, François wrote:
>
> > (almost certainly polybori -- it depends on scons)
> Polybori: ask Alexander Drier
>
Not exactly fair if its via the scons dependency ;-)
http://scons.org says that the current release will be the last one to
support pyt
On Wed, 11 Dec 2013 02:53:25 R. Andrew Ohana wrote:
> But this time with a report!
>
> Broken spkgs:
>
> PIL
We actually now make it possible to use pillow in sage-on-gentoo
one small patch in the sage library is needed.
> setuptools (really distribute)
> sympy
Recent sympy can do py3
> pycry
I did a quick search for these:
gdmodule
Only used in sage/matrix/matrix2.pyx and
sage/matrix/matrix_modn_sparse.pyx in the visualize_structure() method.
Should be replaced by a different imaging library.
PIL
Used in various places: PolyBoRi, Pygments, Sphinx, SciPy
sqlalchemy
sagenb's S
But this time with a report!
Broken spkgs:
PIL
setuptools (really distribute)
sympy
pycrypto
pynac
rpy2
pexpect
gdmodule
sqlalchemy
networkx
mpmath
zn_poly
sagenb
sagetex (maybe?)
scons
(almost certainly polybori -- it depends on scons)
and a number of others that use python 2 spkg-install scrip
20 matches
Mail list logo
