Re: [sage-devel] Re: All of sage as a python library

2010-11-01 Thread William Stein
On Thu, Oct 28, 2010 at 11:02 PM, Dima Pasechnik dimp...@gmail.com wrote: On Oct 28, 4:23 am, Georg S. Weber georgswe...@googlemail.com wrote:   (1) Have a Python library called sagecore, which is just the most important standard spkg's (e.g., Singular, PARI, etc.), perhaps eventually

[sage-devel] Re: All of sage as a python library

2010-11-01 Thread leif
On 1 Nov., 07:51, William Stein wst...@gmail.com 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

Re: [sage-devel] Re: All of sage as a python library

2010-11-01 Thread William Stein
On Mon, Nov 1, 2010 at 7:34 AM, leif not.rea...@online.de wrote: On 1 Nov., 07:51, William Stein wst...@gmail.com wrote: This post is about:    (1) Concern about distutils/setuptools/etc., is misplaced.    (2) Python3 and librarifying Sage. First, all this discussion about

[sage-devel] Re: All of sage as a python library

2010-11-01 Thread Georg S. Weber
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 library.  

[sage-devel] Re: All of sage as a python library

2010-11-01 Thread leif
On 1 Nov., 17:16, William Stein wst...@gmail.com wrote: On Mon, Nov 1, 2010 at 7:34 AM, leif not.rea...@online.de wrote: On 1 Nov., 07:51, William Stein wst...@gmail.com wrote: This post is about:    (1) Concern about distutils/setuptools/etc., is misplaced.    (2) Python3 and

Re: [sage-devel] Re: All of sage as a python library

2010-11-01 Thread William Stein
On Mon, Nov 1, 2010 at 9:48 AM, Georg S. Weber georgswe...@googlemail.com 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

[sage-devel] Re: All of sage as a python library

2010-11-01 Thread Jason Grout
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,

[sage-devel] Re: All of sage as a python library

2010-11-01 Thread Jason Grout
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

[sage-devel] Re: All of sage as a python library

2010-10-29 Thread Dima Pasechnik
On Oct 28, 4:23 am, Georg S. Weber georgswe...@googlemail.com 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

[sage-devel] Re: All of sage as a python library

2010-10-27 Thread Simon King
On 27 Okt., 08:26, Dan Drake dr...@kaist.edu 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

[sage-devel] Re: All of sage as a python library

2010-10-27 Thread Michael Brickenstein
Hi! On Oct 27, 3:44 am, William Stein wst...@gmail.com 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

[sage-devel] Re: All of sage as a python library

2010-10-27 Thread Volker Braun
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

[sage-devel] Re: All of sage as a python library

2010-10-27 Thread Dima Pasechnik
On Oct 27, 1:05 pm, leif not.rea...@online.de wrote: On 27 Okt., 05:54, Dima Pasechnik dimp...@gmail.com 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

Re: [sage-devel] Re: All of sage as a python library

2010-10-27 Thread William Stein
On Wed, Oct 27, 2010 at 3:48 AM, Volker Braun vbraun.n...@gmail.com 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

[sage-devel] Re: All of sage as a python library

2010-10-26 Thread Dima Pasechnik
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

[sage-devel] Re: All of sage as a python library

2010-10-26 Thread leif
On 27 Okt., 05:54, Dima Pasechnik dimp...@gmail.com 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