Python3.13 All functions fail to send: IndentationError: unexpected indent

[karthiknadig]

Discussed in #24222

^{Originally posted by ddxv October 2, 2024}
I recently fired up Python3.13rc2 but quickly found that any lines I send to the terminal do not work, specifically anything with additional line breaks or with indentation.

The new REPL, as I'm sure you know, autoindents for users. So it appears I'm getting a new indent for each line + the existing indent, causing a deeper and deeper indent even on a flat function. As you can see in the screenshot:

This inevitably leads to: IndentationError: unexpected indent

I'm opening a discussion because I don't see others mentioning this for Python 3.13, so I was not sure if this is actually a bug or something unique to my settings?

If others are encountering this, happy to turn this into a ticket.

[AlexNaglich]

I am experiencing the same.

Version: 1.94.2 (system setup)
Commit: 384ff7382de624fb94dbaf6da11977bba1ecd427
Date: 2024-10-09T16:08:44.566Z
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.26100
python: 3.13.0

[MMateo1120]

Same behaviour and error, only happens with python 3.13, 3.12 works fine.

[anthonykim1]

Thanks for the bug report! We investigate issues in order based on priority and severity, which includes the impact it has on your ability to use the extension to do productive work, and the number of people affected. If other users come forward and leave a comment demonstrating they are seeing/reproducing the problem then we will raise this issue's priority. Thanks for understanding and the patience!

Please go ahead and upvote this meanwhile so that we can further acknowledge the severity.

[AlexNaglich]

Regarding severity, it greatly inhibited my ability to do work. Testing individual blocks of code is no longer a viable option for me. I cannot copy paste, I cannot shift+enter, I cannot right click and run in interactive window... I have to modify the python code, then to non-interactively test I run the entire program that calls the python. Dramatic decrease in productivity as a result of tedious testing and debugging.

[teuncm]

For me and students of our classes the impact is also huge. We teach the first steps of Python programming by letting them run blocks of code using shift+enter, but with the new behavior this is no longer an option at all.

[cbrnr]

I just wanted to add that this also severely impacts how I use Python 3.13 in Visual Studio Code. For those looking for a workaround (other than downgrading Python to ≤ 3.12 or setting the env variable PYTHON_BASIC_REPL=1, which are both not good options), is to use the "Native REPL" (enable in the settings).

[cbrnr]

BTW, just to let Windows users know that this currently does not work in Windows Terminal either, see python/cpython#124119.

[masai2018]

I updated VS Code to the most updated version (1.95.0) but still have the same error with Python 3.13 on Windows and Mac OS.

[anthonykim1]

Thanks @cbrnr for

(other than downgrading Python to ≤ 3.12 or setting the env variable PYTHON_BASIC_REPL=1, which are both not good options), is to use the "Native REPL" (enable in the settings).

Thanks everyone for the feedback here. Team is actively looking into resolving this, but please try out the "Native REPL" setting to send code and execute in Native REPL instead of terminal meanwhile.