-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Allow Pylance to be used with Python 2 if explicitly chosen #16210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@@ -200,16 +204,17 @@ suite('Python Settings', async () => { | |||
settings.update(config.object); | |||
|
|||
expect(settings.languageServer).to.be.equal(expectedValue); | |||
expect(settings.languageServerIsDefault).to.be.equal(isDefault); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a basic test of the settings, but this settings test doesn't bother using IDefaultLanguageServer, which is dubious.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
configSettings needs a clean up. It has lots of minor issues that keep causing problems. We will address these when we get to that clean up.
* Cherry-picks into release from main (#16181) * Update pygls dependency (#16165) * Upgrade all packages (#16180) * Update release version (#16196) * Update change log version * Allow Pylance to be used with Python 2 if explicitly chosen (#16210) (#16214) * Update version and change log. (#16237) * Fix Pylance Python 2 mistake (#16246) * Update version and change log for second point release Co-authored-by: Jake Bailey <[email protected]>
For #16204.
I didn't change the logic for jedi, as it will quite literally crash. Pylance doesn't need Python to run, so is safe to use (even if the analysis may not fully understand Python 2).