Re: [sage-combinat-devel] error in queue

2010-10-25 Thread Anne Schilling

I am not an expert with that. It seems to me that you added a new module
in a new folder. I am not sure it fix fix your problem but you should
try to declare this new folder (if it is the case)
in /sage/devel/sage-combinat/sage/setup.py
Look at the lines around line 790 and add your folder there.

For the import :
from rigged_configurations.all import * --  in all.py in /combinat
from filename import bla --  all.py in the new module.

Also don't forget an __init__.py file in your new folder (with just a
space inside this file...)


Brilliant! Thank you, this works. I pushed the code.

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



Re: [sage-combinat-devel] error in queue

2010-10-24 Thread Nicolas Borie
Le samedi 23 octobre 2010 à 18:56 -0700, Anne Schilling a écrit :
 Hi!
 
 With sage-4.5.3 there currently seems to be an error when applying the queue:
 
 applying permgroup_cleanup-mh.patch
 applying permgroup-domain.patch
 patching file sage/categories/finite_permutation_groups.py
 Hunk #1 FAILED at 300
 Hunk #2 FAILED at 326
 2 out of 2 hunks FAILED -- saving rejects to file 
 sage/categories/finite_permutation_groups.py.rej
 patching file sage/groups/perm_gps/permgroup_named.py
 Hunk #10 FAILED at 310
 1 out of 21 hunks FAILED -- saving rejects to file 
 sage/groups/perm_gps/permgroup_named.py.rej
 patch failed, unable to continue (try -v)
 patch failed, rejects left in working dir
 errors during apply, please fix and refresh permgroup-domain.patch
 Abort
 
 Cheers,
 
 Anne

Hello,

I move a piece of code yesterday from the category of finite permutation
group to sage/groups/perm_gps/permgroup_named... I suppose that
permgroup-domain.patch is a patch from Mike. As I was before in the
queue, the later can't be applied.

I can fix it (in your patch and if you want Mike...). You was correcting
some errors in my code which doesn't exist anymore.

For now, I just put a guard on permgroup-domain.patch for the queue to
rebuild well.

Cheers,

Nicolas.



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



Re: [sage-combinat-devel] error in queue

2010-10-24 Thread Nicolas Borie
Le dimanche 24 octobre 2010 à 08:07 -0700, Anne Schilling a écrit :
 Hello Nicolas le Petit,
 
 Thank you!
 
 Now I have another question: I made added a new module
 rigged_configurations and put the line
 from rigged_configurations.all import *
 in all.py in /combinat and an all.py file in the new module.
 
 However, when starting sage I get an error
 `ImportError: No module named rigged_configurations.all`
 
 Do I need to specify this somewhere else as well?
 Also, why do we do
 from sage.combinat.crystals.all import *
 but
 from root_system.all import *
 without the sage.combinat.?
 
 Best,
 
 Anne

I am not an expert with that. It seems to me that you added a new module
in a new folder. I am not sure it fix fix your problem but you should
try to declare this new folder (if it is the case)
in /sage/devel/sage-combinat/sage/setup.py
Look at the lines around line 790 and add your folder there.

For the import :
from rigged_configurations.all import * -- in all.py in /combinat
from filename import bla -- all.py in the new module.

Also don't forget an __init__.py file in your new folder (with just a
space inside this file...)

For your extra question :
from sage.combinat.crystals.all import *
or
from crystals.all import *
if the folder crystals is in combinat, I was thinking both works... (But
I never try to change it...). So I don't know.

I hope that will help.

Cheers,

Nicolas.


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



[sage-combinat-devel] error in queue

2010-10-23 Thread Anne Schilling

Hi!

With sage-4.5.3 there currently seems to be an error when applying the queue:

applying permgroup_cleanup-mh.patch
applying permgroup-domain.patch
patching file sage/categories/finite_permutation_groups.py
Hunk #1 FAILED at 300
Hunk #2 FAILED at 326
2 out of 2 hunks FAILED -- saving rejects to file 
sage/categories/finite_permutation_groups.py.rej
patching file sage/groups/perm_gps/permgroup_named.py
Hunk #10 FAILED at 310
1 out of 21 hunks FAILED -- saving rejects to file 
sage/groups/perm_gps/permgroup_named.py.rej
patch failed, unable to continue (try -v)
patch failed, rejects left in working dir
errors during apply, please fix and refresh permgroup-domain.patch
Abort

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