live-share

live-share copied to clipboard

Product and Version: VSCode OS Version: Windows Live Share Extension Version: 0.3.1071 Target Platform or Language: Python 3.7.1 32 Bit

Steps to Reproduce / Scenario:

1. Log Into Friends Session
2. Watch As VSC says 'No Python Interpreter selected' No matter how many times I click my Python interpreter, it never finds it. Therefor, I cannot compile any code.

Edit. We tested it in reverse; my friend joined me. The same thing happened to him.

Visual Studio Code Bug.zip

@DonJayamanne Does the Python extension have logic for detecting the local interpreter? If so, should we consider disabling that for a Live Share guest? Since they would be getting their language support/build/etc. from the host? And therefore, this dialog could be confusing.

Does the Python extension have logic for detecting the local interpreter?

Yes, can do.

@DonJayamanne Thanks! Let me know if you need anything from our side 👍

This issue has been closed due lack of any recent activity. We've made lots of improvements to Live Share since this issue. Please re-open the issue, if this problem persists. 🤖Live-Share-Clean-Up-Bot🤖

Well the problem still persists, when I try to use live share on google colab

Same issue if I select a python interpreter on live share, VSCode write a config line on .vssettings so my friend's interpreter config is messed. We don't know how to setup a success local running on live share. If I try to run a friend's code my terminal tries to open his file route on my machine so it doesn't exist at all. Any workarround for live share workflow is appreciated. We can only write text remotely on his live share sessions and shared terminals but we cannot manage to get his sharing running locally on our machines.

I can confirm this. Virtual environments do not seem to replicate for guests using the latest live share extension (at least on MacOS host). I can help debug the problem if needed.

Same problem as @alsimist-dev and same offer to help.

@lostintangent, @fubaduba Does this warrant a new issue?

Same issue on Windows 10, with or without virtual environment.

Can confirm this also affects linux users too, though not surprised it's not a platform specific issue. Don't want to overstate it but it's a showstopper for using this plugin with Python.

This issue is not closed, happened to me again yesterday with latest VSCode and Python extension on both Windows 10 and macOS 15. Unfortunately as of now it makes Python unusable with Live Share.

I can confirm that this is still an issue--when joining a Live Share session, VS Code still is unable to find a Python interpreter. Even when trying to select an interpreter, it never seems to do anything. This issue unnecessarily complicates the Live Share experience, as only the host is ever able to run the python program in question.

@lostintangent @fubaduba Can you reopen this issue or create a new one?

I'm running Live Share build: 1.0.266

Still an issue. Happened with macOS host and Linux participant. Cannot select Python interpreter and I can only navigate the shared workspace to look for it..

Re-opening per the comments that this issue still repros. Thanks! 👍

As a temporary workaround, I've been disabling the Python extension for the Live Share workspace.

Any test running, refactoring, etc. must be done by the session leader.

Still an Issue with VSCode

We’re not able to prioritize this issue over the other higher-impact issues we receive every week, based on the votes and comments from others in the community and our understanding of the issue. We understand this may be disappointing; we've all been there, whether in this project or others we've contributed to. However, rest assured that we love your input. If you feel it deserves to stay open, then clarify your use case and contact us to let us know how severe it’s for you.