#16101: Python backend for Polyhedra
-------------------------------------+-------------------------------------
Reporter: vbraun | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.3
Component: geometry | Resolution:
Keywords: days57 | Merged in:
Authors: Volker Braun | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/vbraun/double_description | 1f64cdf1c6add12c8925967132bf1eb9440c7985
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by vbraun):
Replying to [comment:42 chapoton]:
> Well, ok, I understand that it is better not to touch whitespaces to
avoid conflicts, but maybe you could still make the effort to remove
blanks (pep8 errors `W***`) in the new files that you introduce ?
If you care about trailing whitespace then write a commit hook. But I
don't have any intention of removing inconspicuous trailing whitespace by
hand. If you want to talk about whitespace policies then bring it up on
sage-devel.
--
Ticket URL: <http://trac.sagemath.org/ticket/16101#comment:44>
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.