Hej Doug, Nice list of bugs. I was wondering, might you be interested in becoming a sage developer to? It's really not that hard, and it sounds to me that if you knew how to edit the source code of sage you would be able to fix some of these bugs yourself, and become one of the volunteers who makes sage better. And the advantage is by being a developer you are the first one to be able to use the fixed or improved code! If you are willing to learn how to contribute code to sage, I'm also willing to aid you in guiding you trough the developement process. The feature request in number 3 sounds like one which is really doable. If you are interested I could teach you how to create and submit patches to trac while fixing this issue. Just send me an e-mail.
Kind regards, Maarten Derickx -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
