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
The idea is to try to have a consistent coding style across the different DAI-Lab projects.
So yes, actually being a bit more opinionated than pep8, and also include things that fall outsite its scope, like project structure, some generic best practices, docstrings and documentation format guidelines, etc.
But it would also not be something as detailed and rigid as the Google Python Style Guide, it would be something between the two.
This is simply too opinionated for a project template. Otherwise you and I will end up arguing about the contents of the STYLE file ad nauseam.
You should feel free to write up your style recommendations in a blog post or similar. If you are maintaining a project, you can request people review your preferred style. You are not the only user of the cookiecutter :)
Add a STYLE.md document with a detailed coding style guide and reference it from the CONTRIBUTING.md guide.
The text was updated successfully, but these errors were encountered: