just VS CodeLLDB

Benefit is you can just type the command, no need to prepend pyqwe or anything.

See also justfile for a non-python specific tool https://github.com/casey/just

This is an interesting approach. These days I have completely switched to just[0] tool for similar use case.

[0]: https://github.com/casey/just

# Palindrome project Project used to explain my view on a django project architecture ## Tools, libs, etc. Some time related files. Versions on Poetry. - [Python](https://www.python.org/) Programming languange - [django-environ](https://django-environ.readthedocs.io) Manage .envs in Django - [Poetry](https://python-poetry.org/) Python packaging and dependency management - poetry.lock - pyproject.toml - [Django](https://www.djangoproject.com/) Web framework written in Python - [Docker](https://www.docker.com/) Manage containers for dev environment - compose.yaml - compose/dev/Dockerfile - compose/dev/start - .env - [Just](https://just.systems/) encapsulate commands for easier use - justfile ## Dev environment setup 1. Install Just, Docker and Poetry(opcional). 2. Copy .env.example to .env, no need for edtion. 3. Certified that docker is up and running 4. `$ just build` ## Run the server for development 1. Certified that docker is up and running 2. `$ just runserver` You can access on http://0.0.0.0:8000/

We heavily use Just at OpenSauced, a command runner utility, much like GNU’s “make”, for easily executing small scripts. This has enabled us to quickly onramp new team members or community members to our Go ecosystem since building and testing is as simple as “just build” or “just test”!

> If I had to submit one tip it would be to set everything up with a Makefile or similar.

If I had to submit a tip on top of yours, it's to use justfiles instead of Makefiles :-)

https://github.com/casey/just

If you’re going to use make, use just instead:

https://github.com/casey/just

My first thought was that that was dropping one of the main features of make.

On reflection though, the timestamp dependant part isn't really something used much nowadays apart from compiling C.

It'd be cool if it was an opt-in feature for just files so that it could actually function as a replacement for make in all cases.

I went looking in the docs and found this[0] which I'd missed last time I looked into justfiles.

[0] https://github.com/casey/just?tab=readme-ov-file#what-are-th...

Ok, so apparently here they are called 'data formatters' instead of pretty printers or debug helpers... https://github.com/vadimcn/codelldb/wiki/Custom-Data-Formatters

For debugging lldb supports python scripts: https://github.com/vadimcn/codelldb/wiki/Data-visualization

I use VS Code on Linux to debug Zig. Haven't tried the others you mentioned, but it just emits standard DWARF symbols, so I'm guessing if you can debug C/C++ you could probably also do Zig with minimal changes? I just use the lldb VS code plugin[0], which works out of the box for me with no issues.

https://github.com/vadimcn/codelldb

It's pretty bad, unfortunately. As you discovered, using the gnu toolchain works better with code-lldb (see more info here), but it still isn't great. CLion is a little better, but costs money and lacks support in other ways compared to VSCode.

- I tried to install codelldb: https://github.com/vadimcn/vscode-lldb without success.

Are you on Windows or Linux? On Windows I've had nothing but trouble getting code-lldb to display debug info for any sort of nontrivial data structure due to this issue, which means I need to switch to x86_64-pc-windows-gnu, but then that breaks other upstream crates that use cc to compile C++ code.

I've been using vscode-lldb with VS Code on macos, and I've been very happy with the experience so far.

Check this: https://github.com/vadimcn/vscode-lldb/wiki/Breakpoints-are-not-getting-hit

yeah since they updated the rust compiler for windows to use a different style of debugger symbols and since they changed that in CodeLLDB the variables output have not been the same. Though i believe the owner has been trying to fix it. But any issues you do have report them on the codeLLDB git https://github.com/vadimcn/vscode-lldb