Dear Sage / Sage-Combinat developers,
I am up and running, fresh and full of energy and hope. And I have a
bold plan for getting the core of the category patch in by tomorrow,
and the rest in 10 days.
Carl, Craig, David, Mike, Robert (B): what about meeting at 3pm to
build a consensus around this (or another) plan?
Cheers,
Nicolas
------------------------------------------------------------------------------
This afternoon:
- I finish all the renaming things we have discussed
- Carl + Craig choose a parent (say SemiGroups().example()) and add a
call to pickle_fix on it and on all its categories upon import
time. Then disable cPickle-5986-nested-classes-submitted.patch, and
check that pickling works. If yes, this means that in the worst
case scenario, we can always fall back to this.
Yet, I am now 100% convinced that want to avoid this if at all
possible. So we do not pursue this way but rather finish reviewing:
- cPickle-5986-nested-classes-submitted.patch
By the way, they also review:
- explain-pickle-v1.patch
Or remove the trivial dependency on it.
- Robert reviews:
- parent-element_constructor-fix-5979-submitted.patch
- 5598-coerce-declare.patch
- categories-numberfield_homset-nt.patch
- David reviews:
- dynamic_class-5991-submitted.patch
And implements the alternative getattr approach as we have discussed
in a patch on top of categories-nt
- Rob Beezer (it may need to be someone else!) reviews:
- transitive_ideal-6000-submitted.patch
- Early tonight, I cut categories-nt.patch into managable chunks.
- The chunk about CombinatorialFreeModule get bumped for later
This is the one who break code in sage.combinat.
Without it, the tests should just fail in a couple of the
categories (AlgebrasWithBasis, ...) which use
CombinatorialFreeModule's in their examples. This won't break
preexisting code, so we just add a temporary 'notest' to silence them.
- We meet (for dinner?) and split the work of reviewing the chunks
Tonight:
- you guys review the chunks. You fix the trivial issues directly in
little patches on the sage-combinat server.
- I fold them progressively, and take care of the more serious
issues to will certainly pop up.
Hopefuly, by noon tomorrow we can get a positive review on all of
those, and get the main category framework into sage. What remains is
combinatorics-related, and we can manage the review process among
Sage-Combinat developpers (but outside volunteers are of course very
welcome to participate!).
Tomorrow:
- I review (after a quick discussion) Florent's patches:
- family_enumset-fh.patch
- enumset_unions-fh.patch
- I work on cleaning up the free-modules chunk, and we prereview it.
- Mike prereviews with me categories-symmetric_group_algebra-nt.patch
- We run a discussion on later cleanups (morphisms, ...)
Early next week:
- I work with Jason and Mike (we will be at the same conference) to
clean up the sf / ncsf patches. We cross review the result.
Later this week:
- I work with Davis' people, to streamline the root system patch,
and we get it reviewed by Anne / Justin
Once everything is ready (early the week later?):
- We finish uploading everything on trac and set positive reviews.
- Michael gets it in whenever he feels it fits well with the Sage
release schedule
--
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
-~----------~----~----~----~------~----~------~--~---
