Writing and linting Python at scale
engineering.fb.com
Writing and linting Python at scale
1–10 of 160 posts
Re: Writing and linting Python at scale
#2(It's a podcast, not an article)
Re: Writing and linting Python at scale
#3(It's a podcast, not an article)
The description links to the tech article.
https://engineering.fb.com/2023/08/07/developer-tools/fixit-...
Re: Writing and linting Python at scale
#4They are talking about this project : https://pypi.org/project/fixit/2.0.0a1/#description
https://libcst.readthedocs.io/en/latest/ powers Fixit 2. I would love to hear if there are any production users here for this new linter, and how is that working out for them?
Re: Writing and linting Python at scale
#5But but but HN told me that python is only good for small scale and prototypes, the engineers at meta are wrong
Re: Writing and linting Python at scale
#6I'm happy with Ruff[0], it's very fast.
Re: Writing and linting Python at scale
#7There's a lot of neat Python research coming from Facebook.
libcst (which Fixit uses) is super cool - I use it in https://gitlab.com/harford/logzy
Re: Writing and linting Python at scale
#8It looks like the interesting feature of their tool Fixit 2 is that its lint rules know how to auto-apply themselves. I'm fine with an auto code formatter, an auto import organizer, but not sure how much I trust a linter to auto-apply "fixes".
Re: Writing and linting Python at scale
#9[dead]
Re: Writing and linting Python at scale
#10But but but HN told me that python is only good for small scale and prototypes, the engineers at meta are wrong
The engineers at meta worte a language + runtime on top of PHP to make it work "at scale".
If Facebook wants to make something work they have enough resources to throw at the problem to solve it. Regardless of whether it makes sense or not.