#16534: Basic Block design methods
-------------------------------------+-------------------------------------
Reporter: brett | Owner:
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-6.4
Component: combinatorial | Resolution:
designs | Merged in:
Keywords: Block Design, | Reviewers:
Incidence Structure, Residual, | Work issues:
Derived, Complement, Supplement, | Commit:
Union | dc5e9c654673101f1875cc3e1cc7221ce4c8d6c0
Authors: Brett Stevens | Stopgaps:
Report Upstream: N/A |
Branch: u/brett/design |
Dependencies: #16553 |
-------------------------------------+-------------------------------------
Comment (by ncohen):
Hello,
> I will try but I may have questions
You may find some answers in the developer's manual:
http://www.sagemath.org/doc/developer/
> wait, which should we do?
We keep it this way to make it simpler (you will have to do your first
merge/rebase, let us not add a ticket split to that). Next time, however,
it would be better to open a second ticket.
> just remove it entirely or build it in as an option to .blocks()?
I think that it can be removed. Python already solves the problem with a
short and natural one-liner.
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/16534#comment:26>
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.
