Summary

CodeLLDB is triggering this warning: "Could not initialize Python interpreter - some features will be unavailable (e.g. debug visualizers)."

This issue is more of a question or feature request than a bug report per se - It could be a bug, but I don't know.

I am not sure of the full impact of this warning, but there are some things that I expected to work but aren't - Not sure if this is due to early state of debugger or if this warning is impacting it.

Description

In this print, I have my mouse on top of the file_location argument - This feature might not be implemented, if that's the case then we can ignore it. But if it is, this might be a bug.

I don't know what exactly the issue is with CodeLLDB not being able to start the interpreter. I thought it could be virtualenv messing things up, but even upon disabling it it continues to trigger the warning.

Therefore I can't even provide steps to trigger the problem - I don't know why it happens.

For what is worth, on VSCode I also use CodeLLDB and it works without the warning. I also notice that, in the variables tab, it does show the variables but, like the error suggests, it doesn't seem to be printed in the best way. Some types such as String only display the length and not the string itself. In VSCode it's not perfect either but at least all strings are shown as regular strings.

Steps to trigger the problem:

1. Debug any Rust program
2. Somehow trigger the warning

Expected Behavior: Mouse over variable shows the value during debugging. Variables are displayed in its appropriate format.
Actual Behavior: Mouse over variable shows the type instead. String variables shown as strings and not generic structs.

Zed Version and System Specs

Zed: v0.192.8 (Zed)
OS: macOS 15.4.1
Memory: 16 GiB
Architecture: aarch64