News for hackers. Stuff that matters.

A comment on How to create a Python package in 2022. Parent comment

Re:How to create a Python package in 2022 by fnord123 on Friday July 29, 2022 @05:01PM (#32281732)
Well I have different experiences where no one would ever go back to living without pre-commit, black, autoflake, etc. It moves the fixes to before they get to CI. There's literally no downside.

Maybe you have experience with some weird tool? Or running black and autoflake messed around with emacs and it needs to reload all the buffers?

[ Parent | on HN ]
Re:How to create a Python package in 2022 by wyuenho on Friday July 29, 2022 @05:29PM (#32281990)
I initially had some problems, then I've written an emacs package[1] to fix all of them. And it's due to the course of writing this package made me realize just how bad pre-commit is from its UX, design to its entire premise.

[1]: https://github.com/wyuenho/emacs-python-exec-find

[ Parent | on HN ]
Re:How to create a Python package in 2022 by fnord123 on Saturday July 30, 2022 @04:58AM (#32285348)
Ok then I think the issue is not so much pre-commit but that python tooling in general should not be written in python. It's a minority opinion but the fact that there is a tooling python and an application python can mess with things as you're experiencing.
[ Parent | on HN ]