vim-jumpsuite
pudb
vim-jumpsuite | pudb | |
---|---|---|
8 | 19 | |
5 | 2,878 | |
- | - | |
0.0 | 7.1 | |
over 1 year ago | 7 days ago | |
Python | Python | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vim-jumpsuite
-
Parse python traceback in the quickfix list.
Oh, you're in luck because I've actually written this exact plugin, it's called vim-jumpsuite. It is personally one of my special weapons that's becoming completely indispensable for me.
-
Which not so well known Python packages do you like to use on a regular basis and why?
vim-jumpsuite: parses python tracebacks and identifies the most "interesting" part of the stack to create a jump list; despite vim being in the name, the python part of the plug-in is usable with any editors that supports parsing grep/quickfix-style output
-
Are you a person who loves reinventing a wheel ?
Here is link number 1 - Previous text "my"
-
Vim setup as a Python IDE with REPL similar to Spyder/VSCode
vim-jumpsuite for creating a quickfix/loclist jumps out of unittest tracebacks
-
IDE Similar to PyCharm for Work
vim-test with lieryan/vim-jumpsuite
-
Open Python error in Vim
For more elaborate cases, I wrote a plugin that summarises python traceback into the quickfix list. vim-jumpsuite is designed to be used when writing unittest/pytest; for each failing test, it'll try to pick the three most important locations that you'll want to jump to. You can also configure certain files/functions to never be picked by vim-jumpsuite.
-
Python Devs who Use Vim, Share Your Expertise!
Plug: one of the most valuable plugin for me are the vim plugin that I wrote myself: lieryan/vim-jumpsuite. It's a plugin to quickly jump to "interesting" line of code from your test suite by converting unittest reports to a Quickfix jumplist. The plugin uses some customizable heuristics to find the lines from tracebacks that are most likely to be most useful to your code.
pudb
-
How can I debug Python code in neovim!
I simply use the superb pudb. Press ctrl+e to open the current file at the current line in your editor.
-
Writing Python Like Rust
such a waste of time...
To this day, I'm baffled by the dynamic language folks who cannot get they head around how strictness/rigor (via a good expressive type system) actually makes maintenance easier and more importantly: cheaper.
[1] https://github.com/inducer/pudb
- Tracing Python
-
What IDE do y’all use
I use the very under-rated pudb in an adjacent terminal window.
-
What Python debugger do you use?
I've been using PuDB for a while now.
-
Make your Debugging easier with these 8 tips in Python
I think it is also worth mentioning pudb here
-
Does anyone use python debugger?
Most of the time I simply use icecream (a much better version of print()), and sometimes, I use pudb (a visual debugger) for tougher/trickier bugs.
-
What do you use for an IDE and for debugging?
For a quick view etc I usually fire up pudb in an adjacent terminal window but for a detailed/heavy debugging session I fire up VS Code (with the vim plugin of course). I have used vi/vim for 37+ years now so it is part of my DNA and use VS Code only for it's great vim + debugging facility.
-
What is your favorite ,most underrated 3rd party python module that made your programming 10 times more easier and less code ? so we can also try that out :-) .as a beginner , mine is pyinputplus
Two that I haven’t seen here and have saved me tons of time are pudb, a great debugger and petl a simple powerful ETL toolkit.
-
Using a debugger in Vim
If you want to debug Python then pudb is simply superb. Vim users don't really want or need to "debug inside of vim" do they? We usually are happy to use multiple command line and other tools in adjacent windows. Also, you can just step around and view variables etc in pudb and then press ctrl+e to edit that file in vim, then q to restart debugger.
What are some alternatives?
pylsp-rope - Extended refactoring capabilities for python-lsp-server using Rope
ipdb - Integration of IPython pdb
Python-mode - Vim python-mode. PyLint, Rope, Pydoc, breakpoints from box.
pdb-tutorial - A simple tutorial about effectively using pdb
Rope - a python refactoring library
flask-debugtoolbar - A toolbar overlay for debugging Flask applications
vim-test - Run your tests at the speed of thought
winpdb - Fork of the official winpdb with improvements
python-lsp-server - Fork of the python-language-server project, maintained by the Spyder IDE team and the community
django-debug-toolbar - A configurable set of panels that display various debug information about the current request/response.
vim-textobj-indent - Vim plugin: Text objects for indented blocks of lines
django-devserver - A drop-in replacement for Django's runserver.