On Jan 8, 11:31 am, "Mike Hansen" <mhan...@gmail.com> wrote:
> Hello,

Hi Mike,

> Sorry for coming in late on this.  One should really use the
> Combinations constructor as it is much better behaved as it doesn't
> use the GAP interface.
>
> sage: Combinations([1,2,3,4],2).list()
> [[1, 2], [1, 3], [1, 4], [2, 3], [2, 4], [3, 4]]
> sage: Combinations([1,2,3,4],2).count()
> 6
>
> We should really get around to deprecating the lowercase names.

Can you please open a ticket and make a list of lower case
combinatorial functions we should deprecate?

Another thing I would like to see:

 * change the deprecation constructor to take an optional date
argument, i.e. when the function was deprecated, so that it can throw
an error so that we pick up "expired" deprecations. I think that 6
months might or might not be enough, i.e. we might want to come up
with some procedure to determine the time frame for deprecation. In
that light it might be easier to add the date a function will be
deprecated. One issue here is that the behavior of an existing binary
would change, i.e. if you are running some six months old release all
the sudden it might throw deprecation warnings, which is no good. So
making the throwing of the error configurable with the default being
not to throw it seems like the best solution. I would have the flag
set when doctesting my builds, so I would find problems and then
actually remove deprecated code once it triggers the errors since the
elapsed time has passed.

 * Make it so that you can quiet the deprecation warning globally in
case someone wants to run code on an older code on a newer release and
the warnings are annoying. Maybe throwing each deprecation warning
only once might make this option less interesting.

Thoughts?

> --Mike

Cheers,

Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to 
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to