From the Zed Blog: Less wrestling with settings.json == more coding.

Zed's platform  offers insights and resources on technology, software development, and entrepreneurship. Through articles, tutorials, and personal stories, Zed shares  knowledge and practical advice for individuals looking to succeed in the tech industry. Readers can learn about startup culture, product development strategies, and career growth opportunities to navigate the complexities of the tech landscape effectively.

Zed editor has significantly improved its Python support by introducing automatic virtual environment detection with a toolchain selector, monorepo support with per-project toolchains tracked via pyproject.toml, and separate language servers per toolchain. The editor now defaults to Basedpyright and supports Ty and Ruff out of the box, with plans to integrate Astral's Ty language server into the core. These changes address previous pain points around venv management and configuration complexity, making Python development more seamless.

Making Python in Zed Fun — Zed's Blog

Betting on the Future: Ty, Pyrefly & More

Nice read! My biggest issue is, if ty or ruff or whatever can REMOVE unused imports from a script, then it should be able to add them when I use them.
“Oh, I deleted a line that was the only one using said import? And you, oh so helpfully, removed this now-unused import for me? Thank you! I know that I was using <code>timedelta</code> , but have shifted to something else while I am working, so you removed the import. You are wonderful. But, now, I haven’t realized that you have removed my <code>from datetime import timedelta</code> from the top of the file, and I get the oh-so joyful moment of confusion realizing what’s happened.”
If the import has a logical STL namespace, just import it.
Also, I love ZED.