On 11/1/10 8:09 PM, Jason Grout wrote:
On 11/1/10 1:33 PM, William Stein wrote:
My plan for migrating the Sage notebook to not use twisted anymore is
to switch
to Flask (http://flask.pocoo.org/). Flask is a small
"microframework", but it only
works with Python 2.x, and they have no plans at pres
On 11/1/10 1:33 PM, William Stein wrote:
My plan for migrating the Sage notebook to not use twisted anymore is to switch
to Flask (http://flask.pocoo.org/). Flask is a small
"microframework", but it only
works with Python 2.x, and they have no plans at present to support Python 3.x.
Evidently,
On Mon, Nov 1, 2010 at 9:48 AM, Georg S. Weber
wrote:
>
>>
>> This post is about:
>>
>> (1) Concern about distutils/setuptools/etc., is misplaced.
>> (2) Python3 and librarifying Sage.
>>
>> First, all this discussion about distutils/setuptools/david
>> cournapeau, etc., is actually mostly I
On 1 Nov., 17:16, William Stein wrote:
> On Mon, Nov 1, 2010 at 7:34 AM, leif wrote:
> > On 1 Nov., 07:51, William Stein wrote:
> >> This post is about:
>
> >> (1) Concern about distutils/setuptools/etc., is misplaced.
> >> (2) Python3 and librarifying Sage.
>
> >> First, all this discussi
>
> This post is about:
>
> (1) Concern about distutils/setuptools/etc., is misplaced.
> (2) Python3 and librarifying Sage.
>
> First, all this discussion about distutils/setuptools/david
> cournapeau, etc., is actually mostly IRRELEVANT to making the core
> Sage library into a standalone li
On Mon, Nov 1, 2010 at 7:34 AM, leif wrote:
> On 1 Nov., 07:51, William Stein wrote:
>> This post is about:
>>
>> (1) Concern about distutils/setuptools/etc., is misplaced.
>> (2) Python3 and librarifying Sage.
>>
>> First, all this discussion about distutils/setuptools/david
>> cournapeau,
On 1 Nov., 07:51, William Stein wrote:
> This post is about:
>
> (1) Concern about distutils/setuptools/etc., is misplaced.
> (2) Python3 and librarifying Sage.
>
> First, all this discussion about distutils/setuptools/david
> cournapeau, etc., is actually mostly IRRELEVANT to making the cor
On Thu, Oct 28, 2010 at 11:02 PM, Dima Pasechnik wrote:
>
>
> On Oct 28, 4:23 am, "Georg S. Weber"
> wrote:
>> > (1) Have a Python library called "sagecore", which is just the most
>> > important standard spkg's (e.g., Singular, PARI, etc.), perhaps
>> > eventually built *only* as shared object
On Oct 28, 4:23 am, "Georg S. Weber"
wrote:
> > (1) Have a Python library called "sagecore", which is just the most
> > important standard spkg's (e.g., Singular, PARI, etc.), perhaps
> > eventually built *only* as shared object libraries (no standalone
[...]
>
> I just can't believe David Cou
>
> (1) Have a Python library called "sagecore", which is just the most
> important standard spkg's (e.g., Singular, PARI, etc.), perhaps
> eventually built *only* as shared object libraries (no standalone
> interpreters).
>
Interesting!
One challenge I see here, is that on the one hand, Pytho
On Tue, Oct 26, 2010 at 8:54 PM, Dima Pasechnik wrote:
> Being able to get Sage as a part of PyPI would be great!
> Taking into account how many of Sage spkgs are there, e.g. cython,
> scipy, networkx, cvxopt,
> this looks like the right way of factoring
> out components that are just packaged int
On Wed, Oct 27, 2010 at 3:48 AM, Volker Braun wrote:
> Just to clarify, are we talking about different namespaces
>
> from sagecore.rings import Integers
> from sagemain.modular.all import euler_phi
> from sagecombinat.combinat import choose_nk
>
> This seems a bit unwieldy.
I'm not talking about
On Oct 27, 1:05 pm, leif wrote:
> On 27 Okt., 05:54, Dima Pasechnik wrote:
>
> > Being able to get Sage as a part of PyPI would be great!
> > Taking into account how many of Sage spkgs are there, e.g. cython,
> > scipy, networkx, cvxopt,
> > this looks like the right way of factoring
> > out co
Just to clarify, are we talking about different namespaces
from sagecore.rings import Integers
from sagemain.modular.all import euler_phi
from sagecombinat.combinat import choose_nk
This seems a bit unwieldy. On the other hand, if Sage pulls everything
into sage.* then how do I know which library
Hi!
On Oct 27, 3:44 am, William Stein wrote:
> The above is already how the ecosystem with Python
> (http://pypi.python.org/pypi), Perl (http://www.cpan.org/), R, etc.,
> work. Fortunately, Python has reasonably good support already for
> this.
I think that going into this direction is some aw
On 27 Okt., 08:26, Dan Drake wrote:
> On Tue, 26 Oct 2010 at 06:44PM -0700, William Stein wrote:
> > (1) Have a Python library called "sagecore", which is just the most
> > important standard spkg's (e.g., Singular, PARI, etc.), perhaps
> > eventually built *only* as shared object libraries (no
On 27 Okt., 05:54, Dima Pasechnik wrote:
> Being able to get Sage as a part of PyPI would be great!
> Taking into account how many of Sage spkgs are there, e.g. cython,
> scipy, networkx, cvxopt,
> this looks like the right way of factoring
> out components that are just packaged into Sage.
> At t
Being able to get Sage as a part of PyPI would be great!
Taking into account how many of Sage spkgs are there, e.g. cython,
scipy, networkx, cvxopt,
this looks like the right way of factoring
out components that are just packaged into Sage.
At the moment just keeping apace with the latter
component
18 matches
Mail list logo
