On Wed, Jun 22, 2011 at 03:58:26PM +0200, Martin Rubey wrote:
> shouldn't that be is_subset and is_superset?
See the discussion on #10938.
Cheers,
Nicolas
--
Nicolas M. Thiéry "Isil"
http://Nicolas.Thiery.name/
--
You received this message because you are subscr
"Nicolas M. Thiery" writes:
> Dear Stefan,
>
> Thanks for your feedback!
>
> On Mon, Jun 20, 2011 at 02:08:18PM -0700, Stefan van Zwam wrote:
>>Sorry to bug you again with this (I already did so a few months back), but
>>I still have qualms with Sage's built-in Set type. For starter
Dear Stefan,
Thanks for your feedback!
On Mon, Jun 20, 2011 at 02:08:18PM -0700, Stefan van Zwam wrote:
>Sorry to bug you again with this (I already did so a few months back), but
>I still have qualms with Sage's built-in Set type. For starters, it does
>not offer the same int
Hi all,
Sorry to bug you again with this (I already did so a few months back), but I
still have qualms with Sage's built-in Set type. For starters, it does not
offer the same interface that Python's frozenset offers (example: the
issubset() method).
But my more serious concern is speed. I woul
Hi all,
Sorry to bug you again with this (I already did so a few months back), but I
still have qualms with Sage's built-in Set type. For starters, it does not
offer the same interface that Python's frozenset offers (example: the
issubset() method).
But my more serious concern is speed. I woul
