[sage-combinat-devel] Question on a doctest
Hi! Working on some patch, I get the following doctest errors in combinat/ sf/dual.py File /mnt/local/king/SAGE/broken/devel/sage-main/sage/combinat/sf/ dual.py, line 185: sage: l(f._to_self_cache) # note: this may depend on possible previous computations! Expected: [([1, 1], [([1, 1], 2), ([2], 1)]), ([2], [([1, 1], 1), ([2], 1)])] Got: [([], [([], 1)]), ([1, 1], [([1, 1], 2), ([2], 1)]), ([2], [([1, 1], 1), ([2], 1)])] ** File /mnt/local/king/SAGE/broken/devel/sage-main/sage/combinat/sf/ dual.py, line 187: sage: l(f._from_self_cache) Expected: [([1, 1], [([1, 1], 1), ([2], -1)]), ([2], [([1, 1], -1), ([2], 2)])] Got: [([], [([], 1)]), ([1, 1], [([1, 1], 1), ([2], -1)]), ([2], [([1, 1], -1), ([2], 2)])] It states that this may depend on possible previous computations. Is there really no work around? Such as, using an object that is not considered in any other doc test? Is the new result correct? Shouldn't both tests better be marked as random? Best regards, Simon -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
Re: [sage-combinat-devel] Re: Categorification of sage/rings/ring.pyx
On Fri, Apr 01, 2011 at 12:07:36AM -0700, Simon King wrote: On 31 Mrz., 21:35, Simon King simon.k...@uni-jena.de wrote: Once again, I forgot to include __init__.py in a patch. I will update it on trac tomorrow. Done. I don't know why, but aparently mercurial will not include an empty file in the patch. So, I filled __init__.py with a comment. Yup; that's a know shortcoming of standard patches. You can request git-style patches by throwing this in your .hgrc: [diff] git=1 Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
[sage-combinat-devel] #11111: Add features to FiniteDimensional(Modules/Algebras)WithBasis
Hi Franco, Florent, ... There are a bunch of patches (in particular from you) on the sage-combinat queue adding features to finite dimensional modules/algebras with basis. I further refactored/added quite some stuff. Do you mind if I take over those patches, merge them together, and try to get them ready for merging into Sage? This includes: echelon_form_of_module_elements-fs.patch fin_dim_algebra_example-fs.patch fin_dim_algebra_radical-fs.patch fin_dim_algebra_center-fs.patch cache-on-radical-nt.patch # to be folded in the two previous ones fin_dim_algebra_radical_char_p-fs.patch bigmess-nt.patch And possibly: module_morphism_function_extend-fh.patch Any others? I got a cool ticket number for that :-) Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
Re: [sage-combinat-devel] Re: sage-combinat queue broken
Hi! On Thu, Mar 31, 2011 at 11:22:18PM -0700, Anne Schilling wrote: On 3/31/11 5:59 PM, Daniel Bump wrote: It seems that your patch has a problem to be applied to the current sage 4.6.2. The patch was tested with 4.7.alphas (because we hope for it to be merged soon). The syntax of classical_crystals.py at the top of the file has changed since 4.6.2. So it doesn't merge. One possibility would be to guard the patch so that it only applies to more recent versions. I'm cc:ing Nicolas to ask his advice. Which patch are you talking about? The #7922 patches (Weyl character rings) did not apply smoothly due to a trivial import conflict with trac_10446_schuetzenberger_involution-as.patch I am writting a quick reviewer patch on #10466 that make them commute. By the way, it avoids importing parent code (RootSystems, WeylGroups) in category code, to reduce risks of import loops. I'll push that in a couple minutes. Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
Re: [sage-combinat-devel] Re: sage-combinat queue broken
On Fri, Apr 01, 2011 at 03:18:04PM +0200, Nicolas M. Thiery wrote: I'll push that in a couple minutes. Done. I used the occasion to polish a tiny bit the corresponding doctests. Please check, and if you are happy, fold and upload on trac. Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
Re: [sage-combinat-devel] #11111: Add features to FiniteDimensional(Modules/Algebras)WithBasis
On Fri, Apr 01, 2011 at 02:48:22PM +0200, Nicolas M. Thiery wrote: Hi Franco, Florent, ... There are a bunch of patches (in particular from you) on the sage-combinat queue adding features to finite dimensional modules/algebras with basis. I further refactored/added quite some stuff. Do you mind if I take over those patches, merge them together, and try to get them ready for merging into Sage? Go for it ! Sorry for not pushing them to their conclusion. Florent -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
