You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/CONTRIBUTING.rst
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,12 +91,14 @@ Here's how to make a one-off code change.
91
91
92
92
Once the process terminates, you can view the built documentation by opening ``docs/build/html/index.html`` with a browser.
93
93
94
-
- For consistency, please conform to `Google Python Style Guide`_ and `Google Python Style Docstrings`_. In addition, code should be formatted consistently with other code around it.
94
+
- For consistency, please conform to `Google Python Style Guide`_ and `Google Python Style Docstrings`_.
95
95
96
96
- The following exceptions to the above (Google's) style guides applies:
97
97
98
98
- Documenting types of global variables and complex types of class members can be done using the Sphinx docstring convention.
99
99
100
+
- In addition, PTB uses the `Black`_ coder formatting. Plugins for Black exist for some `popular editors`_. You can use those instead of manually formatting everything.
101
+
100
102
- Please ensure that the code you write is well-tested.
101
103
102
104
- Don’t break backward compatibility.
@@ -189,11 +191,6 @@ Here's how to make a one-off code change.
189
191
Style commandments
190
192
------------------
191
193
192
-
Specific commandments
193
-
#####################
194
-
195
-
- Avoid using "double quotes" where you can reasonably use 'single quotes'.
196
-
197
194
Assert comparison order
198
195
#######################
199
196
@@ -255,3 +252,5 @@ break the API classes. For example:
0 commit comments