On Wed, 13 Jan 2010 22:35:16 Craig Citro wrote: > > If you work on getting this merged upstream as a bug that's a good > > selling point for us. We can produce a patched ebuild and possibly > > get it accepted. > > Do you have a bug tracking number of some kind for it? > > I just submitted the bug: > > http://bugs.python.org/issue7689 > > I'll let you know as I hear anything. (I know one of the core Python > devs has a standing offer that he'll review a patch if you review 5 of > his; if I don't hear anything in a week or so, I'll just bite the > bullet and get this reviewed that way.) > > -cc > That's quite good already I can open a bug in Gentoo, quote that bug and put a patched ebuild in the sage-on-gentoo overlay. There are more chances of it being included in the main tree if there is a bug upstream and a need for it in Gentoo.
Thanks, Francois
-- 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
