flow-storm-debugger
PySnooper
Our great sponsors
| flow-storm-debugger | PySnooper | |
|---|---|---|
| 33 | 13 | |
| 626 | 16,260 | |
| 2.4% | - | |
| 9.5 | 5.5 | |
| 10 days ago | 3 months ago | |
| Clojure | Python | |
| The Unlicense | MIT License |
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.
flow-storm-debugger
- FlowStorm a omniscient time travel debugger for Clojure/CLJS
-
What I Have Changed My Mind About in Software Development
Tracing debuggers give you the best of both worlds. I've recently started using Flow-storm [0], by @jpmonettas), and it's been quite transformative. You can still easily see the values flowing through your system (better than just "prints"), and it can handle multi-threaded / async scenarios quite nicely. You don't need to manually step through code, you can just "see" your data flow, and when you have loops or some other form of iteration, you can see the data for each pass. Coupling this with a good data visualization tool (such as Portal [1]) really feels like magic. I've been doing Clojure for quite a few years now, and was very happy with my plain REPL-driven workflow, but this is way better.
[0] https://github.com/jpmonettas/flow-storm-debugger
[1] https://github.com/djblue/portal
- ANN ClojureStorm: Omniscient time travel debugging for Clojure
-
What a good debugger can do
This is another example, a tracing time travel debugger for Clojure https://github.com/jpmonettas/flow-storm-debugger
Supports a bunch of stuff described there and more.
Lisps have some good tooling around debugging, for example clojure's flowstorm or common lisp which has built into the language most of what this article is talking about.
-
Debugging Lisp: trace options, break on conditions
There's some good debugging tooling for Clojure as well. A recent entrant is https://github.com/jpmonettas/flow-storm-debugger and of course there's the estabilished pretty full featured debugging features in CIDER (Emacs), Calva (VS Code) and Cursive (IntelliJ). And for barebones tracing from REPL there's goo old clojure.tools.trace.
-
FlowStorm - Flow Docs, experimental execution derived documentation for Clojure
For Emacs there is something already if you use the Emacs integration described here https://github.com/jpmonettas/flow-storm-debugger/tree/flow-docs/editors.
- Clojure at the REPL: Data Visualization
- [ANN] FlowStorm Clojure[Script] debugger 3.1.259 is out
- Debugging ClojureScript applications with FlowStorm
PySnooper
-
Logging code mess
Definitely not for production, but for debugging (esp. in cases where interactive debugging doesn't work) I've found PySnooper very useful
- What Python debugger do you use?
- What a good debugger can do
-
Trace your Python process line by line with minimal overhead!
Looks interesting I will definitely try this.
For those that find this interesting, you might also like pysnooper - I use it all the time.
https://github.com/cool-RR/PySnooper
https://python.plainenglish.io/pysnooper-stop-debugging-pyth...
-
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
Found PySnooper the other day.
-
What was the most helpful resource that allowed you become a better coder?
pysnooper! https://github.com/cool-RR/PySnooper
-
“I think the vast majority of developers still debug using print() statements”
Shameless plug: PySnooper is a debugging tool for Python that lets you debug in a way that's as easy as adding print statements, but gives you a lot more information automatically.
https://github.com/cool-RR/PySnooper/
HN thread: https://news.ycombinator.com/item?id=19717786
-
Top python libraries/ frameworks that you suggest every one
snoop or pysnooper
-
No more Print For Debugging In Python Anymore
If you want to install a library, pysnooper is cool. It's like an automatic print on every line of your function, with values.
-
The unreasonable effectiveness of print debugging
The Python package PySnooper is pretty good for "fancy" print debug statements: https://github.com/cool-RR/pysnooper
I've caught quite a few bugs using this show-me-all-locals() approach...
What are some alternatives?
test-refresh - Refreshes and reruns clojure.tests in your project.
snoop - Snoop — инструмент разведки на основе открытых данных (OSINT world)
hashp - A better "prn" for debugging
icecream - 🍦 Never use print() to debug again.
sayid - A debugger for Clojure
snoop - A powerful set of Python debugging tools, based on PySnooper
logseq - A local-first, non-linear, outliner notebook for organizing and sharing your personal knowledge base. Use it to organize your todo list, to write your journals, or to record your unique life.
django-modelcluster - Django extension to allow working with 'clusters' of models as a single unit, independently of the database
scope-capture - Project your Clojure(Script) REPL into the same context as your code when it ran
python-devtools - Dev tools for python
portal - A clojure tool to navigate through your data.
pdbpp - pdb++, a drop-in replacement for pdb (the Python debugger)