Kshitij Chawla

Hi everyone. Since this issue was discussed, the software components that were an issue have been refined and fixed. I have implemented pre-commit hooks in two commercial projects without any...

Hi all. What a rousing discussion! :~) I will address the concerns raised. Burden for maintainers ----------------------- The pre-commit hooks will not be setup manually, but by using the pre-commit...

@ymzayek I would love to provide and example but my implementations were all for closed sourced repos. I will build one for my project, or for Nilearn, and you all...

To reiterate, even if this is implemented and merged, it needs to be turned on for first use by the contributor on their local system and can be turned off....

https://pre-commit.com/hooks.html To start with: - isort - black - flake8 - bandit - pydocstyle (maybe)

I was referring to the "rant" in the comment by dangom, not the whole PR. Yes we can and do all the above things but we also do manual formatting...

I didn't understand this comment though https://github.com/nilearn/nilearn/issues/2528#issuecomment-1205653116 The current PR proposal does not interfere with any of the tasks mentioned in the comment linked above. It is simply automating something...

> As long as system packages are managed by docker/docker-ce-packaging and we don't get release cycles aligned there's nothing we can do to enforce latest compose release is available by...

And like @jflattery said, this isn't Oh! Canonical keeps changing their apt thingamajig which keeps breaking our builds and it is not in our control! No, this is Docker Engine...

@ndeloof The Compose team is telling us there is *nothing* they can do? The Compose team cannot update its installation instructions to recommend just installing from the GitHub releases, or...