dmesg --follow
[ 68692020.000 ] posts.x: Full talk on building a structured query engine for agent context, from schema discovery to self-correcting queries:  |   [ 68692020.000 ] posts.x: When Claude starts a task with no context attached, it behaves like a brand new employee: grepping through the codebase, guessing at what matters…  |   [ 68673720.000 ] posts.x: @davidsenra you will love this!  |   [ 68673600.000 ] posts.x: https://t.co/vhJifvV8y9  |   [ 68673600.000 ] posts.x: This Jay-Z documentary, In 8, is exceptional! Nearly 6 hours of intimate conversation between @sc and the brilliant @RickRubin. It’s rare to get such…  |   [ 68662260.000 ] posts.x: Full talk on turning re-prompted fixes into linters, including the OpenAPI drift fix and the skill-writing whack-a-mole:  |   [ 68662260.000 ] posts.x: Re-prompting an agent to fix the same sloppy pattern over and over isn't a workflow, it's a sign the rule should live in code, not in your head…  |   [ 68650020.000 ] posts.x: ↻ @willcb: me: kinda fucked up how many people are offloading their whole lives to muse or instinct or grokbot or whatever claude: yeah  |   [ 68650020.000 ] posts.x: ↻ @iamdevloper: signs you've become the senior dev: you're the only one who understands the deploy script you're the only one who remembe…  |   [ 68649720.000 ] posts.x: Gooooooooood morning! Brazil Oberon Cerrado. Roasted 110 seconds past first crack. Milk chocolate and almond.  |   [ 68647800.000 ] posts.x: @Saanvi_dhillon “Git expert” is a weird flex, though, isn’t it?  |   [ 68610720.000 ] posts.x: @sujee_dev @dkundel @aiDotEngineer Thanks mate!  |   [ 68600580.000 ] posts.x: Full talk on the Codex app server protocol and what you can build on top of the Codex harness:  |   [ 68600580.000 ] posts.x: A lot of engineers assume building their own agent interface means writing their own agent harness from scratch. @dkundel, Developer Experience Lead…  |  
corey@gallon.me:~/til$
apropos
/writing 8 pieces · long form /til 27 notes · small /conferences 20 write-ups /snips 2 · links, quotes /projects 64 things that run /speaking 3 talks · rooms /courses 1 taught · cohorts connect follow ⋅ subscribe about.md who this is
CONTENTS 1 min
Debugging Python Tests in VSCode FIG 1 FIG 2Command Palette Python Configure T FIG 3Command Palette Select Framework.p FIG 4Right Click Debug Test.png
~/til/debugging-python-tests-in-vscode.md
-rw-r--r-- 95 words 1 min4 figures 2024-09-15

Debugging Python Tests in VSCode

FIGURE 1 ⋅ Debugging Python Tests in VSCode

VSCode offers native test capabilities that are quite useful. Testing Python in Visual Studio Code

It doesn’t, however, recognize your Python tests by default. You must configure it to do so for each project.

Command Palette (CTRL+SHIFT+P) → “Python: Configure Tests” →

Command Palette Python Configure Tests.png
FIGURE 2 ⋅ Command Palette Python Configure Tests.png

Select the framework you’re using:

Command Palette Select Framework.png
FIGURE 3 ⋅ Command Palette Select Framework.png

Now, you get all of the testy-goodness that VSCode has to offer for Python.

In this case, I wanted to debug a specific test. Super easy! Just drop breakpoints in the test where you want them, then run “Debug Test”.

Right Click Debug Test.png
FIGURE 4 ⋅ Right Click Debug Test.png

The “Test Explorer” is also quite useful.

corey@gallon.me:~$ tail -f /writing Attach to the stream. An email when I have something worth sending. Replies encouraged!
corey@gallon.me:~$ ls -lt /til ↑2024-10-06 raco: Racket's Package Management System (and More)
▸2024-09-15 Debugging Python Tests in VSCode ⋅ you are here
↓2024-09-15 Debugging Python CLI Arguments in VSCode