On Tue, May 5, 2009 at 9:34 AM, Nicolas M. Thiery <[email protected]> wrote: > (2) My patch does not touch the Python interpreter, but a copy of > cPickle within the Sage source tree. This does not prevent upgrading > python, as long as we keep our copy of cPickle reasonably updated. Of > course this is only acceptable as a temporary workaround.
Clever. That's actually a very good idea, which mostly negates my concerns. Nonetheless, I would really like to hear from python-dev about what *they* thinking about pickling and nested classes. What if there are some good reasons for the current design that we're just not thinking of? > (3) -1 on holding back further a large scale merge for a minor > technical detail that will eventually be resolved one way or the > other. > > (4) My general feeling is that nested classes in Python are on the > edge of full maturity, with just a couple glitches here and > there. Typically, Florent mentionned to me that the devel version of > Sphynx now handled them correctly. This is why I feel confident using > them. And there is a clear advantage to using them (which I'll argue > about in my demo in Seattle). --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
