ouarf.. :) damned !
Bon, bon, je ne sais pas trop quoi dire. Il faudrait retrouver le fichier
"sage" et le remettre la ou il doit etre, i.e. dans le repertoire
home/matthieu/sage-5.1. Si tu l'as effectivement effacé, une maniere serait
peut-etre juste de re-decompacter le .tar *ailleurs*, et
EADME.txt spkg/ start.log tmp/ VERSION.txt
Y a-t-il une solution pour ne pas avoir à recommencer la compilation ?
Matthieu
De : Frédéric Chapoton
À : sage-combinat-devel@googlegroups.com
Envoyé le : Vendredi 27 juillet 2012 17h57
Objet : [sage-combinat-dev
Hum..
Il faut repartir du ficher .tar, le decompresser a nouveau dans un chemin
sans accent, et recommencer la compilation. L'idee est que chaque tentative
de compilation modifie des choses, et laisse des traces. Il vaut mieux
faire table rase des erreurs passées..
Fred
Le vendredi 27 juillet
tplotlib-1.1.0] Erreur 1
make[1] : on quitte le répertoire « /home/matthieu/sage-5.1/spkg »
real 0m5.683s
user 0m3.711s
sys 0m0.916s
Error building Sage.
make: *** [build] Erreur 1
De : Frédéric Chapoton
À : sage-combinat-devel@googlegroups.c
Salut Matthieu,
il ne faut pas d'accents dans le chemin de sage : le mot Thèse avec un
accent pose probleme, je crois...
ressaye d'installer dans un repertoire sans accent.
Fred
Le jeudi 19 juillet 2012 21:54:53 UTC+2, Martin a écrit :
>
> I just wanted to test whether some experimental change
On Fri, Jul 20, 2012 at 07:47:33AM -0700, Anne Schilling wrote:
> > We could modify the Sage Patchbot ( http://patchbot.sagemath.org/ ) to
> > test the Combinat queue automatically.
>
> That sounds like a good idea. I would also like to have a computer set-up
> (like the new upcoming combinat.sage
On 7/20/12 2:13 AM, Keshav Kini wrote:
> Anne Schilling writes:
>> Here are several *ideas*:
>>
>> * We should run daily tests on the "needs review" section and pop patches
>> off that section if the tests do not pass (or people are not actively
>> working
>> on making them pass).
>
> We cou
Anne Schilling writes:
> Here are several *ideas*:
>
> * We should run daily tests on the "needs review" section and pop patches
> off that section if the tests do not pass (or people are not actively
> working
> on making them pass).
We could modify the Sage Patchbot ( http://patchbot.sagem
On Sat, Mar 17, 2012 at 12:06:46AM -0400, msh...@math.vt.edu wrote:
> And the winning patch (the one before which all doctests pass,
> and after which things are broken), is (drum roll please):
>
> trac_11109-stable-grothendieck-polynomials-nt.patch
:-)
Ok. Thanks for the report!
For the record
Nicolas,
And the winning patch (the one before which all doctests pass,
and after which things are broken), is (drum roll please):
trac_11109-stable-grothendieck-polynomials-nt.patch
I'll take a closer look at it.
--Mark
>> Do you have the problems if you do
>>
>> sage -hg qpop -a
>> sage -b
>
Anne,
> Do you have the problems if you do
>
> sage -hg qpop -a
> sage -b
>
> If not, then there is most likely some patch in the queue that breaks
> this.
Well, I unapplied the patches as above, and everything worked!
I suppose I need to look for a culprit in the queue ...
--Mark
> Anne
>
>
Hi Mark,
When you say "top" you mean that all patches are applied in the sage-combinat
queue?
Do you have the problems if you do
sage -hg qpop -a
sage -b
If not, then there is most likely some patch in the queue that breaks this.
Best,
Anne
On 3/16/12 1:13 PM, msh...@math.vt.edu wrote:
> Nic
Nicolas,
I have reverted to a version of the file that is not modified by
my latest patch (it modified a different file).
I am at the top of the stack of patches;
just removed my sage tree and rebuilt it and
reinstalled sage-combinat and updated.
My sage doesn't seem to know about the direct refe
On Fri, Mar 16, 2012 at 12:09:10PM -0400, msh...@math.vt.edu wrote:
> In doctests.
Weird; it works for me. Please send me off line the full file. Or just
use the right idiom :-)
sage: SymmetricFunctions(QQ).m()
(ok, just a workaround; but we want to eventually get rid of those SFA*).
Nicolas,
In doctests.
--Mark
>> Here is a better question:
>> What could cause the following disturbing error?
>>
>> m = sage.combinat.sf.all.SFAMonomial(QQ)
>> NameError: global name 'sage' is not defined
>
> In code, in the interpreter, or in doctests?
>
> Cheers,
>
On Fri, Mar 16, 2012 at 08:20:36AM -0700, Mark Shimozono wrote:
> Thanks for the tutorial on imports.
> That was excellent info.
>
> Here is a better question:
> What could cause the following disturbing error?
>
> m = sage.combinat.sf.all.SFAMonomial(QQ)
> NameError: global name 'sag
Nicolas,
Thanks for the tutorial on imports.
That was excellent info.
Here is a better question:
What could cause the following disturbing error?
m = sage.combinat.sf.all.SFAMonomial(QQ)
NameError: global name 'sage' is not defined
--Mark
--
You received this message because you a
On Fri, Mar 16, 2012 at 07:44:18AM -0700, Mark Shimozono wrote:
> I was messing a little with sage/categories/weyl_groups.py and hit a
> bunch of doctest errors,
Which patch are you at?
> all apparently caused by an EXAMPLE:: reference to
> sage.combinat.sf.all.SFAMonomial.
> I tried to fix them
I was messing a little with sage/categories/weyl_groups.py and hit a
bunch of doctest errors,
all apparently caused by an EXAMPLE:: reference to
sage.combinat.sf.all.SFAMonomial.
I tried to fix them by adding
from sage.combinat.sf.all import SFAMonomial
The test
$ sage -t sage/categories/weyl_gro
19 matches
Mail list logo
