(I thought I posted this last night, but don't see it now. Apologies if it
is a duplicate.)
Thanks everyone for the discussion, and to Mike for the Set(list())
incantation. It looks like that will preserve the ordering on the output
and I will not need to edit a long string of subsequent doct
It looks to me like ClonableArray stores its object as a list
(I looked at ClonableArray.__init__)
while CombinatorialClass can keep the object as a Set,
but I didn't trace down the code very far.
If you convert a SetPartition to a list first then you
can map to sage Set.
sage: A = SetPartition([
Why is a set partition not a set of sets ? It would be much more
natural than an other layer with .to _set_of_sets(). The two levels
version imply that in order to access all operations you need two
identical copy of the same object. And by a set of sets I mean inherit
from Parent and having catego
Hey,
On Monday, October 28, 2013 7:17:50 PM UTC-7, Mike Zabrocki wrote:
>
> I am not sure, but I believe that this was probably changed in #14140
> when SetPartition was changed from a CombinatorialClass to a
> ClonableArray. It doesn't look like it changed in #15143 but additional
> changes to t
I am not sure, but I believe that this was probably changed in #14140
when SetPartition was changed from a CombinatorialClass to a
ClonableArray. It doesn't look like it changed in #15143 but additional
changes to the SetPartition class were made there.
It seems like the easiest fix would to writ
I forwarded your e-mail to sage-combinat as it might be of interest there.
Isn't there a problem of Element (a set partition) which want at the
same time to be a Parent here (ie a set) ?I guess it would be
impossible to cleanly solve the issue in the actual state of the
Parent/Element implementati
