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
I just started working on the code, and it's a little tricky to get used to some of the non-standard conventions, especially the super-deep indentation. Would it be worth running the whole repo through black to get something more PEP-8 compliant?
Similarly, the windows carriage returns are kind of annoying (top tip - set git config --local core.whitespace cr-at-eol to stop them showing up in git diff). Not sure if black will convert file endings anyway, but if not, a pass through dos2unix wouldn't hurt either...
The text was updated successfully, but these errors were encountered:
Yeah, we should probably get on 4-space indentation, and a few more PEP8 compliances.
Thanks for the carriage return tips! Most of this stuff is written on a mixture of operating systems, and I don't always pay attention to these things.
I just started working on the code, and it's a little tricky to get used to some of the non-standard conventions, especially the super-deep indentation. Would it be worth running the whole repo through black to get something more PEP-8 compliant?
Similarly, the windows carriage returns are kind of annoying (top tip - set
git config --local core.whitespace cr-at-eol
to stop them showing up in git diff). Not sure if black will convert file endings anyway, but if not, a pass through dos2unix wouldn't hurt either...The text was updated successfully, but these errors were encountered: