#17034: New user interface for orthogonal arrays and a .explain_construction
method
-------------------------------------+-------------------------------------
Reporter: ncohen | Owner:
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-6.4
Component: combinatorial | Resolution:
designs | Merged in:
Keywords: | Reviewers:
Authors: Nathann Cohen | Work issues:
Report Upstream: N/A | Commit:
Branch: u/ncohen/17034 | 60911298a7c3bd33e4f9b7e73de61acc70dfd445
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by vdelecroix):
Replying to [comment:5 ncohen]:
> > Why do you still allow `k=None` in the function `orthogonal_array`? It
would be simpler/cleaner if it was only managed by `largest_available`.
No?
>
> It depends on you. I hate the very principle of backward compatibility,
but that's why it is there, because the guys who call
`designs.orthogonal_array` and will persist in doing so for a year even if
it displays a warning need to be able to call it anyway, or so I am told.
>
> When this thing will not be deprecated anymore this will only be
internal code and we will be allowed to remove whatever we want whenever
we want.
I see. Following the deprecation rules, the code will not be deleted
before sage 6.5. And at that time we might have forget about this! What do
you think about an extra deprecation there?
Vincent
--
Ticket URL: <http://trac.sagemath.org/ticket/17034#comment:6>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
