But it still does not work due to an import loop also in #10963 (which
I couldn't disable as that would have created more conflicts...)

Which import loop? :-)

It is actually already fixed by the review of the cores patch I did
this morning. In the WeylGroups category, I moved an "import
Partition" inside the function which was using it. Category code is
read in quite early in the Sage startup, and should refrain as much as
possible from importing parents like Partition or others.

Oh sorry, it was triggered by my earlier patch in the queue. Thanks for fixing 
this
and thank you for the review of the cores patch.

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.

Reply via email to