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
>
> On 3/16/12 1:13 PM, [email protected] wrote:
>> 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 references like
>>
>> sage.combinat.sf.sf.SymmetricFunctions
>>
>> Moreover, explicit importing like
>>
>> from sage.combinat.sf.sf import SymmetricFunctions
>>
>> leads to the weird problem with "factorial".
>>
>> It isn't SFA*, it is some weird import issue.
>> I will fix those SFA occurrences but that isn't the problem.
>>
>> --Mark
>>
>>>> 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
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-combinat-devel" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/sage-combinat-devel?hl=en.
>
>
>


-- 
You received this message because you are subscribed to the Google Groups 
"sage-combinat-devel" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-combinat-devel?hl=en.

Reply via email to