Difference between revisions of "RidgeRun Developer Manual/Coding Styles/Python"
Efernandez (talk | contribs) (→Introduction to 'Python' Coding Styles) |
Efernandez (talk | contribs) (→Good practices) |
||
| Line 16: | Line 16: | ||
| + | == Code Layout == | ||
| + | == Naming == | ||
Revision as of 15:56, 21 June 2021
 | WORK IN PROGRESS. Please Contact RidgeRun OR email to support@ridgerun.com if you have any questions. |
| RidgeRun Developer Manual |
|---|
 |
| Coding Styles |
| Development Tools |
| Editors |
| Debugging Tools |
| Methodologies |
| Design Patterns |
| Testing |
| Build Systems |
| Contact Us |
Contents
Introduction to 'Python' Coding Styles
When writing Python code, RidgeRun tries to follow PEP8 - Style Guide for Python Code. Following we present some of the rules presented in this standard. For more information please visit PEP8.
Good practices
Be consistent with your code
In general, if you are adding code to an existent code, be consistent with the coding standard already being used. If no standard is used then follow this guide.
Code Layout
Naming
