formatter script should generate python header

[saatviks]

Currently the formatter script only supports headers for languages using // for comments. We need to add support for Python too(i.e. # style comments).

[schedutron]

I want to work on this one. As of now, I think the formatter script only checks the staged files that have a .cpp extension. @tcm-marcel correct me if I'm wrong. To check for # comments, we need to add .py scripts for checking too. Also, what about triple-quoted doc-strings? Would they be more suitable for this task?

[tcm-marcel]

I talked with @pervazea about this: We don't need validators or formatters for python code, as our primary language will be C++, and those are already provided by the Python community. I would have suggested just to add the headers manually.

However, if we can adapt the existing code for updating/placing headers to also work with Python files with only small changes, this seems reasonable. But then I would just use the same header (except for changing the comment delimiter).

Btw, the header is not checked from the validator at all, there is just the update function in the validator.

[schedutron]

@tcm-marcel The header update function is in the formatter, right? I'm trying to adapt it to .py files with as less code as possible. Should I go ahead and submit a PR?

[schedutron]

Also, I think there should be a new requirements.txt file for required Python libraries.

[tcm-marcel]

The header update function is in the formatter, right?

Yes, sorry this was a typo.

I'm trying to adapt it to .py files with as less code as possible. Should I go ahead and submit a PR?

Feel free to refactor the code to make the header update function more readable. But try to use the same code for C++ and Python files. (We don't want duplicate code for every language) Then create a PR.

Also, I think there should be a new requirements.txt file for required Python libraries.

We can think about including this to the existing install script. I will check that.