v3.24.0: Python Support Is Here 🐍
Publication Date: 07/06/2026
Author: Anas Chakroun
5-6 minutes
Python support is live in Turbo Console Log v3.24.0. The same AST-powered precision that already handles JavaScript, TypeScript, and PHP is now available for Python files — no configuration required.
If you write Python, this release is for you — whether you're chasing a 500 through a Django or FastAPI request, sanity-checking a transform in a data-science notebook, or babysitting an automation script at 2am.
Open a Python file, select a variable, and use the same shortcuts you already know. Turbo detects the language automatically and inserts the right log statement.
Log Functions and Shortcuts
Turbo maps each existing shortcut to the right Python logging method. No new shortcuts to learn — the same chord you use for console.log in JavaScript becomes print() in Python.
Insert
print()—⌘K ⌘L/Ctrl+K Ctrl+Llogging.debug()—⌘K ⌘B/Ctrl+K Ctrl+Blogging.info()—⌘K ⌘N/Ctrl+K Ctrl+Nlogging.warning()—⌘K ⌘R/Ctrl+K Ctrl+Rlogging.error()—⌘K ⌘E/Ctrl+K Ctrl+E
Manage
- Comment —
Alt+Shift+C - Uncomment —
Alt+Shift+U - Delete —
Alt+Shift+D - Correct —
Alt+Shift+X
Available in the free core extension
- Insert
print(),logging.debug(),logging.info(),logging.warning(), andlogging.error()from dedicated shortcuts - Comment and uncomment Turbo Python log messages in the active file (using the
#prefix) - Delete inserted Python log messages once debugging is finished
- Correct Python log messages after variable names or context change
- Same AST-aware placement model across JS, TS, PHP, and Python — log lines land in the right position for functions, loops, conditions, and comprehensions
Turbo Pro: Python at Workspace Scale
Free gives you everything you need to debug the file in front of you. Pro is for the moment the problem was never in one file. You chased a bug through webhook.py, then reconcile.py, then a couple of tasks/ modules, dropping a print() here and a logging.debug() there as you went. The bug is fixed. Now there are log statements scattered across six files, and you're the only one who knows where they all are.
It's the moment before you commit. You run git diff and there they are: a print(f"…") you forgot in reconcile.py, two logging.debug lines buried in a 300-line tasks/payouts.py, and one next to a comprehension you'd have sworn you already cleaned. So you start the scroll — file by file, search for print, search for logging, delete, move on, hoping none slip past you into the PR. One usually does, a reviewer flags it, and you push a second commit titled "remove debug logs." Again. The debugging was the easy part. The cleanup is the tax you pay on every single commit.
Pro, in that same moment
Turbo Pro removes that tax. Same pre-commit moment — but instead of opening six files, you open the Turbo workspace panel. Every log Turbo inserted across the whole project is right there in one tree: JS, TS, PHP, and now Python, grouped by file. You flip on the git-aware filter and the panel collapses to only the logs sitting in the files and the exact lines this branch changed — the six that matter, none of the noise from elsewhere in the repo.
You click one to jump straight to its source and eyeball it, leave the single logging.error() you actually meant to keep, then select the rest and clear them in one bulk action. git diff comes back clean. You commit once. No file-by-file scroll, no project-wide grep, no second "remove debug logs" commit. The bigger the project — a Django monorepo, a FastAPI service with a dozen routers, a pile of data-science scripts — the more that one pass over the panel gives you back.
Not a subscription. One-time purchase, lifetime access — no recurring charges. Buy it once and every future release is yours.