[sage-combinat-devel] Re: Queue on 5.8 -- (mostly) good news
The queue now applies on 5.8. Thanks, Florent! cheers, Hugh On Monday, March 18, 2013 9:09:52 PM UTC-3, Hugh Thomas wrote: Hi! There is only one patch that needs to be rebased in order to apply to 5.8. trac_12876_category-fix_abstract_class-nt-rel11521.patch needs to be rebased over #14254. It looks like this is just be a matter of making a one-line change to the context. (And importing #14254 and its dependencies into the queue.) No rush as far as I am concerned, but I figured since 5.8 has been released, it was worth reporting this. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-combinat-devel] Queue on 5.8 -- (mostly) good news
Hi! There is only one patch that needs to be rebased in order to apply to 5.8. trac_12876_category-fix_abstract_class-nt-rel11521.patch needs to be rebased over #14254. It looks like this is just be a matter of making a one-line change to the context. (And importing #14254 and its dependencies into the queue.) No rush as far as I am concerned, but I figured since 5.8 has been released, it was worth reporting this. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-combinat-devel] Re: rebasing of 12774
Hi! Anne and Mike (and anyone else having this problem) should run sage -combinat qselect. This should fix the problem, which is that your guards are not set properly, so trac_8359-coxeter-groups-permutation-nt.patch is not being applied. cheers, Hugh On Tuesday, February 5, 2013 8:57:42 AM UTC-4, Anne Schilling wrote: Hi Mark, Your patch trac_12774-coxeter-ms.patch does not seem to apply cleanly any longer on sage-5.6: skipping trac_8920-alphabet-vd.patch - guarded by '+disabled,' applying trac_12774-coxeter-ms.patch patching file sage/categories/coxeter_groups.py Hunk #3 FAILED at 469 1 out of 14 hunks FAILED -- saving rejects to file sage/categories/coxeter_groups.py.rej patch failed, unable to continue (try -v) patch failed, rejects left in working dir errors during apply, please fix and refresh trac_12774-coxeter-ms.patch Abort The best would be to get your patch into Sage soon, since the extended weight lattice patch also depends on it ;-) Best, Anne -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-combinat-devel] Re: the queue on 5.7
Hi everyone! The queue applies on 5.7.beta2, and sage starts. cheers, Hugh On Tuesday, January 29, 2013 7:26:48 PM UTC-4, Hugh Thomas wrote: Hi everyone! Sage crashes on startup in 5.7.beta1 with the queue applied, because having branches is broken. This is fixed in #14024, but the line which used to print a line saying what branch you were on, has been removed in the process. I temporarily disabled three patches for 5.7.beta1, because they need rebases. Since you can't use the queue with 5.7.beta1 anyhow, the rebase is obviously not too urgent :). They are: pretty_console_print-EliX-jbp.patch gap3_spkg_doc_link-fh.patch trac_8360_semigroupe-interface-nt.patch cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-combinat-devel] Re: Sanitizing our code (with pyflakes and such)
Nice. Thanks for pointing this out. The problems in quiver_mutation_type are now #14048 (which is ready for review). cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-combinat-devel] the queue on 5.7
Hi everyone! Sage crashes on startup in 5.7.beta1 with the queue applied, because having branches is broken. This is fixed in #14024, but the line which used to print a line saying what branch you were on, has been removed in the process. I temporarily disabled three patches for 5.7.beta1, because they need rebases. Since you can't use the queue with 5.7.beta1 anyhow, the rebase is obviously not too urgent :). They are: pretty_console_print-EliX-jbp.patch gap3_spkg_doc_link-fh.patch trac_8360_semigroupe-interface-nt.patch cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-combinat-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-combinat-devel] the queue on 5.6 (and funny Mercurial behaviour)
Hi! The queue now applies on 5.6. Thanks, Mike Hansen! However, the queue wouldn't apply for me if I manually popped the patches and pushed them again. The reason is that sage ships Mercurial 2.2.2, which in this case is less picky about applying the patches than the Mercurial I have installed (1.9.1). If you find yourself having this problem, you can either upgrade Mercurial, or use sage -hg instead. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/qFbKmbRRs5AJ. 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] Re: sage combinat on 5.5
Hi! The short explanation of the problem is that sage/combinat/some_hopf_algebras/all.py was not importing parking functions from the right place. It should have been using sage.combinat.parking_functions. I have added a patch temporary_parking_import_fix-ht.patch which fixes this. Jean-Baptiste, please feel free to fix the problem however you like and delete my patch. Martin, sage should now run okay with the queue installed. I had trouble replicating this issue, and for a reason that is a bit interesting (I think). The point is that the import statement used to be right; the parking functions files moved. And by default, sage does not clean up the old .py and .pyc files from the old compilations, so they are still sitting in local/lib/python2.7/site-packages/sage/combinat/some_hopf_algebra, and as a result, sage is willing to import from them. If you want sage to remove them when doing the rebuild, you have to tell it to. See #5977. cheers, Hugh On Saturday, January 19, 2013 10:29:20 AM UTC-4, Martin wrote: Hi there, I just installed sage 5.5 from source and then did sage -combinat install But now I get what's reproduced below. :-( What should I do? (upgrade does not work, since sage doesn't start) Martin rubey@convex3:~/sage-5.5$ sage -- | Sage Version 5.5, Release Date: 2012-12-22 | | Type notebook() for the browser-based notebook interface.| | Type help() for help.| -- --- ImportError Traceback (most recent call last) /home/rubey/sage-5.5/local/lib/python2.7/site-packages/IPython/ipmaker.pyc in force_import(modname, force_reload) 61 reload(sys.modules[modname]) 62 else: --- 63 __import__(modname) 64 65 /home/rubey/sage-5.5/local/bin/ipy_profile_sage.py in module() 5 preparser(True) 6 7 import sage.all_cmdline 8 sage.all_cmdline._init_cmdline(globals()) 9 /home/rubey/sage-5.5/local/lib/python2.7/site-packages/sage/all_cmdline.py in module() 12 try: 13 --- 14 from sage.all import * 15 from sage.calculus.predefined import x 16 preparser(on=True) /home/rubey/sage-5.5/local/lib/python2.7/site-packages/sage/all.py in module() 106 107 from sage.coding.all import * -- 108 from sage.combinat.all import * 109 110 from sage.lfunctions.all import * /home/rubey/sage-5.5/local/lib/python2.7/site-packages/sage/combinat/all.py in module() 152 from sidon_sets import sidon_sets 153 -- 154 from some_hopf_algebra.all import * 155 156 #Affine Permutation Group(s) /home/rubey/sage-5.5/local/lib/python2.7/site-packages/sage/combinat/some_hopf_algebra/all.py in module() 1 2 from packed_words import PackedWord, PackedWords 3 from parking_functions import ParkingFunction, ParkingFunctions 4 5 from fqsym import FreeQuasisymmetricFunctions 6 FQSym = FreeQuasisymmetricFunctions ImportError: No module named parking_functions Error importing ipy_profile_sage - perhaps you should run %upgrade? WARNING: Loading of ipy_profile_sage failed. -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/ESt9Q-O9CR8J. 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] Re: Sage-Combinat poster
Hi Nicolas-- On Wednesday, January 16, 2013 10:41:45 AM UTC-4, Nicolas M. Thiery wrote: On Tue, Jan 15, 2013 at 12:45:28PM -0800, Hugh Thomas wrote: Oh, another minor comment, about something I wasn't sure how (or whether) to change. To me, the mention of Kenya and Burkina Faso seems wierd without something more. I would be inclined either to remove it, or to mention something that has happened/is happening there. I totally agree: I was uncomfortable too with naming explicitly a given country without reason. I changed the item to: Sage is free and can be used by students and amateurs, or in low-fund universities in developing countries and elsewhere. I agree that's much better. I would say low-funded, not low-fund. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/4Gw4EKrsdyMJ. 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] Re: Sage-Combinat poster
Hi! You're welcome! It's the kind of thing I enjoy (especially when I should be doing something else). Sound and practical is good (and in fact, you could take out and practical if you wanted -- I also like sound by itself). Sane just sounded odd. I think I now get the idea of mutualization, and I see that you have something a bit more specific in mind than co-operation. To me networking is not quite right -- I think of networking as meaning chatting up people who might give me a job one day. The meaning of pooling is good, but it's a little wierd because it's not quite a dead metaphor. So it really does conjure up pools of liquid for me. This could be avoided by saying something like Knowledge pooling, but that just sounds wierd. I like Knowledge sharing, though it's a bit awkward with the Sharing in the next sentence. How about Collective code development? (It's interesting to me that French distinguishes partage from mutualization -- for the most part, I think we would use sharing for either one in English.) cheers, Hugh On Saturday, January 12, 2013 11:44:33 AM UTC-4, Nicolas M. Thiery wrote: Dear Sage-Combinat devs, I have been longing for a while for a Sage-Combinat poster to be used at various occasions (conferences, labs presentations, ...). And actually Dan Bump would need one by tomorrow for an NSF meeting involving the Sage-Combinat grant. So I started one from an old MuPAD-Combinat poster, and stealing stuff from recent documents written by Anne, Gregg, Dan, ... A first draft is available from the misc server: http://combinat.sagemath.org/misc/file/56964b30bec7/articles/2013-01-17-Poster/main.pdf The sources are in the same directory. Comments and suggestions welcome, in particular for the last column devoted to examples with pictures. In case we decide to keep and update the list of logo, please add the appropriate logos in the PICTURES directory. I probably won't touch the file for the next couple hours, so feel free to hack in. Cheers, Nicolas -- Nicolas M. Thi�ry Isil nth...@users.sf.net javascript: http://Nicolas.Thiery.name/ -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/K7S3gkMeFGEJ. 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] Re: Sage-Combinat poster
Salut Nicolas-- Oh, another minor comment, about something I wasn't sure how (or whether) to change. To me, the mention of Kenya and Burkina Faso seems wierd without something more. I would be inclined either to remove it, or to mention something that has happened/is happening there. cheers, Hugh On Saturday, January 12, 2013 11:44:33 AM UTC-4, Nicolas M. Thiery wrote: Dear Sage-Combinat devs, I have been longing for a while for a Sage-Combinat poster to be used at various occasions (conferences, labs presentations, ...). And actually Dan Bump would need one by tomorrow for an NSF meeting involving the Sage-Combinat grant. So I started one from an old MuPAD-Combinat poster, and stealing stuff from recent documents written by Anne, Gregg, Dan, ... A first draft is available from the misc server: http://combinat.sagemath.org/misc/file/56964b30bec7/articles/2013-01-17-Poster/main.pdf The sources are in the same directory. Comments and suggestions welcome, in particular for the last column devoted to examples with pictures. In case we decide to keep and update the list of logo, please add the appropriate logos in the PICTURES directory. I probably won't touch the file for the next couple hours, so feel free to hack in. Cheers, Nicolas -- Nicolas M. Thi�ry Isil nth...@users.sf.net javascript: http://Nicolas.Thiery.name/ -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/bbFMXYbqzhgJ. 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] Re: The queue on 5.6.beta2
Hi! I think it would be difficult to get the queue to run on 5.6.beta2 without rebasing Nicolas's trac_10193 patch, since it is then used by his functorial patches, and quite a lot of other patches depend on them. My suggestion would be not to worry about it until Nicolas has had a chance to do the rebase -- so far as I know, no one is clamouring to do combinat development on the 5.6 beta's. ** Christian, it turns out I missed a hunk from 8327 which needed to be removed (because it now appears in one of 13727/13728), so the queue didn't apply on 5.5 after you imported 13727 and 13728. I have removed it from 8327 now. I hope that's okay. cheers, Hugh On Sunday, January 6, 2013 12:43:36 PM UTC-4, Christian Stump wrote: Hi, I wasn't able to get the queue running on 5.6.beta2 here - but I hope I didn't introduce too many new problems trying... @Travis: did you introduce #+5_6_beta1, 10193_rebase ? This way, one cannot install the combinat queue anymore since sage -combinat qselect doesn't understand this guard... Sorry for possible mistakes, Christian -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/rodeB0Llm1cJ. 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] Re: The queue on 5.6.beta2
Hi Anne-- I have disabled the 13742 patches. 5.5 should work fine now with the queue applied. cheers, Hugh On Friday, January 4, 2013 12:06:45 PM UTC-4, Hugh Thomas wrote: Hi everyone! Below are the results of my attempt to apply the queue on 5.6.beta2. Nicolas: trac_10193-graded_enumerated_sets-nt.patch needs to be rebased over #13742 (Nathann's ticket about the permutations code), which needs to be added into the queue. Also, category-symmetric_groups-nt.patch needs a trivial rebase over #13366 Travis: trac_8392-check_permutation-ts.patch also needs to be rebased over #13742. Christian: trac_8327_universal_cyclotomic_field-cs.patch needs to be rebased over your patches #13727 and #13728, which also need to be added into the queue. (Unless I'm mistaken, the rebase just amounts to deleting the corresponding hunks from trac_8327.) Florent: gap3_spkg_doc_link-fh.patch needs what may be a trivial rebase over #13211 (GAP upgrade). cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/_mv-zUto7RsJ. 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] conflict between pretty_console_print-EliX-jbp and trac_12719 patches
Hi! There is a conflict between the pretty_console_print-EliX-jbp patch and the trac_12719 patches (upgrading IPython). I disabled the trac_12719 patches for now, since they are at the very bottom of the queue. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/CqSGu8aG5IoJ. 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] Re: The queue on 5.6.beta2
Hi Anne-- Sorry about the commas. It looks to me like your guards might be set wrong. I would try running sage -combinat qselect and then try reapplying the queue. Or, of you prefer, you can look at/edit your .hg/guards file directly. It seems to me that disabled must have gotten in there, because otherwise, why would the 13742 patches still be being applied? cheers, Hugh On Sunday, January 6, 2013 5:57:43 PM UTC-4, Anne Schilling wrote: Hi Hugh, Thanks, but it does not work for me (even after removing the commas that appeared before the #+disabled). applying trac_13728-some_standard_methods_for_fields-cs.patch applying trac_12587-simplicial_complex_hash-ts.patch applying trac_12587-simplicial_complex_hash_review-cs.patch applying trac_12587-ref-jhp.patch applying trac_13742.patch applying trac_13742_reviewer1.patch applying general_dihedral_group_fix.patch applying trac_13727_dict_addition_doc-cs.patch applying trac_13119_apply_module_morphism_bugfix-mz.patch applying trac_13403-bijection_KR_crystals_tableaux-ts.patch applying trac_13762_k_quotient.patch applying trac_13074-tuples-of-tableaux-am.patch applying trac_12518-enumerated_set_from_iterator-vd.patch skipping trac_13579-temporarily_disable_cmdline_tests_for_security-nt.patch - guarded by '+5_4' applying trac_13911-doctests.patch applying trac12215_weak_cached_function-sk.patch patching file sage/misc/cachefunc.pyx Hunk #4 succeeded at 348 with fuzz 2 (offset 0 lines). applying trac12215_segfault_fixes.patch applying trac_13460-RC_spinor-ts.patch applying trac_13840-integer_list_speedup-ts.patch applying trac_10193-graded_enumerated_sets-nt.patch patching file sage/combinat/integer_vector_weighted.py Hunk #1 FAILED at 0 Hunk #4 FAILED at 199 2 out of 4 hunks FAILED -- saving rejects to file sage/combinat/integer_vector_weighted.py.rej patch failed, unable to continue (try -v) patch failed, rejects left in working dir errors during apply, please fix and refresh trac_10193-graded_enumerated_sets-nt.patch Best, Anne On 1/6/13 11:16 AM, Hugh Thomas wrote: Hi Anne-- I have disabled the 13742 patches. 5.5 should work fine now with the queue applied. cheers, Hugh On Friday, January 4, 2013 12:06:45 PM UTC-4, Hugh Thomas wrote: Hi everyone! Below are the results of my attempt to apply the queue on 5.6.beta2. Nicolas: trac_10193-graded_enumerated_sets-nt.patch needs to be rebased over #13742 (Nathann's ticket about the permutations code), which needs to be added into the queue. Also, category-symmetric_groups-nt.patch needs a trivial rebase over #13366 Travis: trac_8392-check_permutation-ts.patch also needs to be rebased over #13742. Christian: trac_8327_universal_cyclotomic_field-cs.patch needs to be rebased over your patches #13727 and #13728, which also need to be added into the queue. (Unless I'm mistaken, the rebase just amounts to deleting the corresponding hunks from trac_8327.) Florent: gap3_spkg_doc_link-fh.patch needs what may be a trivial rebase over #13211 (GAP upgrade). cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/lx8trCY7jRIJ. 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] Re: The queue on 5.6.beta2
Correction to my previous, the current guards are stored in .hg/patches/guards, not .hg/guards, according to the Mercurial book. cheers, Hugh On Sunday, January 6, 2013 6:54:01 PM UTC-4, Hugh Thomas wrote: Hi Anne-- Sorry about the commas. It looks to me like your guards might be set wrong. I would try running sage -combinat qselect and then try reapplying the queue. Or, of you prefer, you can look at/edit your .hg/guards file directly. It seems to me that disabled must have gotten in there, because otherwise, why would the 13742 patches still be being applied? cheers, Hugh On Sunday, January 6, 2013 5:57:43 PM UTC-4, Anne Schilling wrote: Hi Hugh, Thanks, but it does not work for me (even after removing the commas that appeared before the #+disabled). applying trac_13728-some_standard_methods_for_fields-cs.patch applying trac_12587-simplicial_complex_hash-ts.patch applying trac_12587-simplicial_complex_hash_review-cs.patch applying trac_12587-ref-jhp.patch applying trac_13742.patch applying trac_13742_reviewer1.patch applying general_dihedral_group_fix.patch applying trac_13727_dict_addition_doc-cs.patch applying trac_13119_apply_module_morphism_bugfix-mz.patch applying trac_13403-bijection_KR_crystals_tableaux-ts.patch applying trac_13762_k_quotient.patch applying trac_13074-tuples-of-tableaux-am.patch applying trac_12518-enumerated_set_from_iterator-vd.patch skipping trac_13579-temporarily_disable_cmdline_tests_for_security-nt.patch - guarded by '+5_4' applying trac_13911-doctests.patch applying trac12215_weak_cached_function-sk.patch patching file sage/misc/cachefunc.pyx Hunk #4 succeeded at 348 with fuzz 2 (offset 0 lines). applying trac12215_segfault_fixes.patch applying trac_13460-RC_spinor-ts.patch applying trac_13840-integer_list_speedup-ts.patch applying trac_10193-graded_enumerated_sets-nt.patch patching file sage/combinat/integer_vector_weighted.py Hunk #1 FAILED at 0 Hunk #4 FAILED at 199 2 out of 4 hunks FAILED -- saving rejects to file sage/combinat/integer_vector_weighted.py.rej patch failed, unable to continue (try -v) patch failed, rejects left in working dir errors during apply, please fix and refresh trac_10193-graded_enumerated_sets-nt.patch Best, Anne On 1/6/13 11:16 AM, Hugh Thomas wrote: Hi Anne-- I have disabled the 13742 patches. 5.5 should work fine now with the queue applied. cheers, Hugh On Friday, January 4, 2013 12:06:45 PM UTC-4, Hugh Thomas wrote: Hi everyone! Below are the results of my attempt to apply the queue on 5.6.beta2. Nicolas: trac_10193-graded_enumerated_sets-nt.patch needs to be rebased over #13742 (Nathann's ticket about the permutations code), which needs to be added into the queue. Also, category-symmetric_groups-nt.patch needs a trivial rebase over #13366 Travis: trac_8392-check_permutation-ts.patch also needs to be rebased over #13742. Christian: trac_8327_universal_cyclotomic_field-cs.patch needs to be rebased over your patches #13727 and #13728, which also need to be added into the queue. (Unless I'm mistaken, the rebase just amounts to deleting the corresponding hunks from trac_8327.) Florent: gap3_spkg_doc_link-fh.patch needs what may be a trivial rebase over #13211 (GAP upgrade). cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/-bw_kp8IMLYJ. 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] Re: The queue on 5.6.beta2
Thanks, Travis and Christian! Christian, it looks like your patch trac_11187-finite_reflection_groups-cs.patch imports UCF on sage startup, which means that removing UCF meant sage wouldn't start with the queue applied. This was affecting all versions, not just 5.6 betas, so I went ahead and reinstated your UCF patch with the parts from #13727 and #13728 removed. Feel free to resolve this whatever way you like in the longer term, of course. cheers, Hugh On Friday, January 4, 2013 8:06:45 AM UTC-8, Hugh Thomas wrote: Hi everyone! Below are the results of my attempt to apply the queue on 5.6.beta2. Nicolas: trac_10193-graded_enumerated_sets-nt.patch needs to be rebased over #13742 (Nathann's ticket about the permutations code), which needs to be added into the queue. Also, category-symmetric_groups-nt.patch needs a trivial rebase over #13366 Travis: trac_8392-check_permutation-ts.patch also needs to be rebased over #13742. Christian: trac_8327_universal_cyclotomic_field-cs.patch needs to be rebased over your patches #13727 and #13728, which also need to be added into the queue. (Unless I'm mistaken, the rebase just amounts to deleting the corresponding hunks from trac_8327.) Florent: gap3_spkg_doc_link-fh.patch needs what may be a trivial rebase over #13211 (GAP upgrade). cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/d-mmN31BUH4J. 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] The queue on 5.6.beta2
Hi everyone! Below are the results of my attempt to apply the queue on 5.6.beta2. Nicolas: trac_10193-graded_enumerated_sets-nt.patch needs to be rebased over #13742 (Nathann's ticket about the permutations code), which needs to be added into the queue. Also, category-symmetric_groups-nt.patch needs a trivial rebase over #13366 Travis: trac_8392-check_permutation-ts.patch also needs to be rebased over #13742. Christian: trac_8327_universal_cyclotomic_field-cs.patch needs to be rebased over your patches #13727 and #13728, which also need to be added into the queue. (Unless I'm mistaken, the rebase just amounts to deleting the corresponding hunks from trac_8327.) Florent: gap3_spkg_doc_link-fh.patch needs what may be a trivial rebase over #13211 (GAP upgrade). cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/LhDZPtzRohIJ. 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] Re: sage-5.5
Hi Anne-- It looks #12215 had a positive review on trac at one point (4 months ago), so that's probably the explanation for its location in the series file. Recently (before the conflict between 13762 and 13605) , the queue did apply if trac12215_segfault_fixes.patch was disabled, and sage ran, though I don't know if that's the best plan. Part of what was in trac12215_segfault_fixes.patch is now being done by #13741, so segfault_fixes needs to be rebased over it. This seems like it might just be a matter of removing the obvious hunks from segfault_fixes, but I don't really know what's going on with this stuff. cheers, Hugh On Thursday, December 27, 2012 9:32:17 AM UTC-8, Anne Schilling wrote: Hi All! sage-combinat does not seem to apply to sage-5.5: Applying all the patches hg --config 'extensions.hgext.mq=' --config 'ui.username=sage-combinat script' qpush -a applying trac_12930-add_mt_lattice-as.patch skipping trac_13579-temporarily_disable_cmdline_tests_for_security-nt.patch - guarded by '+5_4' applying trac12215_weak_cached_function-sk.patch patching file sage/misc/cachefunc.pyx Hunk #4 succeeded at 348 with fuzz 2 (offset 0 lines). applying trac12215_segfault_fixes.patch patching file sage/all.py Hunk #1 FAILED at 232 1 out of 1 hunks FAILED -- saving rejects to file sage/all.py.rej patching file sage/categories/action.pyx Hunk #1 succeeded at 87 with fuzz 1 (offset 0 lines). patching file sage/libs/pari/gen.pyx Hunk #1 FAILED at 9127 1 out of 1 hunks FAILED -- saving rejects to file sage/libs/pari/gen.pyx.rej patch failed, unable to continue (try -v) patch failed, rejects left in working dir errors during apply, please fix and refresh trac12215_segfault_fixes.patch Abort Ticket #12215 does not seem to have positive review on trac. Why is it in this category in the queue? Best, Anne -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/l6dw4w6vPP8J. 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: state of the queue: 5.4, 5.5.beta0
Hi Christian-- The queue applies fine for me on plain 5.5.rc0. Maybe your guards are not set correctly? This is what is usually the problem for me when the queue seems to have suddenly gone wonky. If that is the case, it can be fixed in one step by running: sage -combinat qselect. cheers, Hugh On Saturday, November 24, 2012 2:34:06 AM UTC-8, Christian Stump wrote: Hi, Thanks for doing this for me Travis and Nicolas! I've just synced and everything is fine. I now have again a reliable connection to test the queue. Unfortunately, it still didn't work for me to install sage combinat on a plain 5.5.rc0. I had to disable Travis' 12587 due to tons of conflicts and to update my new version of the universal cyclotomics (which hopefully make it into main sage soon, thanks to Frédéric!), and then it worked again. Since others didn't have this problem, I don't update the queue as long as Travis doesn't ask me to do so (I also tent to make mistakes in the process, so it might me my fault)... Best, Christian -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/nVFxA_yQmfYJ. 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] Partition options and cleanup patch
Hi! FYI, further rebasing of tableaux-combinatorics-am.patch seems to be needed. I'm going to disable it temporarily so the queue applies. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/gQVugDxP2WcJ. 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] state of the queue: 5.4, 5.5.beta0
Hi! To the best of my knowledge, the queue is fine for any version of 5.4 (including the released version). (Please complain about any issues below.) For 5.5.beta0, there are some issues. Nicolas: trac_12876_category-fix_abstract_class-nt-rel11521.patch needs to be rebased over trac_11521_callback.patch (which isn't in the queue, unlike the other 11521 patch). Travis: trac_12587-simplicial_complex_hash-ts.patch needs to be rebased over 13590 (easy -- I could take care of it if you want). Otherwise it looks good. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/0_waFH-tl4QJ. 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] Partition options and cleanup patch
Thanks, Travis and Andrew, for the rebasing and the explanations. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/Sc6RpTfMtYsJ. 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] Partition options and cleanup patch
Hi-- The patch kshape-om.py now produces an import error at Sage startup (cannot import name Partition_class). I'm guessing this has to do with Travis's work on partitions. I have disabled it for now. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/xq1Yq771PqkJ. 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] Partition options and cleanup patch
Hi! Florent's patch partition_leg_length_speedup-fh.patch no longer applies over trac_13605-partition_options-ts.patch. The relevant change is just to the format of a raise ValueError, so it would be easy enough either not to make the change in 13605, or to rebase Florent's patch. cheers, Hugh On Thursday, November 8, 2012 10:25:42 AM UTC-8, Nicolas M. Thiery wrote: On Thu, Nov 08, 2012 at 10:04:17AM -0800, Travis Scrimshaw wrote: For doing the ordering option, how do we want to compare two elements with different ordering on parents? In particular if we do ordering using the left argument, we'd have (this is not yet in the queue): sage: P = Partitions(order=lex)([3, 3]) sage: Q = Partitions(order=dominance)([4, 1, 1]) sage: P Q True # if compared with lex sage: Q P False # if compared with dominance Should we just return False in both cases or default back to lex ordering? The easiest option seems to be is leave it as is, where everything using comparison operators is lex and to check dominance, you call P.dominate(Q) with large amounts of documentation and warnings about this. Thoughts? If it was just for me, I would forbid to compare with '' two objects with different parents (possibly with some well chosen exceptions like 1/2 1). In other words: if you get into a situation where you have a serious doubt about the semantic (and thus probably even more so for the caller), I vote for just raising an exception. That's the safest. Thoughts anyone else? Cheers, Nicolas -- Nicolas M. Thi�ry Isil nth...@users.sf.net javascript: http://Nicolas.Thiery.name/ -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/psTugEibIkMJ. 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] Partition options and cleanup patch
Hi Travis-- Also, you seem to have incorporated the (unique, small) change from partition_speedup_jb.patch, so it doesn't apply either. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/S3UhtLRpKXkJ. 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] Partition options and cleanup patch
Hi! tableaux-combinatorics-am.patch needs to be rebased on top of Travis's patch trac_13605-partition_options-ts.patch. (Andrew's patch edits some doctests that Travis has removed, and there are some changes to import statements -- nothing looks very complicated.) cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/_TD2JHTQhmAJ. 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] Re: finite_semigroup-rebase-cs.patch needs a rebase
Done (with Christian's permission). cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/Ql50LgCf50sJ. 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: Don't use combinat with 5.4.rc2 (fixed)
Hi Mike-- Sorry, I was away from email for a few days. 9265 was merged in 5.4.beta1; it then got unmerged again. So the guards should be set so neither of those patches would get applied to 5.4.beta1. If you didn't run sage -combinat update explicitly, but are just using hg to pull patches, then your guards may not be set right; you should either run sage -combinat update or else add 5_4_rc2 to your sage-xxx/devel/sage-combinat/.hg/patches/guards file. For me, at the moment, the queue applies smoothly on 5.4.beta1, so maybe the further problem you encountered was some temporary glitch. (Unless someone fixed it in the meantime?) cheers, Hugh On Wednesday, October 24, 2012 1:18:53 PM UTC-7, Mike Zabrocki wrote: Hi, I disabled both of these patches and then I run into trac_12876_category-fix_abstract_class-nt-rel11521.patch doesn't apply. It doesn't look like these patches touch the same files, but this patch hasn't been touched in a few months so something must be conflicting. Any ideas? I'm compiling 5.4.rc2 now, but that will take a while. -Mike On Wednesday, 24 October 2012 14:23:18 UTC-4, Mike Zabrocki wrote: Hi, Something went wrong here for me using 5.4.beta1. The lines in the series files are: trac_9265_tableaux_categories_am.patch #+5_4_beta0 trac_9265_tableaux_categories_am-duplicate.patch#-5_4_rc2 Are those right? I'd like to push some changes but I don't want to mess things up with this patch. -Mike On Tuesday, 23 October 2012 02:10:18 UTC-4, Hugh Thomas wrote: You're welcome. It's actually quite fun (in a somewhat perverse way). After having set things up as I did, I realized it woud be even cleaner if I could simply have two different lines in the series file pointing to the same patch, but, alas, mercurial doesn't let you do that. cheers, Hugh On Monday, October 22, 2012 8:54:51 AM UTC-7, Nicolas M. Thiery wrote: On Sat, Oct 20, 2012 at 01:13:23AM -0700, Hugh Thomas wrote: I think this is now fixed, by introducing a second copy of trac_9265_tableaux_categories_am.patch which is guarded so it will only be applied to 5.4.rc2 or later. Ah yes, that works! This should mean that the queue will apply cleanly against 5.4 and all its prerelease versions. Thanks for going the extra mile for our devs :-) Cheers, Nicolas -- Nicolas M. Thi�ry Isil nth...@users.sf.net http://Nicolas.Thiery.name/ -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/4zvZ1dQohWYJ. 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: Don't use combinat with 5.4.rc2 (fixed)
You're welcome. It's actually quite fun (in a somewhat perverse way). After having set things up as I did, I realized it woud be even cleaner if I could simply have two different lines in the series file pointing to the same patch, but, alas, mercurial doesn't let you do that. cheers, Hugh On Monday, October 22, 2012 8:54:51 AM UTC-7, Nicolas M. Thiery wrote: On Sat, Oct 20, 2012 at 01:13:23AM -0700, Hugh Thomas wrote: I think this is now fixed, by introducing a second copy of trac_9265_tableaux_categories_am.patch which is guarded so it will only be applied to 5.4.rc2 or later. Ah yes, that works! This should mean that the queue will apply cleanly against 5.4 and all its prerelease versions. Thanks for going the extra mile for our devs :-) Cheers, Nicolas -- Nicolas M. Thi�ry Isil nth...@users.sf.net javascript: http://Nicolas.Thiery.name/ -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/BNo8pwpY9qcJ. 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] Don't use combinat with 5.4.rc2 (for now)
Hi! Because 9265 got unmerged, the queue will not apply properly to 5.4.rc2. The fix for this would break the queue for the earlier 5.4 betas/rc's. The solution proposed by Nicolas on 9265 is to hold off on fixing this until 5.4 is released (likely in a few days) and then at that point cease supporting the earlier prerelease versions of 5.4. So for now, don't try to install the queue on 5.4.rc2. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/mxh3b8ot3y8J. 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] trac_5294--improving_pickle_jar_documentation-am.patch doesn't apply against new-ish versions
Hi Andrew-- trac_5294 doesn't apply for me against 5.4.rc1 or 5.4.beta2. It needs to be rebased over 13123, which was merged in 5.4.beta2. But in fact, maybe it makes more sense not to include 5294 in the queue. The files it touches are not files that the combinat queue is messing with, so I don't see a benefit, and in order to have it in the queue, it would be necessary to import 13123 into the queue. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/qOERo5t25i0J. 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] Re: Don't use combinat with 5.4.rc2 (for now)
Hi! I think this is now fixed, by introducing a second copy of trac_9265_tableaux_categories_am.patch which is guarded so it will only be applied to 5.4.rc2 or later. This should mean that the queue will apply cleanly against 5.4 and all its prerelease versions. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/9z7I7f_-kV8J. 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] Re: the queue applies on 5.4.beta2 and 5.4.rc0
FYI, the queue also applies to 5.4.rc1. cheers, Hugh On Monday, October 1, 2012 12:07:19 AM UTC-7, Hugh Thomas wrote: Hi everyone! The queue now applies on 5.4.beta2 and 5.4.rc0. Christian, your patch concrete_combinatorial_statistics_and_maps-cs.patch needs to be rebased over #13431 (which is not in the queue but was merged into 5.4.beta2). In the meantime, I guarded it so it isn't applied to 5.4.beta2 or 5.4.rc0. Florent, your patch trac_8703-trees-fh.patch needs to be rebased over #5160 (which renames the file sage/misc/sagex_ds and makes some minor markup changes, some of which coincide with yours). I have guarded this patch, and the patches that depend on it, so that they are not applied against 5.4.rc0. Frédéric, among the patches relying on Florent's 8703 are some of yours. Andrew, I rebased 13072 over 11442 and 11446 (and imported them). cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/g9Cvqu7QzRwJ. 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] the queue applies on 5.4.beta2 and 5.4.rc0
Hi everyone! The queue now applies on 5.4.beta2 and 5.4.rc0. Christian, your patch concrete_combinatorial_statistics_and_maps-cs.patch needs to be rebased over #13431 (which is not in the queue but was merged into 5.4.beta2). In the meantime, I guarded it so it isn't applied to 5.4.beta2 or 5.4.rc0. Florent, your patch trac_8703-trees-fh.patch needs to be rebased over #5160 (which renames the file sage/misc/sagex_ds and makes some minor markup changes, some of which coincide with yours). I have guarded this patch, and the patches that depend on it, so that they are not applied against 5.4.rc0. Frédéric, among the patches relying on Florent's 8703 are some of yours. Andrew, I rebased 13072 over 11442 and 11446 (and imported them). cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/woSXTzMr8BYJ. 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] Re: the queue applies on 5.4.beta2 and 5.4.rc0
You're welcome! cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/14QmpSVG62sJ. 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] Re: 5.4.beta2 and tableaux
On Saturday, September 29, 2012 4:35:32 PM UTC-7, Hugh Thomas wrote: Hi everyone (especially Andrew)-- trac_13072-tuples-of-partitions_am.patch doesn't apply on 5.4.beta2, because of #11442, which is not in the queue but touches partition.py. I guess it will be necessary to import 11442, and refactor 13072 on top of it. This will be trivial and I don't mind doing it if you like, Andrew. Another relevant patch has been merged in 5.4.rc0: #11446. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/79lXbkwELYkJ. 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] 5.4.beta2 and tableaux
Hi everyone (especially Andrew)-- trac_13072-tuples-of-partitions_am.patch doesn't apply on 5.4.beta2, because of #11442, which is not in the queue but touches partition.py. I guess it will be necessary to import 11442, and refactor 13072 on top of it. This will be trivial and I don't mind doing it if you like, Andrew. I am also in no particular rush, I just had some time today and wondered how the queue was doing on 5.4.beta2. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/5A1KAzZTvNIJ. 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] 5.4.beta2 and partitions
Sorry, got the subject of the discussiong wrong: it should be and partitions. -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/MY0_y45iFsUJ. 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 working on 5.4.beta1
I should perhaps mention that I think the problem I reported was due to a different ticket (but similar circumstances): trac_9265_tableaux_categories_am. (This is not relevant to the policy discussion, but might be relevant to restoring the queue to maximal sanity.) cheers, Hugh On Wednesday, September 26, 2012 7:27:36 AM UTC-7, Nicolas M. Thiery wrote: Hi Anne, Jeroen, On Wed, Sep 26, 2012 at 07:10:13AM -0700, Anne Schilling wrote: Lesson to be learned: please everybody refrain from modifying a patch in a ticket that is in the closed state; instead, create a new ticket! The merge manager forces us to do so. I do not think this is our choice. Jeroen did not change the ticket status to needs work which I think he would have if his intention was for the change to happen on that ticket. This seems like more work for him (having to unmerge/remerge the ticket) and for us (having Sage beta's with various versions of the ticket merged in). Ok, I just asked for clarification on #5457. Cheers, Nicolas -- Nicolas M. Thi�ry Isil nth...@users.sf.net javascript: http://Nicolas.Thiery.name/ -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/DFyMNpU6YCwJ. 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] Re: Sage-Combinat queue working on 5.4.beta1
Thanks, Nicolas -- the queue is now applying properly for me (on 5.4.beta1). cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/BpS9PJvI1OoJ. 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] implementation of cluster algebras
Hi! Christian Stump and Gregg Musiker have written code implementing many methods related to cluster algebras. This spans several tickets. The first substantial one is #10527. I have reviewed it and am willing to give it a positive review for correctness. I have not done a lot of Sage development, so I would be happy if someone else were to take a look at the design aspects, but if no one leaps in (or expresses an intention to do so), I will set a positive review myself. The version in the combinat queue is not quite up-to-date, so if you want to take a close look, please look at the version on the trac server. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/JyrniMznNvIJ. 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] Re: sage 5.2.rc0
FYI, the next glitch is a trivial rebase of 12215_segfault_fixes.patch over trac_5457-symmetric_functions-mz.patch. 12215 is needed in order to get a bunch of the category patches to apply. cheers, Hugh On Sunday, July 22, 2012 5:46:40 PM UTC+9, Martin wrote: I just compiled successfully sage 5.2.rc0 (with an install of the openssl pkg in the middle). However, the queue doesn't apply: patching file sage/groups/perm_gps/permgroup.py Hunk #1 FAILED at 279 1 out of 1 hunks FAILED -- saving rejects to file sage/groups/perm_gps/permgroup.py.rej patching file sage/groups/perm_gps/permgroup_element.pyx Hunk #1 FAILED at 173 1 out of 1 hunks FAILED -- saving rejects to file sage/groups/perm_gps/permgroup_element.pyx.rej patch failed, unable to continue (try -v) patch failed, rejects left in working dir errors during apply, please fix and refresh trac_13169-permgroup_doctests-nt.patch Abort Martin -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/tfxIVoURAMgJ. 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] Re: queue broken
The queue is applying to 5.0 fine for me. -Hugh On Thursday, July 12, 2012 9:46:15 PM UTC+3, Anne Schilling wrote: Hi! The patch queue is currently broken with sage-5.1. Nicolas claims that he fixed this before lunch, so Chris, did you make changes since that break the queue? Thanks, Anne -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/ZBgzO-vXl4AJ. 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] Re: Merging issue
Hi Andrew-- I think the problem is that there is no problem! When you updated after making your changes, mercurial updated your repository by merging your version with the most current version on the server. Then when you pushed, the server was updated to that updated version as well. (The merging can generally be handled in an entirely automatic way because everyone only edits their own patches, so the only file where there could be conflicts would be the series file.) (One of the actual experts can correct me if I am wrong...) cheers, Hugh On Thursday, July 12, 2012 2:35:07 AM UTC+3, Andrew Mathas wrote: Hi All, Sorry for breaking the queue last week. I am trying not to break it again but whenever I push a patch to the server merging returns the error message abort: branch 'default' has one head - please merge with an explicit rev I am not if I am missing something in my commit process and I don't know where to find the revision number to complete the merge. The log of my commit is below. Could some one please set me straight? I am not able to read sage-combinat directly at the moment (I'm behind the great firewall of China), so if you could cc any reply to me directly that would be appreciated. Cheers, Andrew --- How I am committing: I am following the instruction on wiki.sagemath.org/combinat/MercurialStepByStep#Pushing_patches_to_the_sage-combinat_server After first running sage -combinat update -fsage -hg qpush -asage -br testing my files and updating again I did the following: 730-patches: sage -hg push pushing to http://combinat.sagemath.org/patches/ searching for changes remote: adding changesets remote: adding manifests remote: adding file changes remote: added 1 changesets with 3 changes to 3 files 731-patches: sage -hg pull -u pulling from http://combinat.sagemath.org/patches/ searching for changes no changes found 732-patches: sage -hg merge abort: branch 'default' has one head - please merge with an explicit rev (run 'hg heads' to see all heads) sage reports that there is only one head. Presumably the real head is on the server. 733-patches: hg heads changeset: 7117:9f35e096afe6 tag: tip user:Andrew Mathas andrew.mathas at sydney.edu.au date:Thu Jul 12 07:19:32 2012 +0800 summary: updating PartitionTuple code -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/X-VyGQgT2gIJ. 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] Re: sage-5.1.rc1
Hi Nicolas, hi Christian, Mike, and Andrew (whose patches I guarded)-- Nicolas, I added the guard +sage_5_1_rc1 on the three patches which don't apply to sage-5.1.rc1, but this guard does not get selected by someone running sage-5.0. (Andrew pointed this out, and I have the same experience with my copy of 5.0.) What's up? Is there something else I need to do so that the -combinat update script knows about the existence of release 5.1? Christian, Mike, Andrew: sorry to have guarded your patches a bit too effectively. If you need to unguard them, I doubt there are many people clamoring to install the combinat queue on 5.1 urgently. Andrew: thanks very much for pointing out the problem to me! cheers, Hugh On Tuesday, July 10, 2012 3:17:28 AM UTC+3, Hugh Thomas wrote: Hi! In order to avoid doing useful things, I took a look at what happens when you try to apply the queue to sage-5.1.rc1 (which is presumably close to what sage-5.1 will be). The patches which don't apply are: trac_12876_category-fix_abstract_class-nt-rel11521.patch #-sage_5_0 depends on #715, #11521, #12875, #12877, #12215 trac_12876_category-fix_abstract_class-nt-rel11521-review-nt.patch #-sage_5_0 depends on #715, #11521, #12875, #12877, #12215 concrete_combinatorial_statistics_and_maps-cs.patch pp_function_for_dyck_words-mz.patch trac_13072-tuples-of-partitions_am.patch However, if you guard out these patches, sage doesn't load, so I guess there is some rebasing which will be needed before the queue applies properly. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/tk5Jye1TsZMJ. 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] Re: sage-5.1.rc1
Hi Nicolas-- I thought a bit harder about my question, and checked which guards 5.0 and 5.1 are selecting. My sage 5.0 does not select a guard called 5_1_rc1 or 5_1, which I guess is what it should be doing (using the new format for the guard names). I could fix that for myself using qselect, but is there any way I can fix that for everyone? (And I should also update the name of the guard in the series file; I used the name you suggested, which is in the old format.) cheers, Hugh On Wednesday, July 11, 2012 11:30:11 AM UTC+3, Hugh Thomas wrote: Hi Nicolas, hi Christian, Mike, and Andrew (whose patches I guarded)-- Nicolas, I added the guard +sage_5_1_rc1 on the three patches which don't apply to sage-5.1.rc1, but this guard does not get selected by someone running sage-5.0. (Andrew pointed this out, and I have the same experience with my copy of 5.0.) What's up? Is there something else I need to do so that the -combinat update script knows about the existence of release 5.1? Christian, Mike, Andrew: sorry to have guarded your patches a bit too effectively. If you need to unguard them, I doubt there are many people clamoring to install the combinat queue on 5.1 urgently. Andrew: thanks very much for pointing out the problem to me! cheers, Hugh On Tuesday, July 10, 2012 3:17:28 AM UTC+3, Hugh Thomas wrote: Hi! In order to avoid doing useful things, I took a look at what happens when you try to apply the queue to sage-5.1.rc1 (which is presumably close to what sage-5.1 will be). The patches which don't apply are: trac_12876_category-fix_abstract_class-nt-rel11521.patch #-sage_5_0 depends on #715, #11521, #12875, #12877, #12215 trac_12876_category-fix_abstract_class-nt-rel11521-review-nt.patch #-sage_5_0 depends on #715, #11521, #12875, #12877, #12215 concrete_combinatorial_statistics_and_maps-cs.patch pp_function_for_dyck_words-mz.patch trac_13072-tuples-of-partitions_am.patch However, if you guard out these patches, sage doesn't load, so I guess there is some rebasing which will be needed before the queue applies properly. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/76ftbrFzCe8J. 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] Re: sage-5.1.rc1
Hi Nicolas-- I agree that the (now only two) patches that don't apply to 5.1.rc1 are now applied to 5.0 and guarded from 5.1. Success! (My help probably only made the process longer, but I did learn something.) I edited your explanation in the series file because I think it had typos, including some which were potentially confusing. Please check that what is now there makes sense (when you have a minute). Could you please explain what you did so that now my sage-5.0 sage -combinat update knows to select the 5_1_rc1 guard when before, it didn't? cheers, Hugh On Wednesday, July 11, 2012 5:44:57 PM UTC+3, Nicolas M. Thiery wrote: On Wed, Jul 11, 2012 at 01:30:11AM -0700, Hugh Thomas wrote: Hi Nicolas, hi Christian, Mike, and Andrew (whose patches I guarded)-- Nicolas, I added the guard +sage_5_1_rc1 on the three patches which don't apply to sage-5.1.rc1, but this guard does not get selected by someone running sage-5.0. (Andrew pointed this out, and I have the same experience with my copy of 5.0.) The guard should be ``+5_1_rc1''. Guards of the form ``sage_...'' were used with the sage-combinat script for Sage = 4.8. I just fixed the series, and used the occasion to remove old cruft to avoid future confusion. Please double check, and thanks for investigating! Cheers, Nicolas -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/oXUCkd9KrLwJ. 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] Re: sage-5.1.rc1
Hi Nicolas-- I still have one question (though, in writing this email, I think I may have figured it out for myself). Before you fixed things, if I ran hg qselect in sage-5.0/deve/sage-combinat, then 5_1_rc1 did not appear in the list. After you fixed things, it did appear. What caused that change? I guess the answer is that sage -combinat update looks through the series file, and selects all guards *that appear in the series file* and which are subsequent to the current version. Is that right? (I had assumed that, somewhere, there was a complete list of sage releases which it would consult, so as to know which guards to select, but I guess it is actually much easier just to look through the series file and see what guards are actually being used.) cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/8lHvvdQ5MssJ. 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] Re: sage-5.1.rc1
Hi! The following four patches don't apply to 5.1.rc1, so I have added guards for them. new_sym_categories-fs.patch concrete_combinatorial_statistics_and_maps-cs.patch pp_function_for_dyck_words-mz.patch trac_13072-tuples-of-partitions_am.patch cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/WVyDb5BedOUJ. 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] Re: Patches for PartitionTuples and TableauTuples
Dear Andrew-- Your patch trac_13072-tuples-of-partitions_am.patch does not apply against sage-5.1.rc1 (and presumably for the same reason won't apply against sage-5.1 either). I have added a guard in the series file so that if someone is trying to use the combinat queue with sage-5.1.rc1 or later, your patch won't be applied, but it will be applied as normal for anyone using sage-5.0. There is nothing you need to do about this immediately. In particular, for you, as long as you are using 5.0, what I have done should change nothing. (Please let me know if it did change anything!) At some point, you will want to move to sage-5.1 (at the latest, when the queue stops supporting 5.0), and then, after you have updated to sage-5.1, you will need to see what there is in your patch which doesn't apply to sage-5.1. If this is unclear, or you need further advice about how to proceed, I can try to help, though I am not an expert, or you can ask one of the actual experts. cheers, Hugh On Sunday, July 8, 2012 6:49:57 AM UTC+3, Nicolas M. Thiery wrote: Hi Andrew, I reinstated the queue to its previous sane state. This means that your patches are not there anymore. At this point, you want to reinstall the sage-combinat patches anew, and then reimport your patches. If you don't have a copy under hand, you can grab them from the dead branch: http://combinat.sagemath.org/patches/file/da02b569f34b To reimport them, you can then do from the sage-combinat directory: sage -hg qimport where you saved your patches/...-am.patch sage -hg qpush And then follow the usual update/commit/push cycle. I am a bit puzzled about what went wrong. Everything should be back to normal now, so it's no big deal, but let's investigate a bit to learn from it and see if we need to update the instructions on the wiki, or if it was just a one-time issue. A couple questions: - What version of Sage are/were you using? - When did you last update the sage-combinat queue before merging? - Do you have by any chances a trace of the messages from mercurial? Thanks! 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 view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/kdKt7xH9E2MJ. 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] Re: Sage install party FPSAC
I will be there and am interested. Thanks for bringing this up! cheers, Hugh On Wednesday, June 20, 2012 11:20:17 AM UTC-5, Viviane Pons wrote: Hi everyone, I was wondering if some of you were attending the next FPSAC in Nagoya and would be interested in organizing some informal sage presentations with a sage install party as well. It wouldn't be part of the official software presentations but I'm sure it is possible. As Florent and Nicolas won't be there, we need some sage developers to help and participate. Please let me know who is interested See you Viviane -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/gWqCx1kQNtMJ. 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] Re: symmetric functions
Actually, the patch that I accidentally edited was Martin's not Mike's. My edits seem to have disappeared, which is great. So I think from my point of view everything is copacetic, and I will try to be more careful in the future. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/bYlD5UGUqCsJ. 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] Re: symmetric functions
Hi! Sorry, the reason my patch came up (I think) is that I screwed up something else, and wound up putting something changing cluster_algebras_quivers/quiver_mutation_type.py into Mike's patch. Sorry Mike! I don't know what the best way to fix that is -- it's perfectly fine with me if you just delete that from your patch; I can put it back in my patch where it belongs. Or if you want me to remove it from your patch myself, that's fine with me too -- whatever's easiest for you. Apologies for messing things up -- I (obviously) still do not have all the right habits for working with the combinat queue. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/5LyC4gfw7ncJ. 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] Re: on DyckWords
Hi! I think area, bounce, and dinv are standard terms. Spelling out what dinv means would only confuse matters for me. I don't remember the precise definition --- it is complicated. So even spelling outtwo or three words would still be only be able to give an imprecise description. That being the case, I think the best thing is to use the standard term. cheers, Hugh On Thursday, May 17, 2012 5:45:19 AM UTC-3, Christian Stump wrote: Hi, I am currently working on filling the wiki at www.findstat.org with more data, since Chris Berg and I are going to present it at the FPSAC this summer. I would like to make the following changes to Dyck words: 1. changing a-statistic, b-statistic, d-statistic to area, bounce, dinv (and leaving the old with a warning). 2. changing the to_partition to return the partition when cutting out the path above the diagonal (currently, the transposed is returned). Is that okay with everyone? Christian -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/XkUWwReNbD8J. 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] Re: queue broken
Sorry! I should have been aware that I should check for conflicts. I will be more careful in the future! -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/YfUgVwQ1y8UJ. 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] Re: queue doesn't apply to 5.0.rc0
It now applies fine for me on 5.0.rc0 too. Thanks, Nicolas! cheers, Hugh On Saturday, May 5, 2012 6:27:38 PM UTC-3, Hugh Thomas wrote: Hi! On a clean copy of 5.0.rc0, I get a rejection at move_iet_into_dynamics-vd.patch. applying move_iet_into_dynamics-vd.patch patching file sage/combinat/iet/iet.py Hunk #1 FAILED at 0 1 out of 1 hunks FAILED -- saving rejects to file sage/combinat/iet/iet.py.rej patch failed, unable to continue (try -v) patch failed, rejects left in working dir errors during apply, please fix and refresh move_iet_into_dynamics-vd.patch It looks to me like the patch is removing a file iet.py which doesn't exist. cheers, Hugh -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To view this discussion on the web visit https://groups.google.com/d/msg/sage-combinat-devel/-/VCB69DzENOcJ. 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] problem building documentation caused by installing combinat
Hi!
I am running sage 4.7. If I install combinat, and build
documentation, then switch back to the main branch and rebuild the
documentation, I get an error:
Specifically, running:
sage -b main
sage -docbuild reference html
I get:
sphinx-build -b html -d /home/hugh/sage-4.7-clean/devel/sage/doc/
output/doctrees/en/reference/home/hugh/sage-4.7-clean/devel/sage/
doc/en/reference /home/hugh/sage-4.7-clean/devel/sage/doc/output/html/
en/reference
Running Sphinx v1.0.4
loading pickled environment... done
building [html]: targets for 905 source files that are out of date
updating environment: 0 added, 1 changed, 0 removed
reading sources... [100%] sage/schemes/generic/
toric_variety
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
writing output... [ 13%] sage/categories/examples/
commutative_additive_semigroupwriting output... [ 14%] sage/categories/
finite_dimensional_algebras_with_basis
Exception occurred:
File /home/hugh/sage-4.7-clean/local/lib/python2.6/site-packages/
Sphinx-1.0.4-py2.6.egg/sphinx/writers/html.py, line 501, in
unknown_visit
raise NotImplementedError('Unknown node: ' +
node.__class__.__name__)
NotImplementedError: Unknown node: todo_node
The full traceback has been saved in /tmp/sphinx-err-z52FEc.log, if
you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error
message can be provided next time.
Either send bugs to the mailing list at http://groups.google.com/
group/sphinx-dev/,
or report them in the tracker at http://bitbucket.org/birkenfeld/
sphinx/issues/. Thanks!
Build finished. The built documents can be found in /home/hugh/
sage-4.7-clean/devel/sage/doc/output/html/en/reference
Please let me know if more information would be useful.
cheers,
Hugh
--
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] Rejection on trac_10335-permgroup_domain-mh.patch
Dear friends of the queue-- With sage-4.6.2, running sage -combinat update, I got: applying trac_10335-permgroup_domain-mh.patch patching file sage/categories/pushout.py Hunk #1 succeeded at 974 with fuzz 1 (offset -1737 lines). Hunk #4 FAILED at 2771 1 out of 4 hunks FAILED -- saving rejects to file sage/categories/ pushout.py.rej patching file sage/groups/perm_gps/permgroup.py Hunk #29 succeeded at 1309 with fuzz 2 (offset -5 lines). Hunk #30 FAILED at 1473 Hunk #31 FAILED at 1481 Hunk #37 FAILED at 1642 3 out of 64 hunks FAILED -- saving rejects to file sage/groups/ perm_gps/permgroup.py.rej patch failed, unable to continue (try -v) patch failed, rejects left in working dir errors during apply, please fix and refresh trac_10335- permgroup_domain-mh.patch Abort I do not know what to do -- if there is anything I should do in this situation, I would be happy to learn what it is. cheers, Hugh -- 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] semistandard tableaux
Hi! Eric Webster and I want to make some changes to SemistandardTableaux(p,mu). This is the first change I've tried to make to Sage, so I'm not totally sure of the protocol, but it was suggested to me that I should describe here what we plan to do (as well as opening a trac ticket, which I will do shortly). Mostly, we want to make a change to add a feature, so that one can specify an additional keyword argument max_entry=k so as to get the Semistandard Tableaux(p,mu) with entries in 1..k, or max_entry=-1 so there is no maximum. (Currently, the entries are in 1..|p| unless mu is specified, and I would keep that as the default.) So our proposed change is just an enhancement and presumably won't screw anything up if done right. I do also want to change __repr__ so it always explicitly says what the maximum entry is. While looking at the code, though, I noticed something a bit wierd about the way SemistandardTableaux(p,mu) operates. As it stands, p can be an integer, a partition, or None, and mu is an integer vector describing content. If p is an integer, it returns all tableaux of size p (and with content mu if mu is specified). If p is a partition, it returns all tableaux of shape p (and with content mu if mu is specified). If p is None, it ignores mu. This seems wrong: surely it ought to give you all tableaux of content mu and size |mu|. So I wanted to change that. But it's not because I really need it, it's just tidy-mindedness. If anyone suggests it's a bad idea to do this part, I won't. cheers Hugh -- 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-de...@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.
