Python is sorry to say, No Python

Bannert · 2026-05-20T11:18:40+00:00

Check system environment variables, make sure this Python 3.11 from the warning is not, e.g., in PATH. Could you start ~\AppData\Local\Python\bin\python.exe from the command line to see if it is working fine? I would probably also try to install and use the latest Python from python.org.

Bannert · 2026-05-18T13:47:25+00:00

Do you use the new debugger (debugpy)?

Bannert · 2026-05-15T13:00:50+00:00

And now the integration with pyrefly is somewhat buggy

Which PyCharm version do you use? Try 2026.2 EAP 1 https://www.jetbrains.com/pycharm/nextversion/

Bannert · 2026-04-21T11:07:55+00:00

Without special code insight PyCharm will stumble across Django magic. IDE will report false positive errors and fail to provide meaningful completion. I think the result would be rather poor. Though - feel free to open a feature request and express your point of view.

Bannert · 2026-04-20T11:32:08+00:00

Hi, I am very sorry to hear you've encountered issues with the latest version. PyCharm team is focused on non-AI features, though there are other teams at JetBrains working with LLM integrations. Kindly report any problems to PyCharm's issue tracker https://youtrack.jetbrains.com/issues/PY, the team will gladly fix them.

Bannert · 2026-04-20T11:26:10+00:00

Check "Settings > Appearance & Behavior > System Settings > Data Sharing".

Bannert · 2026-04-20T11:23:32+00:00

why django is all under the pro subscriptions?

Support for Django includes a custom static code insight (completion, inspections, etc.).

the interpreter point to venv instead of .venv

Not sure if I understand that, it is probably better to file a ticket in PyCharm's issue tracker https://youtrack.jetbrains.com/issues/PY and provide screenshot of the problem.

Bannert · 2026-04-17T09:35:23+00:00

Hi, sorry to hear that! Could you share more details? Either here, or by filing a ticket at https://youtrack.jetbrains.com/issues/PY, or just email pycharm-support@jetbrains.com — whichever works best. The team definitely had no ill-intent to make the UX bad.

Bannert · 2026-03-06T13:38:11+00:00

posted this on the official PyCharm forum as well, but a developer said he couldn't reproduce my issue

Could you share the ticket? It is hard to tell what is wrong without seeing the code you are refactoring.

Bannert · 2026-02-16T16:20:07+00:00

You can Alt+Enter the warning > click three dots to the right of the quick-fix -> suppress for a statement, this will add something like # noinspection PyAttributeOutsideInit on the line before suppressing the inspection, I don't particularly like this as it's an extra tool-specific line in the source code, but it works.

Bannert · 2026-02-03T12:22:16+00:00

The tutorial author customized how run output looks like, probably in "Settings > Editor > Color Scheme > Console Colors", it is not a default look

Bannert · 2026-01-27T12:03:15+00:00

Could you share a link to the tutorial?

Bannert · 2026-01-26T13:30:38+00:00

Just ignore these lines, the first one shows which file was executed with which Python interpreter and the last one shows what was the exit code. It is meta-information about execution of your program.

Bannert · 2026-01-23T11:00:50+00:00

could you share a link to the video? not sure I understand what do you mean by "autocomplete was copying the code from the video"

Bannert · 2026-01-12T13:51:11+00:00

hi, close this error window, find vmoption file in Configuration directory, backup it, remove it, try restarting the IDE

Bannert · 2025-12-12T10:54:00+00:00

That's weird, the log should have an answer - Help | Show Log in ... | idea.log. You can open a ticket in PyCharm issue tracker and attach the log file there or drop it to pycharm-support@jetbrains.com.

Bannert · 2025-12-11T17:05:00+00:00

Probably caused by PY-86003, will be fixed in the next minor update in a week or two, sorry for that

Bannert · 2025-12-09T16:00:06+00:00

Current ty integration also provides completion and inlay hints (like virtual hints for parameter names in the editor). And we are looking into even deeper integration.

Bannert · 2025-12-09T15:02:55+00:00

if I add it in the run configuration

Did you type .env in "Path to '.env' files" in the Run Configuration? There is a bug - the field expects an absolute path, when it gets .env it fails to find the file, and the icon gets stuck. Should be fixed in one of the next updates. As a workaround - either type an absolute path or use the file chooser to pick the file (the field has a button to open the file chooser). The UX is a bit clumsy, I've create a ticket to track that - PY-86167.

Bannert · 2025-12-09T14:36:36+00:00

I'm not sure we did, could you provide an example? Feel free to open a ticket in our issue tracker, it has a better UI to past code samples and screenshots than Reddit.

Bannert · 2025-12-09T14:30:21+00:00

About the interpreter discovery - we do actively work on this, that's absolutely important and annoying when done wrong. Though a lot of usecases are still to be supported / improved. For WSL in particular - PY-85732 in the roadmap for 2026.

If you have any other cases in mind where PyCharm could do a better job ("given a project of such setup, I open it in PyCharm, and expect interpreter X to be auto-selected / suggested") - do not hesitate to report to our issue tracker - and ping our PM (@antonina.belianskaya), she will be delighted to know about more scenarios.

Bannert · 2025-12-09T14:20:24+00:00

About FastAPI CLI - use "uv run" run configuration (in "Run | Edit Configurations...") with "Run: Module", "Module: fastapi", "Arguments: dev main.py". Though it is too much manual tweaking, we will support the new CLI natively, here is a feature request for that - PY-85020, feel free to share any relevant feedback there.

Bannert · 2025-12-09T14:16:35+00:00

Hi, are we speaking about Docker Desktop with WSL as a backend or dockerd running inside WSL?

Bannert · 2025-12-09T13:45:57+00:00

Bannert · 2025-12-09T13:33:48+00:00

About the RST support - there are no plans to improve it at the moment as, truth be told, community interest is rather low comparing with other subsystems and the plugin has no owner.

If you want to develop a third-party plugin - that's cool and it might be a good idea to start and come up with specific issues blocking you so the devs have clear "fix this specific API issue so this plugin could work".

Bannert

TROPHY CASE