Re: [sage-combinat-devel] queue broken?

2013-03-17 Thread tom d
Ok,thanks!

Just today there was another broken spot in the queue.  (I upgraded to 
5.8rc0 just in case, too.)  I was wanting to rebase my affine permutations 
patch for the new documentation system so that it can finally get a review, 
and it was under the broken patch, so I just made the fixes and pushed... 
 hope that's ok.

applying trac_12876_category-fix_abstract_class-nt-rel11521.patch
patching file sage/categories/homset.py
Hunk #6 FAILED at 261
1 out of 11 hunks FAILED -- saving rejects to file 
sage/categories/homset.py.rej
patch failed, unable to continue (try -v)
patch failed, rejects left in working dir
errors during apply, please fix and refresh 
trac_12876_category-fix_abstract_class-nt-rel11521.patch
Abort



On Saturday, March 16, 2013 12:57:22 AM UTC+3, Anne Schilling wrote:

 Hi Tom, 

 Yes, I got the same error with sage-5.8.bet4. I rebased Ben Salisbury's 
 patch. 
 It should work now. 

 Ben, please pull from the sage-combinat server before you keep working on 
 your patch! 

 Best, 

 Anne 

 On 3/15/13 2:51 PM, tom d wrote: 
  From tonight's attempt to apply the queue in Sage 5.7rc0: 

  
  applying trac_4327-root_system_plot_refactor-nt.patch 
  patching file sage/combinat/root_system/type_affine.py 
  Hunk #1 succeeded at 237 with fuzz 2 (offset -54 lines). 
  applying trac_14143-alcove-path-al.patch 
  applying trac_14192-infinity_crystal-bs.patch 
  patching file sage/combinat/crystals/all.py 
  Hunk #1 FAILED at 11 
  1 out of 1 hunks FAILED -- saving rejects to file 
 sage/combinat/crystals/all.py.rej 
  patch failed, unable to continue (try -v) 
  patch failed, rejects left in working dir 
  errors during apply, please fix and refresh 
 trac_14192-infinity_crystal-bs.patch 
  
  
  This persists after trying to qselect guards and recloning the combinat 
 branch.  Is this happening for others or do I need to suck it up and move 
 on to true 5.7? 


-- 
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.




Re: [sage-combinat-devel] queue broken?

2013-03-15 Thread Anne Schilling
Hi Tom,

Yes, I got the same error with sage-5.8.bet4. I rebased Ben Salisbury's patch.
It should work now.

Ben, please pull from the sage-combinat server before you keep working on your 
patch!

Best,

Anne

On 3/15/13 2:51 PM, tom d wrote:
 From tonight's attempt to apply the queue in Sage 5.7rc0:
  
 
 applying trac_4327-root_system_plot_refactor-nt.patch
 patching file sage/combinat/root_system/type_affine.py
 Hunk #1 succeeded at 237 with fuzz 2 (offset -54 lines).
 applying trac_14143-alcove-path-al.patch
 applying trac_14192-infinity_crystal-bs.patch
 patching file sage/combinat/crystals/all.py
 Hunk #1 FAILED at 11
 1 out of 1 hunks FAILED -- saving rejects to file 
 sage/combinat/crystals/all.py.rej
 patch failed, unable to continue (try -v)
 patch failed, rejects left in working dir
 errors during apply, please fix and refresh 
 trac_14192-infinity_crystal-bs.patch
 
 
 This persists after trying to qselect guards and recloning the combinat 
 branch.  Is this happening for others or do I need to suck it up and move on 
 to true 5.7?

-- 
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.




Re: [sage-combinat-devel] queue broken on 5.7

2013-02-26 Thread Travis Scrimshaw
I'll check as soon as I get in that trac_13872-RC_bijections-ts.patch still 
applies and reupload #13605 to trac. However on 5.8.beta1, I get this 
reject:

