[sage-devel] Re: Categories restart: call for reviewers
On Mon, Oct 19, 2009 at 11:01:00PM -0700, Robert Bradshaw wrote: On Oct 13, 2009, at 12:34 PM, Nicolas M. Thiery wrote: Any chances for you to review shortly: http://combinat.sagemath.org/patches/file/tip/categories-fixsagelib-nt.patch Looks fine to me. Seems to be mostly renaming stuff and plumbing category definitions around. Indeed (and also a couple __len__ - cardinality). Thanks! One more category patch reviewed :-) Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Categories restart: call for reviewers
On Oct 13, 2009, at 12:34 PM, Nicolas M. Thiery wrote: Hi Robert, Craig, Any chances for you to review shortly: http://combinat.sagemath.org/patches/file/tip/categories-fixsagelib-nt.patch Looks fine to me. Seems to be mostly renaming stuff and plumbing category definitions around. - Robert --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Categories restart: call for reviewers
On Tue, Oct 13, 2009 at 05:45:42PM -0700, Robert Bradshaw wrote: On Oct 13, 2009, at 12:34 PM, Nicolas M. Thiery wrote: Any chances for you to review shortly: http://combinat.sagemath.org/patches/file/tip/categories-fixsagelib-nt.patch 500 - Internal Server Error Argl, again! Anyone knows why light-httpd/mercurial crashes there? It used to work before the server was migrated. In the mean time: please use hg clone http://combinat.sagemath.org/patches/ To get a copy of the files (or the usual sage -combinat install) Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Categories restart: call for reviewers
Hi Robert, Craig, Any chances for you to review shortly: http://combinat.sagemath.org/patches/file/tip/categories-fixsagelib-nt.patch Thanks! Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Categories restart: call for reviewers
On Oct 13, 2009, at 12:34 PM, Nicolas M. Thiery wrote: Hi Robert, Craig, Any chances for you to review shortly: http://combinat.sagemath.org/patches/file/tip/categories-fixsagelib-nt.patch 500 - Internal Server Error - Robert --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Categories restart: call for reviewers
On Sep 16, 2009, at 5:49 AM, Nicolas M. Thiery wrote: Dear category fans, Thanks to Florent (and previous work by Anne, Jason, Franco, ...) all the sage-combinat related categories have a positive review. There remains just the mostly trivial categories listed below which would be best reviewed by some non-sage-combinat person (standard categories), or specialist (number fields, schemes, ...). Please help! Other than that: Craig: what's your time line for finalizing #5985, as a patch for python? Robert: What's your time line for: - the review of categories-fixsagelib-nt.patch - finalizing #5597 [with patch, needs work] rename coercion action methods Rebased, has doctests, needs review. - finalizing #5598 [with patch, needs work] (allow post-creation (pre-use) declaration of coercions) Does the later really depend on the former? No, I don't think there's a dependancy. Lots of doctest failures, but I bet they're all due to the same bug or two. I'll get to it within a week. Robert: Florent did review the category+cython proof of concept example of semigroup. Could you still have a glance at it? Sure, link? David Roe: what's your time line for the review of categories-numberfield_homset-nt.patch? Craig, Robert, Carl: what's the status for #5986. Remember that I am not convinced that the alternative metaclass approach (using #6121) will be practical. So if you insist going this way, you have to implement it, or at the very least to provide me with a proof of concept patch covering all the use cases. We're pretty sure it can be done--proof of concept in the works. We'd really like to get this pickling thing out of the way without adding ugliness that will never go upstream (and I've always regretting letting cruft get in as it seems to never actually get cleaned up until it really bites and is a mess.) - Robert P.S. Cool category graph. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Categories restart: call for reviewers
On Fri, Oct 09, 2009 at 12:25:54AM -0700, Robert Bradshaw wrote: Robert: What's your time line for: - the review of categories-fixsagelib-nt.patch - finalizing #5597 [with patch, needs work] rename coercion action methods Rebased, has doctests, needs review. Yep. Will review very soon, unless someone beats me to it! (last week has been loaded with teaching) - finalizing #5598 [with patch, needs work] (allow post-creation (pre-use) declaration of coercions) Does the later really depend on the former? No, I don't think there's a dependancy. Lots of doctest failures, but I bet they're all due to the same bug or two. I'll get to it within a week. Great. Robert: Florent did review the category+cython proof of concept example of semigroup. Could you still have a glance at it? Sure, link? http://trac.sagemath.org/sage_trac/wiki/CategoriesRoadMap See sage.categories.examples.semigroups_cython with the category patches applied: http://combinat.sagemath.org/hgwebdir.cgi/code/file/tip/sage/categories/examples/semigroups_cython.pyx Craig, Robert, Carl: what's the status for #5986. Remember that I am not convinced that the alternative metaclass approach (using #6121) will be practical. So if you insist going this way, you have to implement it, or at the very least to provide me with a proof of concept patch covering all the use cases. We're pretty sure it can be done--proof of concept in the works. We'd really like to get this pickling thing out of the way without adding ugliness that will never go upstream (and I've always regretting letting cruft get in as it seems to never actually get cleaned up until it really bites and is a mess.) As I said on sage-combinat-devel, I am now convinced by your alternative workaround which is slick and well localized. P.S. Cool category graph :-) Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Categories restart: call for reviewers
Hi Tim! On Mon, Aug 24, 2009 at 02:39:15PM +0200, Nicolas Thiéry wrote: On Mon, Aug 24, 2009 at 04:04:28AM -0400, Tim Daly wrote: Do you have the inheritance graph of the categories? Almost :-) The category primer currently suggests: sage: GradedHopfAlgebrasWithBasis(QQ).category_graph().plot() which gives a reasonable approximation. However some categories are missing, and the layout of the plot is ugly (we definitely need a good graph layout engine for acyclic graphs; that's on its way using graphviz dot2tex, but not quite ready). Having such a graph have been on my todo list from the beginning. I'll try to hack something shortly and post a pdf. I finally got there! With Sage 4.1.1, all sage-combinat patches applied, graphviz installed, and the experimental dot2tex.spkg (pfff) one can now do: sage: G = sage.categories.category.category_graph().reverse() sage: G.set_latex_options(format=dot2tex) sage: view(G, tightpage = True, pdflatex=True) Which produces the following: http://sagetrac.org/sage_trac/raw-attachment/wiki/CategoriesRoadMap/sage-category-graph.pdf Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Categories restart: call for reviewers
On Fri, Oct 09, 2009 at 12:04:18AM +0200, Nicolas Thiéry wrote: With Sage 4.1.1, all sage-combinat patches applied, graphviz installed, and the experimental dot2tex.spkg (pfff) one can now do: sage: G = sage.categories.category.category_graph().reverse() sage: G.set_latex_options(format=dot2tex) sage: view(G, tightpage = True, pdflatex=True) Which produces the following: http://sagetrac.org/sage_trac/raw-attachment/wiki/CategoriesRoadMap/sage-category-graph.pdf I forgot to mention: for parametrized categories, the graph includes just a typical instance of the category (like Modules(QQ), Algebras(QQ), ...) Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
[sage-devel] Re: Categories restart: call for reviewers
Hi John! On Sun, Aug 23, 2009 at 12:37:11PM +0100, John Cremona wrote: 2009/8/23 Nicolas M. Thiery nicolas.thi...@u-psud.fr: So you can focus on looking at the code, doc, and tests in the files mentioned in: http://trac.sagemath.org/sage_trac/wiki/CategoriesCategoriesReview possibly simply by browsing: http://combinat.sagemath.org/hgwebdir.cgi/code/file/tip/sage/categories) and make sure they makes sense. I don't really know how this type of reviewing differs from normal Sage reviewing of patches attached to trac tickets. Just that you don't need to worry about the technical side (checking that the patch applies, pass test, ...). Also setting a positive review will be on the wiki page, file by file, rather than on the trac ticket. Finally, there is essentially no datastructure/algorithm issue in the current code (that will change!) But anyway, I looked at one file, finite_fields.py, and the method _call_() in there looks wrong -- it raises an error whatever the input, while the dicstring suggests that it is supposed to try using __call__() and only change the error message if that does not work. It's the converse: __call__ tries to do generic stuff (like C(P) returns P if P is readilly a parent in the category C), and if that does not work calls _call_ (similar to what happens for __mul__ / _mul). I actually haven't changed that part; that's how it is in the original category framework. See the doc of _call_ / __call__ in Category (sage.category.category.py). Suggestions to improve the doctests to clarify this are welcome! If I have completely misunderstood what is going on, then I will carry on ignoring the category activity until it is finished, Please don't! at which point I'm sure I will use it all the time! Which is why I want as much early feedback from you as possible :-) Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ --~--~-~--~~~---~--~~ 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 URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Categories restart: call for reviewers
Nicolas Do you have the inheritance graph of the categories? Tim Daly Nicolas M. Thiery wrote: Hi John! On Sun, Aug 23, 2009 at 12:37:11PM +0100, John Cremona wrote: 2009/8/23 Nicolas M. Thiery nicolas.thi...@u-psud.fr: So you can focus on looking at the code, doc, and tests in the files mentioned in: http://trac.sagemath.org/sage_trac/wiki/CategoriesCategoriesReview possibly simply by browsing: http://combinat.sagemath.org/hgwebdir.cgi/code/file/tip/sage/categories) and make sure they makes sense. I don't really know how this type of reviewing differs from normal Sage reviewing of patches attached to trac tickets. Just that you don't need to worry about the technical side (checking that the patch applies, pass test, ...). Also setting a positive review will be on the wiki page, file by file, rather than on the trac ticket. Finally, there is essentially no datastructure/algorithm issue in the current code (that will change!) But anyway, I looked at one file, finite_fields.py, and the method _call_() in there looks wrong -- it raises an error whatever the input, while the dicstring suggests that it is supposed to try using __call__() and only change the error message if that does not work. It's the converse: __call__ tries to do generic stuff (like C(P) returns P if P is readilly a parent in the category C), and if that does not work calls _call_ (similar to what happens for __mul__ / _mul). I actually haven't changed that part; that's how it is in the original category framework. See the doc of _call_ / __call__ in Category (sage.category.category.py). Suggestions to improve the doctests to clarify this are welcome! If I have completely misunderstood what is going on, then I will carry on ignoring the category activity until it is finished, Please don't! at which point I'm sure I will use it all the time! Which is why I want as much early feedback from you as possible :-) Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ --~--~-~--~~~---~--~~ 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 URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Categories restart: call for reviewers
On Sun, Aug 23, 2009 at 02:48:15AM -0700, javier wrote: On Aug 23, 12:56 am, Nicolas M. Thiery nicolas.thi...@u-psud.fr wrote: For the rest, this review is a bit specific: you can skip the technical part of the review (checking that the patch applies smoothly, pass tests, ...); this part will be done at once for all the category code once the mathematical review will be finished. So, just to be clear, I don't need to get a trac account or learn how to use mercurial right now, right? Nope. I tried, but got a No username found error that resulted in aborting the process. I guess I do need that trac account after all? This is just a warning. Ah but you are using sage 4.1.1, right? Oops, sorry, I should have though about this and warned you. The sage-combinat patches have not yet be rebased for 4.1.1. Actually they have, but only on my machine, and I still need to double check a couple things before pushing. Please try again tonight or tomorrow night. Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ --~--~-~--~~~---~--~~ 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 URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Categories restart: call for reviewers
Hi Tim! On Mon, Aug 24, 2009 at 04:04:28AM -0400, Tim Daly wrote: Do you have the inheritance graph of the categories? Almost :-) The category primer currently suggests: sage: GradedHopfAlgebrasWithBasis(QQ).category_graph().plot() which gives a reasonable approximation. However some categories are missing, and the layout of the plot is ugly (we definitely need a good graph layout engine for acyclic graphs; that's on its way using graphviz dot2tex, but not quite ready). Having such a graph have been on my todo list from the beginning. I'll try to hack something shortly and post a pdf. Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ --~--~-~--~~~---~--~~ 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 URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Categories restart: call for reviewers
On Aug 23, 12:56 am, Nicolas M. Thiery nicolas.thi...@u-psud.fr wrote: For the rest, this review is a bit specific: you can skip the technical part of the review (checking that the patch applies smoothly, pass tests, ...); this part will be done at once for all the category code once the mathematical review will be finished. So, just to be clear, I don't need to get a trac account or learn how to use mercurial right now, right? possibly simply by browsing: http://combinat.sagemath.org/hgwebdir.cgi/code/file/tip/sage/categories) and make sure they makes sense. About this, I clicked on a file at random (algebras.py) to have an idea on a general shape of the stuff. I was very startled to see a method called direct sum. The category of algebras (over a fixed based field) does not have a direct sum (or coproduct), what is constructed there is actually the direct product. Sure thing, as in the big category (vector spaces over the base field) there is a direct sum, which coincides with the direct product, but it doesn't descend to the category of algebras: the map A --- A\oplus B in vector spaces is defined by a |--- (a,0), which this is not a morphism of algebras. I know that most physicists and some mathematicians abuse the term direct sum to refer to the direct product, but since this whole thing is called Categories I expect a Category theory level of precision. Is this the kind of stuff you refer to with checking mathematical sanity, or am I going needlessly abstract here? You may want to actually install the patch with sage -combinat install to play around with it and/or create a reviewer patch. I tried, but got a No username found error that resulted in aborting the process. I guess I do need that trac account after all? Cheers Javier --~--~-~--~~~---~--~~ 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 URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Categories restart: call for reviewers
2009/8/23 Nicolas M. Thiery nicolas.thi...@u-psud.fr: So you can focus on looking at the code, doc, and tests in the files mentioned in: http://trac.sagemath.org/sage_trac/wiki/CategoriesCategoriesReview possibly simply by browsing: http://combinat.sagemath.org/hgwebdir.cgi/code/file/tip/sage/categories) and make sure they makes sense. I don't really know how this type of reviewing differs from normal Sage reviewing of patches attached to trac tickets. But anyway, I looked at one file, finite_fields.py, and the method _call_() in there looks wrong -- it raises an error whatever the input, while the dicstring suggests that it is supposed to try using __call__() and only change the error message if that does not work. If I have completely misunderstood what is going on, then I will carry on ignoring the category activity until it is finished, at which point I'm sure I will use it all the time! John --~--~-~--~~~---~--~~ 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 URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Categories restart: call for reviewers
Dear category fans, For information: in principle, the new category code is now 100% doctested! Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ --~--~-~--~~~---~--~~ 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 URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Categories restart: call for reviewers
Dear javier, On Thu, Aug 20, 2009 at 02:17:34AM -0700, javier wrote: I would like to get more involved with Sage developing, and mathematical sanity check looks like something I can certainly do and a nice way to get started, so I will try to jump into this one. Great, thanks! Mind that I haven't been involved with Sage any further than the mail lists so far, so any pointers will be appreciated. Just to complete the Minh's answer (thanks Minh!) for this particular mission: You probably want to start by browsing through: http://combinat.sagemath.org/doc/reference/sage/categories/primer.html to get the general picture about categories. For the rest, this review is a bit specific: you can skip the technical part of the review (checking that the patch applies smoothly, pass tests, ...); this part will be done at once for all the category code once the mathematical review will be finished. So you can focus on looking at the code, doc, and tests in the files mentioned in: http://trac.sagemath.org/sage_trac/wiki/CategoriesCategoriesReview possibly simply by browsing: http://combinat.sagemath.org/hgwebdir.cgi/code/file/tip/sage/categories) and make sure they makes sense. You may want to actually install the patch with sage -combinat install to play around with it and/or create a reviewer patch. Feel free to ask for further help! Best regards, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ --~--~-~--~~~---~--~~ 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 URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Categories restart: call for reviewers
I would like to get more involved with Sage developing, and mathematical sanity check looks like something I can certainly do and a nice way to get started, so I will try to jump into this one. Mind that I haven't been involved with Sage any further than the mail lists so far, so any pointers will be appreciated. Cheers Javier On Aug 19, 11:52 pm, Nicolas M. Thiery nicolas.thi...@u-psud.fr wrote: Dear category fans, David Kohel won't be available in the next two weeks for working on the category review. Is there any volunteer for reviewing (some of the) 40 categories listed under his name on: http://sagetrac.org/sage_trac/wiki/CategoriesCategoriesReview The files are all 100% doctested, and most of them are essentially trivial. So the reviewing work is essentially about their mathematical sanity. For your convenience, the sage code with the sage-combinat patches applied is (experimentally!) browsable from: http://combinat.sagemath.org/hgwebdir.cgi/code/file/tip/sage/categories Alternatively, they can be installed with: sage -combinat install Thanks in advance! Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.nethttp://Nicolas.Thiery.name/ --~--~-~--~~~---~--~~ 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 URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Categories restart: call for reviewers
Hi Javier, On Thu, Aug 20, 2009 at 7:17 PM, javiervengor...@gmail.com wrote: I would like to get more involved with Sage developing, and mathematical sanity check looks like something I can certainly do and a nice way to get started, so I will try to jump into this one. Welcome aboard! At the moment, there is no official quality assurance team with respect to code quality, but any help is appreciated. Mind that I haven't been involved with Sage any further than the mail lists so far, so any pointers will be appreciated. You might find the Developers' Guide helpful: http://www.sagemath.org/doc/developer/index.html It covers topics like coding conventions, using Mercurial to manage patches, and guidelines for things like reviewing other people's patches. The sage-combinat team has written a tutorial on using Mercurial for Sage development, so you might find that helpful: http://wiki.sagemath.org/combinat/MercurialStepByStep If you require more documentation about Mercurial, the official website of Mercurial contains heaps of documentation ranging from short tutorials to full-blown books and of course the standard Mercurial documentation: http://mercurial.selenic.com/wiki/ At Sage Days 16 in Barcelona, Spain, Martin Albrecht gave a talk on how to get started with Sage development. You can find his talk slides at the talks wiki page: http://wiki.sagemath.org/days16 Sage development isn't just about writing computer code in some programming language. You can also help out with translating the Sage tutorial (or some other documentation) to another (human) language. Presently, there are translations of the tutorial in French and Spanish, which you can find here: http://www.sagemath.org/help.html Nathann Cohen has volunteered to help maintain a French mirror of Sage and do more translation work: http://www.sagemath.fr I have recorded some of my experiences in Sage development in the following blog post: http://mvngu.wordpress.com/2009/07/02/getting-started-with-developing-sage/ Yes, I know... Shame on me for promoting myself :-) -- Regards Minh Van Nguyen --~--~-~--~~~---~--~~ 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 URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Categories restart: call for reviewers
Dear category fans, David Kohel won't be available in the next two weeks for working on the category review. Is there any volunteer for reviewing (some of the) 40 categories listed under his name on: http://sagetrac.org/sage_trac/wiki/CategoriesCategoriesReview The files are all 100% doctested, and most of them are essentially trivial. So the reviewing work is essentially about their mathematical sanity. For your convenience, the sage code with the sage-combinat patches applied is (experimentally!) browsable from: http://combinat.sagemath.org/hgwebdir.cgi/code/file/tip/sage/categories Alternatively, they can be installed with: sage -combinat install Thanks in advance! Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ --~--~-~--~~~---~--~~ 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 URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
