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
Just to make everything more consistent as we start to push out more code, could we settle on some style conventions? Some things come to mind:
4 spaces for indentation
80 character line limit
camel case for classes (e.g., MyClass), snake case for everything else (e.g., my_variable, my_function) (and I suppose dashes for file/directory names, like policy-smoothing).
docstring for every function explaining at a minimum what it does, and preferably what inputs are expected, and what it returns and possibly what exceptions it raises.
Are these ok with everyone, and does anyone have any to add? We could/should eventually put these into a readme.
Also, we should also settle on what versions of things we're using. In particular, @benlawson 's amazon pricing script uses Python 3, but @ch3njust1n 's code uses Python 2. Is there a reason not to use Python 3 for everything?
The text was updated successfully, but these errors were encountered:
Just to make everything more consistent as we start to push out more code, could we settle on some style conventions? Some things come to mind:
Are these ok with everyone, and does anyone have any to add? We could/should eventually put these into a readme.
Also, we should also settle on what versions of things we're using. In particular, @benlawson 's amazon pricing script uses Python 3, but @ch3njust1n 's code uses Python 2. Is there a reason not to use Python 3 for everything?
The text was updated successfully, but these errors were encountered: