Both bugs are fixed in the ticket's patch. In particular, this now works as
it should:
sage: x[0] = 1
x_0 = 1
sage: x[0] = 1
1 = x_0
sage: 1 = x[0]
1 = x_0
sage: 1 = x[0]
x_0 = 1
On Wednesday, October 24, 2012 4:31:19 AM UTC+1, P Purkayastha wrote:
This is
That's only one bug as mentioned in #12091 (having numerics on the left
of a comparison operator). The other bug is the chained inequalities.
sage: x[0] = x[1] = 2
x_1 = 2
This can't be fixed (I think) without moving to python3.
On 10/24/2012 05:38 PM, Volker Braun wrote:
Both bugs are fixed
Yes, there is another can of worms in chained comparisons. So far I've
implemented parents for LinearFunction, but there should be a parent for
LinearConstraint as well. I'm pretty sure your example can be fixed by
overriding __nonzero__.
On Wednesday, October 24, 2012 2:23:02 PM UTC+1, P
Hello !!!
According to the doc, this seems to be a bug. Unfortunately, this behavior
produces wrong results. It took me some time to isolate the problem! Bugs
which just produce error messages are much friendlier ...
I totally agree. It has been reported before, and I definitely
I'd say there are two bugs:
1) p.new_variable() should raise an error if it doesn't understand the
argument, and not just silently do nothing.
2) the inequality operators should work both ways to create
LinearConstraints
On Tuesday, October 23, 2012 9:36:54 AM UTC+1, Peter Mueller wrote:
And, by the way, the MIP stuff has absolutely no support for any of the
Sage infrastructure. Everything just derives from object. Not even
SageObject.
On Tuesday, October 23, 2012 10:41:05 AM UTC+1, Volker Braun wrote:
2) the inequality operators should work both ways to create
Here's a trac ticket that -- at least -- prints a bug report.
http://trac.sagemath.org/sage_trac/ticket/13646
Nathann
--
You received this message because you are subscribed to the Google Groups
sage-support group.
To post to this group, send email to sage-support@googlegroups.com.
To
Hellooo !!
I'd say there are two bugs:
There are always too many.
1) p.new_variable() should raise an error if it doesn't understand the
argument, and not just silently do nothing.
Perfectly true. #13646 is meant to fix that :-)
2) the inequality operators should work both ways to
On 10/23/2012 05:26 PM, Nathann Cohen wrote:
Hello !!!
According to the doc, this seems to be a bug. Unfortunately, this
behavior produces wrong results. It took me some time to isolate the
problem! Bugs which just produce error messages are much friendlier ...
I
I've added the missing parents and coercion bits in a patch at the trac
ticket.
On Tuesday, October 23, 2012 12:44:03 PM UTC+1, Nathann Cohen wrote:
Here's a trac ticket that -- at least -- prints a bug report.
http://trac.sagemath.org/sage_trac/ticket/13646
--
You received this message
This is really nice. A long standing functionality. When we move to
python3, the other bug can also be taken care of.
On Tuesday, October 23, 2012 10:24:26 PM UTC+8, Volker Braun wrote:
I've added the missing parents and coercion bits in a patch at the trac
ticket.
On Tuesday, October 23,
11 matches
Mail list logo
