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
Short list of things to be cleaned up in this file. As discussed previously, keeping in some of these things and addressing them in the readme would also be good... perhaps having two (or more) versions of the file could be worth considering, like a "starter" file and a "solution" file or similar.
updating the docstring formatting to be fully consistent with CSC148 (rough example below for the Particle class):
running python TA and fixing all style issues, such as ones mentioned below:
adding type annotations to all functions and methods; for tuple, make sure to specify the types the tuple contains (e.g., tuple[float, float] for coordinates... or using int if in units of pixels).
adding docstrings to all functions and methods, with docstring examples as appropriate.
naming conventions with pothole case used for method names and CamelCase for class names.
80 character line length max.
The text was updated successfully, but these errors were encountered:
Short list of things to be cleaned up in this file. As discussed previously, keeping in some of these things and addressing them in the readme would also be good... perhaps having two (or more) versions of the file could be worth considering, like a "starter" file and a "solution" file or similar.
Particle
class):adding type annotations to all functions and methods; for
tuple
, make sure to specify the types thetuple
contains (e.g.,tuple[float, float]
for coordinates... or usingint
if in units of pixels).adding docstrings to all functions and methods, with docstring examples as appropriate.
naming conventions with pothole case used for method names and CamelCase for class names.
80 character line length max.
The text was updated successfully, but these errors were encountered: