Hi Craig!

So how is the baby?????

On Wed, Jul 08, 2009 at 11:03:21AM -0700, Craig Citro wrote:
> 
> > What's the status on this one? I though that the bottom line of the
> > discussion at SD15 for this one (not to be mixed up with #5986) was that:
> >
> >  - Apart from importing the cPickle sources into the Sage tree, the
> >   patch was essentially trivial (a 5 lines change to the cPickle
> >   code) and therefore easy to review
> >  - It had some reasonable chances to be merged into Python at some point.
> >  - Craig was going to push this upstream
> >  - There were no simple alternatives
> >
> > And that in view of all this it was good to go in Sage, and would get
> > a positive review shortly. Which did not occur.
> >
> > Craig, Carl: could you please do this now or comment back why not?
> >
> 
> My plan is still to push this upstream at some point soon, with the
> intention that it make it into Python 2.7/3.2. 

Cool

> However, the release date for 2.7 isn't even set yet -- meaning it's
> still quite a ways off.

Ok.

> Honestly, I don't recall -- what was our plan for patching this in
> the interim? Or did we not decide on anything because we got
> sidetracked talking about #5986?

We definitely got sidetracked talking about #5986 ...

As far as I recall, the plan for #5985 was to just apply what's on
trac (i.e. one patch to import the cPickle sources and tests in the
sage tree and a 5 line patch on them), as a temporary measure until
things get fixed in python.

Are you ok finishing the review accordingly?

Thanks in advance,

Cheers,
                                Nicolas
--
Nicolas M. Thiéry "Isil" <nthi...@users.sf.net>
http://Nicolas.Thiery.name/

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to 
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to