RidgeRun Developer Manual/Coding Styles/Python: Difference between revisions
Efernandez (talk | contribs) |
Efernandez (talk | contribs) |
||
| Line 9: | Line 9: | ||
== 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. | |||
Revision as of 20:55, 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 |
|
| Profiling Tools |
| Methodologies |
| Design Patterns |
| RidgeRun Developer Manual/Testing |
| RidgeRun Developer Manual/Build Systems |
| Contact Us |
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.