#16453: Cythonize quiver paths
-------------------------------------+-------------------------------------
Reporter: SimonKing | Owner:
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-6.4
Component: algebra | Resolution:
Keywords: | Merged in:
Authors: Simon King | Reviewers:
Report Upstream: N/A | Work issues: Rebase wrt #17564
Branch: | Commit:
public/ticket/16453 | e03b66156f5b5212bfeffc937887ae5c29a1a6ca
Dependencies: #15820 #17564 | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by SimonKing):
Replying to [comment:89 SimonKing]:
> {{{
> git checkout -b new_branch_for_here branch_17564
> git merge --squash branch_from_here
> git commit
> git trac push --forced --ticket=16453
> }}}
> (or however a forced push is done).
>
> I am not sure that that's what I want. If I understood correctly what
Nathann said, he as a reviewer prefers to have a sequence of commits each
addressing a single feature, ...
On the other hand, I don't see how this could be naturally split into
features. We have a relatively straight forward cython implementation of
paths on top of bounded integer sequences, and we apply the new paths in
`path_semigroup`. So, I guess a single commit should be easy enough to
review.
--
Ticket URL: <http://trac.sagemath.org/ticket/16453#comment:90>
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.
