4 ms·

I love Sublime, but like many others have not used it nearly as much in recent years due to how much more powerful VSC is for Python development: do you still d

by memco 6y ago

I love Sublime, but like many others have not used it nearly as much in recent years due to how much more powerful VSC is for Python development: do you still do work in Python and if so, does ST4 have a somewhat comparable experience to VSC? Last I tried (which was two or three years ago) I couldn't get code navigation, completion and debugging to work on nearly the same level and remote editing in VSC was also much easier to set up.

fprog 6y ago
Unfortunately I haven't worked with Python in some time, so I can't say. If my Go experience translates, then the basics (code navigation, completions, definitions...) have gotten much better, both in form and function. Those could be worth another try. I'm less sure about debugging, and as far as I know, there's no equivalent to VSC's remote editing. I've heard great things about that VSC feature and been meaning to try it out.
krut-patel 6y ago
I'm someone who always tries to use the "right tool for the job", CLion for C/C++ (large projects), VSC for Rust (the inline type hints from Rust Analyzer are to die for), and ST for Python. I tried out the python experience in VSC but have found it to be _inferior_ to the speed of ST when coupled with the Anaconda (not the venv stack) plugin [0]. It supports venvs, build systems (even remote jobs, but I haven't messed around with those), and all the basic things like go to definition (instant! Even works inside libraries) and find usages work quite well. When paired with the SublimeREPL plugin, I get the venv repl inside ST _with_ autocomplete. That is just a step below full blown (slower) Jupyter notebook experience. The Python exception tracebacks in the output panel have their file paths clickable, so I can immediately jump to the source line. This is adequate for me in terms of debugging experience, but ST obviously doesn't bundle a full-fledged debugger like VSC. The quality of autocomplete is pretty much the same as VSC since both Anaconda and the LSP server use Jedi internally for all the core stuff. There are definitely some rough edges, like having to set the python interpreter path for a new project using venvs, instead of the auto-setup we see in VSC. Another thing is the development of Anaconda has mostly gone into maintenance mode, and is much slower with bug fixes than VSC in that regard, but this hasn't affected me by a lot since most of the core functionality is pretty stable. I really recommend giving Anaconda+ST a try for your Python dev needs. [0]: http://damnwidget.github.io/anaconda/ http://damnwidget.github.io/anaconda/

by memco 6y ago

fprog 6y ago

Unfortunately I haven't worked with Python in some time, so I can't say. If my Go experience translates, then the basics (code navigation, completions, definitions...) have gotten much better, both in form and function. Those could be worth another try. I'm less sure about debugging, and as far as I know, there's no equivalent to VSC's remote editing. I've heard great things about that VSC feature and been meaning to try it out.

krut-patel 6y ago

I'm someone who always tries to use the "right tool for the job", CLion for C/C++ (large projects), VSC for Rust (the inline type hints from Rust Analyzer are to die for), and ST for Python. I tried out the python experience in VSC but have found it to be _inferior_ to the speed of ST when coupled with the Anaconda (not the venv stack) plugin [0]. It supports venvs, build systems (even remote jobs, but I haven't messed around with those), and all the basic things like go to definition (instant! Even works inside libraries) and find usages work quite well. When paired with the SublimeREPL plugin, I get the venv repl inside ST _with_ autocomplete. That is just a step below full blown (slower) Jupyter notebook experience. The Python exception tracebacks in the output panel have their file paths clickable, so I can immediately jump to the source line. This is adequate for me in terms of debugging experience, but ST obviously doesn't bundle a full-fledged debugger like VSC. The quality of autocomplete is pretty much the same as VSC since both Anaconda and the LSP server use Jedi internally for all the core stuff. There are definitely some rough edges, like having to set the python interpreter path for a new project using venvs, instead of the auto-setup we see in VSC. Another thing is the development of Anaconda has mostly gone into maintenance mode, and is much slower with bug fixes than VSC in that regard, but this hasn't affected me by a lot since most of the core functionality is pretty stable. I really recommend giving Anaconda+ST a try for your Python dev needs. [0]: http://damnwidget.github.io/anaconda/ http://damnwidget.github.io/anaconda/