-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
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
Update vscode python #121072
Update vscode python #121072
Conversation
584a942
to
c93888b
Compare
Result of 2 packages built successfully:
|
This splits off part of the Python extension into Microsoft's jupyter extension, so this is necessary but not sufficient. Signed-off-by: Daniel Silverstone <[email protected]>
This is a necessary dependency of the new Python extension for VSCode. Signed-off-by: Daniel Silverstone <[email protected]>
In order for the ms-python.python extension to work these days, we also need the ms-toolsai.jupyter extension. To permit easy upgrades and to honour the principle of least surprise, we wrapper the Python extension to include the Jupyter one. The reverse is not true, you *can* have the Jupyter extension without the Python one, so the reverse is not also done. Signed-off-by: Daniel Silverstone <[email protected]>
c93888b
to
b71773e
Compare
I have confirmed the closure sizes, checked again against CONTRIBUTING and rebased against current master. |
@jonringer Do you need me to do anything else for this, or is it simply a case of "when you have time to consider it again" ? |
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.
LGTM - mind bumping the Jupyter version and giving it a quick test? Then I'll merge.
vscode-extensions.ms-python.python: revert #121072
Motivation for this change
Microsoft updated their Python extension for vscode in April 2021. This isn't a straightforward upgrade since it splits some of the functionality out into their Jupyter extension (which is also unfree :( )
However if we don't update then anyone installing their vscode extensions via nix will suffer with vscode bugging them about the extension being updatable until they eventually crack and end up with an extension installed in their homedir rather than declaratively.
I tested this via swapping out my "unstable" nixpkgs flake in my system configuration and rebuilding to confirm the new python extension was installed along with the Jupyter one automatically.
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)