patching file doc/en/thematic_tutorials/index.rst
Hunk #1 FAILED at 4
1 out of 1 hunks FAILED -- saving rejects to file 
doc/en/thematic_tutorials/index.rst.rej
patch failed, unable to continue (try -v)
patch failed, rejects left in working dir
errors during apply, please fix and refresh 
trac_14090-thematic_tutorials-nt.patch

I'll also look into this and fix this this morning.

Best,
Travis


On Monday, February 25, 2013 10:32:56 PM UTC-5, Franco Saliola wrote:


 Hello Nicolas,

 Thank you for the quick fix!

 Take care,
 Franco

 --

 On Mon, Feb 25, 2013 at 9:58 PM, Nicolas M. Thiery 
 nicolas...@u-psud.frjavascript:
  wrote:

 On Mon, Feb 25, 2013 at 09:01:52PM -0500, Franco Saliola wrote:
 $ sage -v
 Sage Version 5.7, Release Date: 2013-02-19
 $ sage -combinat update
 ...
 applying trac_13605-partition_options-ts.patch
 patching file 
 sage/combinat/rigged_configurations/rigged_configurations.py
 Hunk #1 FAILED at 930
 1 out of 1 hunks FAILED -- saving rejects to file
 ...

 I fixed my failing patch as well as Travis. The queue is functional
 again on 5.7.

 Cheers,
 Nicolas

 PS: Travis, I allowed myself to trim out the following trivial hunk
 out of trac_13605-partition_options-ts.patch

 --
 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 unsubscribe from this group and stop receiving emails from it, send an 
 email to sage-combinat-devel+unsubscr...@googlegroups.com javascript:.
 To post to this group, send email to 
 sage-comb...@googlegroups.comjavascript:
 .
 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.





-- 
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.




Re: [sage-combinat-devel] queue broken on 5.7

2013-02-26 Thread Anne Schilling
Hi Travis,

Thank you for your work on this.

  I did the quick rebase of #14090 over #11490.
 
 I also had to do some minor rebasing of the following patches:
 
 trac_12876_category-fix_abstract_class-nt-rel11521.patch over #9235.
 
 trac_12895-subcategory-methods-nt.patch and 
 trac_10963-more_functorial_constructions-nt.patch over #13370.
 
 After that, the queue applies for me on 5.8.beta1 and starts. Can someone 
 make sure the same occurs for 5.7?

It works for me with sage-5.7.

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.




Re: [sage-combinat-devel] queue broken on 5.7

2013-02-26 Thread Vincent Delecroix
Hello,

The sage -combinat install failed for my sage-5.7 freshly installed with

applying trac_12895-subcategory-methods-nt.patch
patching file sage/categories/category_singleton.pyx
Hunk #3 FAILED at 277
1 out of 3 hunks FAILED -- saving rejects to file
sage/categories/category_singleton.pyx.rej
patch failed, unable to continue

Best,
Vincent

-- 
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.




Re: [sage-combinat-devel] queue broken on 5.7

2013-02-25 Thread Nicolas M. Thiery
On Mon, Feb 25, 2013 at 09:01:52PM -0500, Franco Saliola wrote:
$ sage -v
Sage Version 5.7, Release Date: 2013-02-19
$ sage -combinat update
...
applying trac_13605-partition_options-ts.patch
patching file sage/combinat/rigged_configurations/rigged_configurations.py
Hunk #1 FAILED at 930
1 out of 1 hunks FAILED -- saving rejects to file
...

I fixed my failing patch as well as Travis. The queue is functional
again on 5.7.

Cheers,
Nicolas

PS: Travis, I allowed myself to trim out the following trivial hunk
out of trac_13605-partition_options-ts.patch

--
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 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.




Re: [sage-combinat-devel] queue broken on 5.7

2013-02-25 Thread Franco Saliola
Hello Nicolas,

Thank you for the quick fix!

Take care,
Franco

--

