3 ms·
We've got about 30+ backends in python all wrapped in docker containers. Majority of the team was pure vim before I joined and they're slowly converting to pych
by _drFaust 9y ago
We've got about 30+ backends in python all wrapped in docker containers. Majority of the team was pure vim before I joined and they're slowly converting to pycharm after seeing how nicely you can setup a remote interpreter against a docker container. And it has vim bindings so you don't have to re-learn new hotkeys.
I've also been following this VS Code issue on adding remote docker support for python
https://github.com/Microsoft/vscode-python/issues/79#issuecomment-366000230 https://github.com/Microsoft/vscode-python/issues/79#issueco...
However, if you're a hardcore vim guy then I doubt these IDEs are gonna satiate your current flow.
- nickjj 9y agoFunny you mentioned that issue. I'm eagerly awaiting that feature too. I commented in the issue a few weeks ago: https://github.com/Microsoft/vscode-python/issues/79#issuecomment-362836925 https://github.com/Microsoft/vscode-python/issues/79#issueco.... Once that's implemented, oh man, development nirvana.
- wirrbel 9y agoI remember, on my laptop with pycharm and docker (and the virtual machine docker lived in), the RAM usage was just excessive. I am by no means a minimalist, but data-science stuff was barely impossible with 16 GB RAM. Also, I strongly dislike PyCharm. I am a vim guy by heart, but I am generally not against IDEs. VS Code is okayish. For C++ development, I really loved Visual Studio. But PyCharm just feels wrong, bloated, slow and baroque
- jsmeaton 9y agoWhat I do is create the virtualenv locally that docker would also create, and point my editor to the local virtualenv. It gives me all of the intellisense locally. I still need to debug within the container/shell for the moment but I'm hoping there's a pathway coming for vscode that pycharm already has.
- sheraz 9y agoyup. happy pycharm and docker user here. even have it working with debugging and breakpoints.