zcy
/
svgpathtools
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

minor improvements

pull/65/head^2
Andy Port 2018-11-02 16:42:11 -07:00 committed by GitHub
parent 9e218b2b3b
commit d810653b63
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
CONTRIBUTING.md
View File

@ -42,8 +42,9 @@ you want your code's variable names to match some official documentation, or
PEP8 guidelines contradict those present in this document). PEP8 guidelines contradict those present in this document).
* Include docstrings and in-line comments where appropriate. See * Include docstrings and in-line comments where appropriate. See
"Docstring Style" section below for more info. "Docstring Style" section below for more info.
* Use explicit, uncontracted names (e.g. "parse_transform" instead of * Use explicit, uncontracted names (e.g. `parse_transform` instead of
"parse_trafo"). The ideal names should be something a user can guess `parse_trafo`). Maybe the most important feature for a name is how easy it is
for a user to guess (after having seen other names used in `svgpathtools`).
* Use a capital 'T' denote a Path object's parameter, use a lower case 't' to * Use a capital 'T' denote a Path object's parameter, use a lower case 't' to
denote a Path segment's parameter. See the methods `Path.t2T` and `Path.T2t` denote a Path segment's parameter. See the methods `Path.t2T` and `Path.T2t`
if you're unsure what I mean. In the ambiguous case, use either 't' or another if you're unsure what I mean. In the ambiguous case, use either 't' or another