On Mon, Feb 25, 2013 at 9:58 PM, Nicolas M. Thiery nicolas.thi...@u-psud.fr
 wrote:

 On Mon, Feb 25, 2013 at 09:01:52PM -0500, Franco Saliola wrote:
 $ sage -v
 Sage Version 5.7, Release Date: 2013-02-19
 $ sage -combinat update
 ...
 applying trac_13605-partition_options-ts.patch
 patching file
 sage/combinat/rigged_configurations/rigged_configurations.py
 Hunk #1 FAILED at 930
 1 out of 1 hunks FAILED -- saving rejects to file
 ...

 I fixed my failing patch as well as Travis. The queue is functional
 again on 5.7.

 Cheers,
 Nicolas

 PS: Travis, I allowed myself to trim out the following trivial hunk
 out of trac_13605-partition_options-ts.patch

 --
 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 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.




-- 
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.




Re: [sage-combinat-devel] queue broken for sage 5.3

2012-09-18 Thread Franco Saliola
On Tue, Sep 18, 2012 at 10:08 AM, Martin Rubey
martin.ru...@math.uni-hannover.de wrote:
 Hi there,

 I just installed sage 5.3 from source and did

 sage -combinat install

 and got

 patching file sage/categories/category.py
 Hunk #6 FAILED at 1803
 1 out of 7 hunks FAILED -- saving rejects to file
 sage/categories/category.py.rej
 unable to find 'sage/categories/category_with_axiom.py' for patching
 1 out of 1 hunks FAILED -- saving rejects to file
 sage/categories/category_with_axiom.py.rej
 patch failed, unable to continue (try -v)
 patch failed, rejects left in working dir
 errors during apply, please fix and refresh
 impose_mro_for_category_classes-nt.patch
 Abort

 I'm rather desperate (I didn't update because I needed a stable
 environment, but now it seems that the operating system was updated
 :-())

It's not clear what you are desperate for. The command

sage -b main

will return you to the main sage branch. This will give you a working
copy of sage without any combinat patches applied.

Franco

--

-- 
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] queue broken for sage 5.3

2012-09-18 Thread Christian Stump
 I'm rather desperate (I didn't update because I needed a stable
 environment, but now it seems that the operating system was updated
 :-())

if you just want a working version old of the queue, the following might work

cd SAGE_ROOT/devel/sage-combinat
sage -hg update -r XXX
sage -hg qpop -a
sage -hg qpush -a

Here, XXX is a version of the queue that was still working on your
version of sage (if I don't make a mistake, for me XXX=7527 was
working for 5.3.rc1). Please report if this helps since others might
want to do the same if the queue is broken.

Best, Christian

-- 
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] queue broken for sage 5.3

2012-09-18 Thread Anne Schilling
hg update -r 7570:f738ef433157

works with sage-5.3. Unfortunately, nobody can push until Nicolas fixes his 
patches!

Best,

Anne

On 9/18/12 7:20 AM, Christian Stump wrote:
 I'm rather desperate (I didn't update because I needed a stable
 environment, but now it seems that the operating system was updated
 :-())
 
 if you just want a working version old of the queue, the following might work
 
 cd SAGE_ROOT/devel/sage-combinat
 sage -hg update -r XXX
 sage -hg qpop -a
 sage -hg qpush -a
 
 Here, XXX is a version of the queue that was still working on your
 version of sage (if I don't make a mistake, for me XXX=7527 was
 working for 5.3.rc1). Please report if this helps since others might
 want to do the same if the queue is broken.
 
 Best, Christian

-- 
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] queue broken for sage 5.3

2012-09-18 Thread Martin Rubey
Franco Saliola sali...@gmail.com writes:

 It's not clear what you are desperate for. The command

I need some of the patches...

 if you just want a working version old of the queue, the following might work

 cd SAGE_ROOT/devel/sage-combinat
 sage -hg update -r XXX
 sage -hg qpop -a
 sage -hg qpush -a

 Here, XXX is a version of the queue that was still working on your
 version of sage (if I don't make a mistake, for me XXX=7527 was
 working for 5.3.rc1). Please report if this helps since others might
 want to do the same if the queue is broken.

 Best, Christian

