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:
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
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:
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!
Hi Anne,
On 2013-03-05, Anne Schilling a...@math.ucdavis.edu 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
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 sdent...@gmail.com wrote:
I think longest_element is fine; long_word
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 for
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:
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:
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:
Yes, I would support such a warning; I've even led tutorials with new sage
users where defining things called 'max' or 'min' has seemed an obvious
thing to do and then minutes later been a problem as the default function
was unavailable.
On Tuesday, March 5, 2013 12:36:33 AM UTC+3, luisfe
On 5 March 2013 06:54, Peng Tian tianpeng.ch...@gmail.com wrote:
Dear David,
You are right. I tried to change the data type of the code in sage, which is
int type in the source code of SAGE and now I'm using long int instead.
The previous error is gone and everything is working well now.
Hello all,
I'm trying to install mysql-python within the sage shell on a Mac (OS X
10.8). Outside of the sage shell, I can install it, by typing:
easy_install mysql-python
but within the sage shell I get the following error:
Running MySQL-python-1.2.4/setup.py -q bdist_egg --dist-dir
I was reading through the documentation at
http://www.sagemath.org/doc/reference/sage/plot/plot.html
and came across this section that makes no sense.
*
When the labels have quite different orders of magnitude or are very large,
scientific notation (the e notation for powers of
On Tuesday, March 5, 2013 11:18:27 AM UTC-5, Brad Burkman wrote:
I was reading through the documentation at
http://www.sagemath.org/doc/reference/sage/plot/plot.html
and came across this section that makes no sense.
*
When the labels have quite different orders of magnitude
Hey everyone,
My guess is that the reason it works is because MathJax is being forgiving
in how it parses things. I don't know if MathJax has a strict setting
which would complain in these cases.
Hmm...well at least behavior will now be documented.
I think the developer's guide could
See http://www.maa.org/pubs/cmj_mar13.html and your local library (or
online, if you have access) for Jeff Denny's review of Sage in the
just-appeared College Math Journal. It is even-handed but overall very
positive. Enjoy!
Minh/Harald - can you add this to the bibliography online?
--
Karl-Deiter: plot(x^3,(x,0,500),ticks=[[],[]]) worked. Thanks.
On Tuesday, March 5, 2013 10:18:27 AM UTC-6, Brad Burkman wrote:
I was reading through the documentation at
http://www.sagemath.org/doc/reference/sage/plot/plot.html
and came across this section that makes no sense.
Hello,
debug() in a new cell after 1/0 does not work for me with IndexError:
string index out of range message. This is using Sage 5.7 or
5.8.beta2, while 5.5 shows the interact William has added a while ago.
Is this a regression (due to IPython upgrade?) or should I build Sage
somehow
Solved it. In the sage shell, I wrote:
export CC=/usr/bin/gcc
and then easy_install worked
On Tuesday, 5 March 2013 11:00:55 UTC-5, Chris Berg wrote:
Hello all,
I'm trying to install mysql-python within the sage shell on a Mac (OS X
10.8). Outside of the sage shell, I can install it, by
On Mon, Mar 4, 2013 at 3:41 AM, Simon King simon.k...@uni-jena.de wrote:
Hi Jeroen,
On 2013-03-04, Jeroen Demeyer jdeme...@cage.ugent.be wrote:
On 2013-03-04 12:01, Simon King wrote:
+With 99.3% confidence, startup time decreased by at least 0.1%
+With 99.4% confidence, startup time
On Tue, Mar 5, 2013 at 7:39 AM, David Loeffler
d.a.loeff...@warwick.ac.uk wrote:
On 5 March 2013 06:54, Peng Tian tianpeng.ch...@gmail.com wrote:
Dear David,
You are right. I tried to change the data type of the code in sage, which is
int type in the source code of SAGE and now I'm using long
On Wed, Feb 27, 2013 at 2:24 AM, Simon King simon.k...@uni-jena.de wrote:
Hi Volker,
On 2013-02-27, Volker Braun vbraun.n...@gmail.com wrote:
The output of sage -startuptime only lists the 50 slowest modules, not
all.
OK. But *with* the patch, sage.plot.graphics is the 6th slowest module,
On Tue, Mar 5, 2013 at 10:55 AM, Robert Bradshaw
rober...@math.washington.edu wrote:
On Tue, Mar 5, 2013 at 7:39 AM, David Loeffler
d.a.loeff...@warwick.ac.uk wrote:
On 5 March 2013 06:54, Peng Tian tianpeng.ch...@gmail.com wrote:
Dear David,
You are right. I tried to change the data type of
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 for
Hi Robert, Volker and other fans of lazy import!
Working on #4327 made me want to be able to lazy import a full
module. That is have:
lazy_import(sage.combinat.root_system.plot)
be a lazy analogue of:
import sage.combinat.root_system.plot
Currently lazy_import
26 matches
Mail list logo
