Uploaded image for project: 'Other'
  1. Other
  2. OTHER-391

Code formatting guideline for PythonBrainz

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Normal Normal
    • Guidelines
    • None

      The pep 8 formatting tool we are using is annoying us with small formatting issues, rather than automatically fixing them.
      We should find the right tools and choose the right rules and let an automated tool do it for us instead (autopep8, 130 char line length).

      • Propose save hooks for vim/vscode/pycharm
      • Add develop.sh command to re-format
      • Add this guideline to our developer docs

      We don't want to do this on local precommit hooks (because this will commit content changes without the coder doing anything).
      Another way is having a bot in PRs doing it, but this adds an additional commit to the history, and has the effect of changing code after developers test it locally.
      We want to keep pep8speaks:
      Guidelines are at https://github.com/metabrainz/guidelines (Apparently we all forgot about this repo?)

      • Make clear links to this from each project that uses it.

          Loading...
          Uploaded image for project: 'Other'
          1. Other
          2. OTHER-391

          Code formatting guideline for PythonBrainz

            • Icon: Task Task
            • Resolution: Unresolved
            • Icon: Normal Normal
            • Guidelines
            • None

              The pep 8 formatting tool we are using is annoying us with small formatting issues, rather than automatically fixing them.
              We should find the right tools and choose the right rules and let an automated tool do it for us instead (autopep8, 130 char line length).

              • Propose save hooks for vim/vscode/pycharm
              • Add develop.sh command to re-format
              • Add this guideline to our developer docs

              We don't want to do this on local precommit hooks (because this will commit content changes without the coder doing anything).
              Another way is having a bot in PRs doing it, but this adds an additional commit to the history, and has the effect of changing code after developers test it locally.
              We want to keep pep8speaks:
              Guidelines are at https://github.com/metabrainz/guidelines (Apparently we all forgot about this repo?)

              • Make clear links to this from each project that uses it.

                    Unassigned Unassigned
                    ApekattQuest, MonkeyPython MonkeyPython
                    Votes:
                    0 Vote for this issue
                    Watchers:
                    1 Start watching this issue

                      Created:
                      Updated:

                        Version Package

                          Unassigned Unassigned
                          ApekattQuest, MonkeyPython MonkeyPython
                          Votes:
                          0 Vote for this issue
                          Watchers:
                          1 Start watching this issue

                            Created:
                            Updated:

                              Version Package