21–30 of 35 posts
- uv (went from pipenv to poetry to uv), which was the right decision imo.
- ruff (replaced black)
- PyCharm, but some people use vscode or neovim.
- mypy for type checking, which I am not 100% happy with. One experienced developer swears by mypy, thats the reason we haven't explored alternatives.
- 'just' as task runner
I have been forced into VS Code due to a heavy handed push to use more AI stuff and Copilot in VS Code being the blessed way to do that.
I only use it for local models and don't have any hosted ones that I'm willing to pay for so YMMV.
With that out of the way: mise for managing versions of all the runtimes (asdf is fine too), uv for packages (previously poetry which is ok), mypy type checking for things I make. Otherwise I switch between projects a lot so just use whatever the projects use by default.
Deployment tools aren't really language specific (when they are they're rarely good). The editing, it's just Cursor, although I did like the jetbrains IDE previously.
But overall - just give things a go. It's usually quite easy to swap those tools as needed.
Not a big company, however: - uv (went from pipenv to poetry to uv), which was the right decision imo. - ruff (replaced black) - PyCharm, but some people use vscode or neovim. - mypy for type checking, which I am not 100% happy with. One experienced developer swears by mypy, thats the reason we haven't explored alternatives. - 'just' as task runner
If I had my choice, I'd switch environment and package management to uv.
I have been forced into VS Code due to a heavy handed push to use more AI stuff and Copilot in VS Code being the blessed way to do that.
I haven't tried it but I'd assume copilot just exposes an OpenAI compatible API. The Llama.cpp plugin for neovim should work with that OOTB. I only use it for local models and don't have any hosted ones that I'm willing to pay for so YMMV.
We authenticate through a GitHub via SSO, which has a whole RBAC model behind it.
Maybe it would work with something else, but it’s usually more trouble than it’s worth, and depending on the source of the plugin for the other editors, could set off alarms with the security organization, and maybe legal as well. We have a lot of rules around our use of AI.
VS Code and local Python virtual environments. Packages managed with pip and versions pinned with pipcompile. One ML production environment forces us to use conda we inherit from the pip environment and try to have as much done by pip as possible. Formatted with black and flake8 Unit tests with unittest Azure Dev Ops for running tests, security screening, and CI The happy path for deployment is build docker images in…