[sage-combinat-devel] partition code breaks k-Schur functions

2013-03-05 Thread Anne Schilling
Hi! I noticed today that some patch between the beginning and trac_14102 in the sage-combinat queue breaks k-Schur functions. Perhaps the partition patches? This needs to be fixed!!! Best, Anne - sage: Sym = SymmetricFunctions(QQ) sage: s = Sym.schur() sage: ks = Sym.kschur(3,1) sage: s[2,

Re: [sage-combinat-devel] Re: Longest element in a Coxeter Group - name decision

2013-03-05 Thread Nicolas M. Thiery
On Tue, Mar 05, 2013 at 03:11:00AM -0800, tom d wrote: >I think longest_element is fine; Ok for me, unless someone finds something better. >long_word indicates that there will be a word returned instead of >an element, which is maybe not what we're after here. +1 Thanks Kannappan f

Re: [sage-combinat-devel] Re: Longest element in a Coxeter Group - name decision

2013-03-05 Thread Kannappan Sampath
Hah! Fantastic!! I'll go ahead and implement this later tonight if I receive no more information regarding this issue. Thanks for the enlightenment, Tom. With Sincere Regards, Kannappan. On Tue, Mar 5, 2013 at 4:41 PM, tom d wrote: > I think longest_element is fine; long_word indicates that th

[sage-combinat-devel] Re: kschur versus new_kschur

2013-03-05 Thread Simon King
Hi Anne, On 2013-03-05, Anne Schilling wrote: > Yes, sage.combinat.sf.kschur is old. Sage now uses the functionality > in sage.combinat.sf.new_kschur, so it indeed would not make sense > to prevent regression in kschur. Great! So, I'll feel a bit less guilty... Cheers, Simon -- You received t

Re: [sage-combinat-devel] kschur versus new_kschur

2013-03-05 Thread Anne Schilling
Hi Simon, Yes, sage.combinat.sf.kschur is old. Sage now uses the functionality in sage.combinat.sf.new_kschur, so it indeed would not make sense to prevent regression in kschur. Eventually, we will want to move new_kschur to kschur. Viele Gruesse, Anne On 3/5/13 6:09 AM, Simon King wrote: > Hi!

[sage-combinat-devel] Re: Longest element in a Coxeter Group - name decision

2013-03-05 Thread tom d
I think longest_element is fine; long_word indicates that there will be a word returned instead of an element, which is maybe not what we're after here. Wiser minds than mine will have more knowledge of how to handle deprecation, but here's an example from skew_partition.py: sage: x.r_quotient

[sage-combinat-devel] kschur versus new_kschur

2013-03-05 Thread Simon King
Hi! I wonder: There is sage.combinat.sf.kschur and sage.combinat.sf.new_kschur. Is the former just deprecated? Hence, does it make any sense at all to try and prevent regressions in kschur? I think of #13991. Best regards, Simon -- You received this message because you are subscribed to the Goo

[sage-combinat-devel] Longest element in a Coxeter Group - name decision

2013-03-05 Thread Kannappan Sampath
Hello friends, I am writing this mail to ask for your help in a naming decision. In the file sage/categories/finite_coxeter_groups.py, there is a function called long_element. The docstring asks if this should be renamed and if so, to what? There are two suggestions from the authors: longest_elem