Anne Schilling a...@math.ucdavis.edu writes:

 hg update -r 7570:f738ef433157

 works with sage-5.3. Unfortunately, nobody can push until Nicolas
 fixes his patches!

Many many thanks!!!

Martin

-- 
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] queue broken for sage 5.3

2012-09-18 Thread Nicolas M. Thiery
On Tue, Sep 18, 2012 at 07:47:44AM -0700, Anne Schilling wrote:
 Unfortunately, nobody can push until Nicolas fixes his patches!

Oops, sorry, there was a missing guard on the patch I had just
added. Well, it was an easy fix. Pushed.

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] queue broken

2012-08-31 Thread Christian Stump
Hi Anne,

 sage -hg qselect
 sage -hg qpush -a

I don't know why I constantly forget to do so. Thanks for the reminder...

-- 
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] queue broken

2012-08-30 Thread Anne Schilling
Hi Christian,

Did you try

sage -hg qselect

and then

sage -hg qpush -a

I had changed the guards on trac_11305-rigged_configurations-ts.patch
and the patch trac_13403-bijection_KR_crystals_tableaux-ts.patch is based
on it.

That's what happened for me the first time I applied the queue after the change,
but now it works.

Best,

Anne

On 8/30/12 2:14 AM, Christian Stump wrote:
 Hi,
 
 trac_13403-bijection_KR_crystals_tableaux-ts.patch doesn't apply on
 5.2 . Since it is the newest version, we might want the queue to apply
 there (even if most people updated to 5.3.??? already - I am now doing
 so with 5.3.rc0).
 
 Christian

-- 
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] queue broken

2012-05-21 Thread Christian Stump
Hi!

 There is a break in sage between patch

 trac_12895-subcategory-methods-nt.patch
 trac_8327_universal_cyclotomic_field-cs.patch

fixed -- it was actually Mark closing the last link for the import
loop by importing

from sage.graphs.digraph import DiGraph

in categories/weyl_groups. I updated his patch accordingly (Mark,
please pull my changes before changing your patch!).

I still don't know how to properly do the importing. E.g., here we have

...
-- 243 from sage.combinat.free_module import CombinatorialFreeModule
...
--- 28 from sage.categories.all import ModulesWithBasis
...
-- 126 from weyl_groups import WeylGroups
127 from finite_weyl_groups import FiniteWeylGroups
128 from affine_weyl_groups import AffineWeylGroups

why does something low level like combinatorial free module or
modules with basis import weyl groups ? Or are categories always
considered to be lower ?

Best, Christian

-- 
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] queue broken

2012-05-21 Thread Christian Stump
Hi,

unfortunately, the queue is still broken at
trac_12940_affine_permutations-td.patch.

Christian

-- 
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] queue broken

2012-05-21 Thread Nicolas M. Thiery
On Mon, May 21, 2012 at 09:32:02AM +0200, Christian Stump wrote:
 Or are categories always considered to be lower ?

Taken from: 
http://groups.google.com/group/sage-combinat-devel/msg/15221ad8016af193
(which btw should be discussed on sage-devel and put in the dev manual)
--
To avoid  import loops, I try to stick to the following order:

- Python modules
- Misc
- Categories
- Stuff in sage.structure
- Basic parents (NN, QQ, ...)
- Rest of the stuff

and a module in one of the above items should only import modules from
higher items. E.g. a module in sage.categories can import from a
module in sage.misc, but not reciprocally.
--

According to the above rules, a category file should not import stuff
like DiGraph or CombinatorialFreeModule (but that's ok within its
methods, or using lazy imports).

 why does something low level like combinatorial free module or
 modules with basis import weyl groups ?

That's because of the all in:

from sage.categories.all import ModulesWithBasis

