[sage-devel] Sage 5.2 released

2012-07-30 Thread Jeroen Demeyer
Sage 5.2 was released on 25 July 2012. It is available in source and binary form from: * http://www.sagemath.org/download.html Sage (http://www.sagemath.org/) is developed by volunteers and combines over 90 open source packages. For instructions about installing Sage, see * http://www.sagema

Re: [sage-devel] Re: [sage-support] Re: Error building gcc

2012-07-30 Thread kfiz
Am Dienstag, 31. Juli 2012 07:37:42 UTC+2 schrieb Dima Pasechnik: > > > > On Tuesday, 31 July 2012 10:38:52 UTC+8, kfiz wrote: >> >> >> >> Am Montag, 30. Juli 2012 16:25:24 UTC+2 schrieb Dima Pasechnik: >>> >>> If you look for the 1st Error in the log, you will see >>> >>> ---

Re: [sage-devel] Re: [sage-support] Re: Error building gcc

2012-07-30 Thread Dima Pasechnik
On Tuesday, 31 July 2012 10:38:52 UTC+8, kfiz wrote: > > > > Am Montag, 30. Juli 2012 16:25:24 UTC+2 schrieb Dima Pasechnik: >> >> If you look for the 1st Error in the log, you will see >> >> --- >> ld: wa

Re: [sage-devel] Re: [sage-support] Re: Error building gcc

2012-07-30 Thread kfiz
Am Montag, 30. Juli 2012 16:25:24 UTC+2 schrieb Dima Pasechnik: > > If you look for the 1st Error in the log, you will see > > --- > ld: warning: in build/genautomata.o, file was built for unsupported file

[sage-devel] Re: Documenting Factory Functions (RE trac #13282)

2012-07-30 Thread Rob Beezer
On Monday, July 30, 2012 1:31:53 PM UTC-7, Nils Bruin wrote: > While I agree that tab completion is very useful as a low-cost > documentation tool, I find it a little worrisome if our design > decisions come to be dominated by having tab completion generate > appropriate indices. In lots of cas

Re: [sage-devel] Re: Documenting Factory Functions (RE trac #13282)

2012-07-30 Thread Mike Hansen
On Mon, Jul 30, 2012 at 10:31 AM, Nils Bruin wrote: > While I agree that tab completion is very useful as a low-cost > documentation tool, I find it a little worrisome if our design > decisions come to be dominated by having tab completion generate > appropriate indices. In lots of cases it will g

[sage-devel] Re: Documenting Factory Functions (RE trac #13282)

2012-07-30 Thread Nils Bruin
On Jul 30, 12:06 pm, Rob Beezer wrote: > Then the thing to do would be to write > > my_functions = No, I would think that the module should appear exactly in the spot where you want the names imported. "import my_functions" would be the appropriate thing to do, unless there is some architectural

[sage-devel] Re: Documenting Factory Functions (RE trac #13282)

2012-07-30 Thread Rob Beezer
On Monday, July 30, 2012 10:31:49 AM UTC-7, Nils Bruin wrote: > > In python there is the concept of a "module" as well as a class. > Modules can do that much better. > The pattern Samuel suggests shows up several places in Sage, such as for examples of graphs and posets. I'm doing something si

[sage-devel] Re: Documenting Factory Functions (RE trac #13282)

2012-07-30 Thread Nils Bruin
On Jul 30, 9:02 am, samgonshaw wrote: > Say I wrote a suite of functions and made them available through a factory > class such as: > > {{{ > class MyFunctions(): >     def FunctionA(self,*args,**kwargs): >         ... >     def Functionb(self,*args,**kwargs): >         ... >     def FunctionC(sel

[sage-devel] Documenting Factory Functions (RE trac #13282)

2012-07-30 Thread samgonshaw
Say I wrote a suite of functions and made them available through a factory class such as: {{{ class MyFunctions(): def FunctionA(self,*args,**kwargs): ... def Functionb(self,*args,**kwargs): ... def FunctionC(self,*args,**kwargs): ... my_functions=MyFunctions(

[sage-devel] Documenting functions accessed through a factory (Re #13282)

2012-07-30 Thread samgonshaw
If I introduce a suite of functions via a function factory such as {{{ class MyFunctions(): def FunctionA(self,*args,kwarg**) In the patch in trac #13282 it has been suggested to introduce a suite of functions accessing the graded ring

Re: [sage-devel] Re: [sage-support] Re: Error building gcc

2012-07-30 Thread Dima Pasechnik
If you look for the 1st Error in the log, you will see --- ld: warning: in build/genautomata.o, file was built for unsupported file format which is not the architecture being linked (x86_64) Undefined symbo

Re: [sage-devel] the default behaviour of reduce() for ideals

2012-07-30 Thread Marco Streng
2012/7/30 Thomas Feulner : > Hi, > > in the definition of a QuotientRing there is the following assumption > > ASSUMPTION: > > ``I`` has a method ``I.reduce(x)`` returning the normal form > of elements `x\in R`. In other words, it is required that > ``I.reduce(x)==I.reduce(y)`` `\if

[sage-devel] the default behaviour of reduce() for ideals

2012-07-30 Thread Thomas Feulner
Hi, in the definition of a QuotientRing there is the following assumption ASSUMPTION: ``I`` has a method ``I.reduce(x)`` returning the normal form of elements `x\in R`. In other words, it is required that ``I.reduce(x)==I.reduce(y)`` `\iff x-y \in I`, and ``x-I.reduce(x) in I