Newlines don't work in debugger console - forwarding as directed by /vscode team

[Tim-K-DFW]

This was reported in May 2019 in the vscode repo, and after a good deal of discussion the team there concluded that it stems from choices made (or implied, as I understood) by the Python Extension group here.
Visual Studio Code is the most beautiful and well-made programming experience in Python I've ever seen, but sadly this one glitch makes it unusable for anything data-science related. Runtime inspection of matrix-like objects (numpy arrays, tensors etc.) is fundamental to what we do, and "printing" them as one mess with interspersed \ns - I seriously cannot comprehend in what ways it may be preferred to evaluating newlines and pretty-printing. I agree not everything can be printed, and these objects are complex and so on, however that's why their libraries address that and do their best... but then debugger console decides nah, we'll pretend we haven't see those newlines.

To be clear, I'm aware of Python Interactive and its inspection capabilities. This is different, for example Python Interactive can't be used for non-interactive work like building classes and functions.

Can you guys please look into this and change this behavior? As I understood, it was almost done around April but then reverted back... Many many people will thank you. 🌞 ☮️ And in any case, thank you very much and mad respect for the great work you and your colleagues are doing on this. 👍

[karthiknadig]

@Tim-K-DFW see here for the original issue and we are tracking bug on the debugger side. microsoft/ptvsd#1432

The solution we are looking at is to make that behavior configurable. So that extensions can set their preferred behavior. Once that configuration is available in VS Code, we will update the python extension.