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
> 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
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
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 th
