#18972: twographs and Seidel switching
-------------------------------------+-------------------------------------
Reporter: dimpase | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.9
Component: graph theory | Resolution:
Keywords: | Merged in:
Authors: | Reviewers: Nathann Cohen
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/dimpase/seidelsw | a729b27245f217f98bde11e4fc13dd03cdce9c96
Dependencies: #18960, #18948, | Stopgaps:
#18988, #18991, #18986, #19018, |
#19019 |
-------------------------------------+-------------------------------------
Comment (by ncohen):
> what is the guideline? 80 chars, less, more?
The "official" rule, if I remember correctly, is to follow "yet another
senseless" PEP. If I make no mistake, it is something like 80 characters
for the code and 72 characters for the doc (no joke).
In Sage it seems that we apply 80 characters everywhere, which is already
rather boring to enforce.
> Removing will cause a doctest failure, hopefully...
Err, right...
> How does one mix `**kwargs` and explicit keywords (which have to be used
too, as I need
> some control over this)?
In the natural way:
{{{
sage: def a(hey=3,**kwargs):
....: print hey, kwargs
....:
sage: a(6)
6 {}
sage: a(hey=9,eeee=4)
9 {'eeee': 4}
}}}
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/18972#comment:135>
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.
