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
There are lots of tools for using PEP8, which is the style I generally expect to see in a disciplined Python project. Most of PEP8 is great; the main contentious bit is the maximum linewidth of 79 characters, but that actually isn't a problem with the current Macrodensity codebase. The biggest change from the existing style is the consistent use of spaces after commas. The pep8 program is handy for finding inconsistencies and there's even yapf which will reformat for you. (Although I find it a bit too eager to split function arguments onto individual lines.)
It's also worth noting that Google-style docstrings are already in somewhat-consistent use. If that's cleaned up and expanded a little it would be easy to get some fancy API docs using sphinx/Napoleon.
There are not many style rules observed in the code. It would be nice to tidy this up before a submission to JOSS.
ToDo: run the source code through and try to check for style conventions, imports of unused functions etc.
The text was updated successfully, but these errors were encountered: