> (suggestions, or better patches, to improve that example are welcome) Earlier I posted code to construct exterior algebras in Sage here:
http://sporadic.stanford.edu/bump/exterior.sage This uses CombinatorialAlgebras. Currently the preferred method of constructing a ring is to implement it as a subclass of CombinatorialFreeModule using convenient hooks that are provided there. I reimplemented the exterior algebra that way and for comparison, here it is: http://sporadic.stanford.edu/bump/exterior1.sage Both methods are about the same number of lines of code, but the second method is cleaner and easier if you know how to do it. I think both rings have identical behavior. I would like to comment on the deprecation warnings in combinatorial_algebra.py. The method of constructing a ring in combinatorial_algebra.py is quick and convenient. I do agree that the preferred method is better. I think that any construation that is to be put into sage should not use CombinatorialAlgebras. However I think the deprecation warning (just "deprecated - don't use!") in combinatorial_algebras.py is not helpful. After all, the old method does work and is convenient and quick. If I want a quick and dirty ring for some experiment I might use it. There is the deprecation warning but no pointer towards a better way. Dan -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org To unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
