Re: [sage-devel] sage thoughts

2011-02-11 Thread Nicolas M. Thiery
On Sat, Feb 12, 2011 at 02:32:09AM +0800, D. S. McNeil wrote: > My single most common use involves parts_in, though, and that's what doesn't > work: Partitions(10, min_length=2, max_length=6, parts_in=[1,2,3,5]) > is a completely > consistent set of constraints, but it silently drops two of them, a

Re: [sage-devel] sage thoughts

2011-02-11 Thread D. S. McNeil
On Thu, Feb 10, 2011 at 9:38 PM, Nicolas M. Thiery wrote: > However one should be careful: the kwarg > options are *not* mutually exclusive as long as they are consistent > (for some loose definition of consistent), and this feature is used in > many places. My single most common use involves par

Re: [sage-devel] sage thoughts

2011-02-10 Thread Nicolas M. Thiery
Hi Doug, Welcome to the Sage community! On Wed, Feb 09, 2011 at 01:02:10PM +0800, D. S. McNeil wrote: > (2) No kwarg constraints in Partitions/Compositions should be mutually > exclusive. (I think there's a ticket for this but I can't find it > now.) > > Partitions(15,length=5, parts_in

Re: [sage-devel] sage thoughts

2011-02-09 Thread Willem Jan Palenstijn
On Wed, Feb 09, 2011 at 04:46:52PM +0800, D. S. McNeil wrote: > > Could you post an example [re: my whitespace issues --ed] to nail down > > exactly what you're talking about? > > sage: s = 'for i in range(3):\n' + ' '*4 + 'print i\n' > sage: # add extra space, such as can often happen in practice

Re: [sage-devel] sage thoughts

2011-02-09 Thread David Roe
> >> (1) gcd is broken.http://trac.sagemath.org/sage_trac/ticket/10459 > [..] > > I'm personally OK either way with this. > > IMO a*b = gcd(a,b)*lcm(a,b) should be maintained wherever possible. > There are pari codes whose direct Sage equivalent silently breaks for > this reason, and I can't br

Re: [sage-devel] sage thoughts

2011-02-09 Thread D. S. McNeil
>> (1) gcd is broken.    http://trac.sagemath.org/sage_trac/ticket/10459 [..] > I'm personally OK either way with this. IMO a*b = gcd(a,b)*lcm(a,b) should be maintained wherever possible. There are pari codes whose direct Sage equivalent silently breaks for this reason, and I can't bring myself to

Re: [sage-devel] sage thoughts

2011-02-08 Thread William Stein
On Tue, Feb 8, 2011 at 9:02 PM, D. S. McNeil wrote: > Hello! > > First time poster, so brief introduction: planetary astronomer, been > using Sage for years for both science and fun.  I'm also one of the > Editors-in-Chief of the OEIS, and have been experimenting with using > Sage for bulk sequenc