On Tue, 12 Jan 2010 04:53:14 Craig Citro wrote: > Hi Francois, > > > While Carl Witty mentions that python shouldn't be patched directly > > as it would make it harder to package sage for distros, Craig Citro > > went ahead and did just that. > > I couldn't find a ticket or a thread describing the why of this > > decision. > > Basically, the thought was that this patch was a legit bug in python, > and we could get this patch pushed upstream in the long run. I hadn't > gotten around to doing that, but I'll start taking care of that today. > > The real objection Carl raised was to another patch which was *not* > merged, as I recall. Ultimately we didn't think such a patch would get > upstreamed ever, which is why we ultimately worked around that. > > That said, I agree that it's frustrating for distro packaging. I'll > try and get this patch merged, but I don't know how long that will > take. That said, I think there are several patches in our Python spkg > -- is this the only one that's causing trouble, or just the only one > you've run into because it causes doctest failures? > > -cc > 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?
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
