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
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
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,
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 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,
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
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
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
>
>
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
>
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
11 matches
Mail list logo
