solve(eqts, solution_dict=True) gives IndexError if there's no solution for eqts

26 views
Skip to first unread message

tvn

unread,
May 17, 2011, 1:20:01 PM5/17/11
to sage-s...@googlegroups.com
shouldn't this be taken care of automatically ?  


sage: solve([x == 0, x== 1],x,solution_dict=True)
...

IndexError: list index out of range


sage: solve([x == 0, x== 1],x)
[]


zsharon

unread,
May 18, 2011, 2:21:10 AM5/18/11
to sage-support
This is already mentioned here: http://www.mail-archive.com/sage-s...@googlegroups.com/msg20832.html
(It seems from that thread that this may not be a problem with Sage
itself.)

It should be reported as a bug if it hasn't been already.

kcrisman

unread,
May 18, 2011, 9:07:45 AM5/18/11
to sage-support


On May 18, 2:21 am, zsharon <zacherysha...@gmail.com> wrote:
> This is already mentioned here:http://www.mail-archive.com/sage-s...@googlegroups.com/msg20832.html
> (It seems from that thread that this may not be a problem with Sage
> itself.)
>
> It should be reported as a bug if it hasn't been already.

It is http://trac.sagemath.org/sage_trac/ticket/8553, as it happens.
It should have been fixed a LONG time ago, but I think everyone
involved lost energy because there was a lot of extraneous banter.
The patches do still seem to apply properly, so it's probably just a
matter of finishing things off with the last comment about an extra
line, and reviewing it.

- kcrisman

tvn

unread,
May 18, 2011, 9:17:43 AM5/18/11
to sage-s...@googlegroups.com
so is there someway we can do so that this patch or temporary solution be pushed into the next Sage release ?  

kcrisman

unread,
May 18, 2011, 11:31:34 AM5/18/11
to sage-support


On May 18, 9:17 am, tvn <nguyenthanh...@gmail.com> wrote:
> so is there someway we can do so that this patch or temporary solution be
> pushed into the next Sage release ?  

Well, *you* can do that yourself - see, for instance,
http://www.sagemath.org/doc/developer/walk_through.html#reviewing-a-patch

Unfortunately, until someone has time to finish this review/fix, we
can't just put it in. Because this is the end of the school year in
many jurisdictions, some things tend to slow down around now (though
in this case, as I noted above, it seems to have been because of some
side issues).

In the long run, this is a good thing, because it ensures higher
quality code (not perfect code! nothing ensures that). You can feel
free to put any comments you have on that ticket, though, or even to
review it if you feel like this is within your skill set (as may be
the case!). That is how people turn from users to improvers of Sage,
and we like to encourage that very much.

- kcrisman
Reply all
Reply to author
Forward
0 new messages