Given the above rules, it's in principle ok for combinatorial free
module to import all categories. However, for extra safety, it would
indeed be better to use from sage.categories.modules_with_basis.

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] queue broken

2012-05-21 Thread Nicolas M. Thiery
On Mon, May 21, 2012 at 09:36:57AM +0200, Christian Stump wrote:
 unfortunately, the queue is still broken at
 trac_12940_affine_permutations-td.patch.

Fixed. See other thread (NCSF/trac_12940_affine_permutations-td.patch)

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] queue broken

2012-05-21 Thread Christian Stump
 Fixed. See other thread (NCSF/trac_12940_affine_permutations-td.patch)

thx, but don't forget to push, please!

-- 
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] queue broken

2012-05-21 Thread Anne Schilling
On 5/21/12 12:52 AM, Nicolas M. Thiery wrote:
 On Mon, May 21, 2012 at 09:32:02AM +0200, Christian Stump wrote:
 Or are categories always considered to be lower ?
 
 Taken from: 
 http://groups.google.com/group/sage-combinat-devel/msg/15221ad8016af193
 (which btw should be discussed on sage-devel and put in the dev manual)
 --
 To avoid  import loops, I try to stick to the following order:
 
 - Python modules
 - Misc
 - Categories
 - Stuff in sage.structure
 - Basic parents (NN, QQ, ...)
 - Rest of the stuff
 
 and a module in one of the above items should only import modules from
 higher items. E.g. a module in sage.categories can import from a
 module in sage.misc, but not reciprocally.
 --

Is this a rule for the import statements at the beginning of the file?

I am currently implementing an __iter__ method for the category of
Crystals. But without any further import statements, I get an import
loop just by adding this method.

How can I debug this?

Cheers,

Anne

-- 
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] queue broken

2012-05-21 Thread Nicolas M. Thiery
On Mon, May 21, 2012 at 01:24:38PM -0700, Anne Schilling wrote:
 On 5/21/12 12:52 AM, Nicolas M. Thiery wrote:
  --
  To avoid  import loops, I try to stick to the following order:
  
  - Python modules
  - Misc
  - Categories
  - Stuff in sage.structure
  - Basic parents (NN, QQ, ...)
  - Rest of the stuff
  
  and a module in one of the above items should only import modules from
  higher items. E.g. a module in sage.categories can import from a
  module in sage.misc, but not reciprocally.
  --

 Is this a rule for the import statements at the beginning of the file?

Yes. Well, that's the rule I follow myself, and would tend to
recommend. I guess it's time to open the debate about this on
sage-devel (though I won't be able to do it before I come back from
China).

 I am currently implementing an __iter__ method for the category of
 Crystals. But without any further import statements, I get an import
 loop just by adding this method.

This should not occur. Make sure that this really is the only change.

 How can I debug this?

Usually the traceback is quite informative on which module import
which. Then you have to figure out where it's most natural to break
the loop.

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] queue broken

2012-05-14 Thread Anne Schilling
On 5/13/12 10:32 PM, Martin Rubey wrote:
 Following advice of Volker, I installed 5.0rc1.  This install went
 fine.  However, the combinat queue does not apply:
 
 patching file sage/combinat/partition.py
 Hunk #1 FAILED at 428
 1 out of 1 hunks FAILED -- saving rejects to file
 sage/combinat/partition.py.rej
 patch failed, unable to continue (try -v)
 patch failed, rejects left in working dir
 errors during apply, please fix and refresh
 partition_k_boundary_speedup-fh.patch
 
 since this happens frequently: is there a way for me to fix it and help?

In fact, I also get this reject in sage-5.0.beta14:

