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 -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
