> Hi Craig! > > So how is the baby????? > Very overdue! But she'll hopefully be here soon. ;)
>> 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. > So I chatted with Robert Bradshaw about this, and he reminded me what we were talking about at SD15. Since this 5-line patch is one we expect to be upstreamed, we should just patch our python spkg instead of importing the cpickle file into the sage repo. I'll roll a new spkg shortly. > Are you ok finishing the review accordingly? > Yep, I'll try and work on it right now. -cc --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
