search

microsoft / vscode-python

Python extension for Visual Studio Code
https://aka.ms/pvsc-marketplace
MIT License
4.34k stars 1.19k forks source link

Logging for Jedi (Debug Information) #9235

Closed davidhalter closed 3 years ago

davidhalter commented 4 years ago

Some VSCode users have recently come forward with issues that I wasn't able to reproduce in Jedi with my environment (like https://github.com/davidhalter/jedi/issues/1454).

@karrtikr told me that you guys might explore the possibility of stdout/stderr logging. IMO this would probably be enough. However in general, it's probably more helpful to have the debug information.

One of the most helpful things you guys could do would be to enable stdout/stderr logging in combination with a switch where users could enable jedi.set_debug_function(). You could also implement the debug function yourself and pass it instead of capturing stdout/stderr: jedi.set_debug_function(mydebug_function).

If you could explore something like this, I would probably be able to help you guys fix some more issues. Thanks!

brettcannon commented 4 years ago

Thank you for the suggestion! We have marked this issue as "needs decision" to make sure we have a conversation about your idea. We plan to leave this feature request open for at least a month to see how many 👍 votes the opening comment gets to help us make our decision.

karthiknadig commented 3 years ago

Now that we are switched over to purely Jedi behind LSP in main, this should probably be handled with jedi-language-server project. Currently we have LSP logging that is used by pygls print out logging for the LS. jedi-language-server could use something similar to send over jedi logs.