applying dyck_word_print-fh.patch
applying partition_constructor_speedup-fh.patch
applying skew_partitions_init_speedup-fh.patch
applying partition_k_boundary_speedup-fh.patch
patching file sage/combinat/partition.py
Hunk #1 FAILED at 428
1 out of 1 hunks FAILED -- saving rejects to file sage/combinat/partition.py.rej
patch failed, unable to continue (try -v)
patch failed, rejects left in working dir
errors during apply, please fix and refresh 
partition_k_boundary_speedup-fh.patch
Abort

Florent, could you fix this?

Thanks,

Anne

-- 
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] queue broken

2012-05-13 Thread Anne Schilling
On 5/13/12 10:32 PM, Martin Rubey wrote:
 Following advice of Volker, I installed 5.0rc1.  This install went
 fine.  However, the combinat queue does not apply:
 
 patching file sage/combinat/partition.py
 Hunk #1 FAILED at 428
 1 out of 1 hunks FAILED -- saving rejects to file
 sage/combinat/partition.py.rej
 patch failed, unable to continue (try -v)
 patch failed, rejects left in working dir
 errors during apply, please fix and refresh
 partition_k_boundary_speedup-fh.patch
 
 since this happens frequently: is there a way for me to fix it and help?

I just got precisely the same problem. This is due to the fact that nobody has
yet tried to run the queue with 5.0.rc1. Since this is Florent's patch it is
probably best to wait till he refreshes it.

Martin, as far as I understood Volker his patch is already in 5.0.rc1, so you
won't need the sage-combinat queue. You can just do

sage -br

and try his commands.

Best,

Anne

-- 
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] queue broken

2012-05-13 Thread Martin Rubey
Anne Schilling a...@math.ucdavis.edu writes:

 On 5/13/12 10:32 PM, Martin Rubey wrote:
 Following advice of Volker, I installed 5.0rc1.  This install went
 fine.  However, the combinat queue does not apply:
 
 patching file sage/combinat/partition.py
 Hunk #1 FAILED at 428
 1 out of 1 hunks FAILED -- saving rejects to file
 sage/combinat/partition.py.rej
 patch failed, unable to continue (try -v)
 patch failed, rejects left in working dir
 errors during apply, please fix and refresh
 partition_k_boundary_speedup-fh.patch
 
 since this happens frequently: is there a way for me to fix it and help?

 I just got precisely the same problem. This is due to the fact that nobody has
 yet tried to run the queue with 5.0.rc1. Since this is Florent's patch it is
 probably best to wait till he refreshes it.

 Martin, as far as I understood Volker his patch is already in 5.0.rc1, so you
 won't need the sage-combinat queue. You can just do

 sage -br

 and try his commands.

Yes, but I need combinat to generate the data :-)

Martin

-- 
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] queue broken

2012-05-13 Thread Anne Schilling
On 5/13/12 10:54 PM, Martin Rubey wrote:
 Anne Schilling a...@math.ucdavis.edu writes:
 
 On 5/13/12 10:32 PM, Martin Rubey wrote:
 Following advice of Volker, I installed 5.0rc1.  This install went
 fine.  However, the combinat queue does not apply:

 patching file sage/combinat/partition.py
 Hunk #1 FAILED at 428
 1 out of 1 hunks FAILED -- saving rejects to file
 sage/combinat/partition.py.rej
 patch failed, unable to continue (try -v)
 patch failed, rejects left in working dir
 errors during apply, please fix and refresh
 partition_k_boundary_speedup-fh.patch

 since this happens frequently: is there a way for me to fix it and help?

 I just got precisely the same problem. This is due to the fact that nobody 
 has
 yet tried to run the queue with 5.0.rc1. Since this is Florent's patch it is
 probably best to wait till he refreshes it.

 Martin, as far as I understood Volker his patch is already in 5.0.rc1, so you
 won't need the sage-combinat queue. You can just do

 sage -br

 and try his commands.
 
 Yes, but I need combinat to generate the data :-)

Then try to disable the offending patch in your series file and hope that 
nothing
else after that depends on it ... otherwise you might have to wait till Florent
refreshes his patch.

Best,

Anne

-- 
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.