vscode-extensions.ms-python.python: 2025.3.2025031001 -> 2024.15.2024091301

[r-ryantm]

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

meta.description for vscode-extensions.ms-python.python is: Visual Studio Code extension with rich support for the Python language

meta.homepage for vscode-extensions.ms-python.python is: https://github.com/Microsoft/vscode-python

meta.changelog for vscode-extensions.ms-python.python is: https://github.com/microsoft/vscode-python/releases

Updates performed

• Ran passthru.UpdateScript

To inspect upstream changes

Impact

Checks done

---

• built on NixOS
• The tests defined in passthru.tests, if any, passed
• found 2024.15.2024091301 with grep in /nix/store/97ddnz922r1zvc4n11qrafkddxzxjg34-vscode-extension-ms-python-python-2024.15.2024091301
• found 2024.15.2024091301 in filename of file in /nix/store/97ddnz922r1zvc4n11qrafkddxzxjg34-vscode-extension-ms-python-python-2024.15.2024091301

---

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

vscode-extensions.ms-python.python

Instructions to test this update (click to expand)

---

Either download from the cache:

nix-store -r /nix/store/97ddnz922r1zvc4n11qrafkddxzxjg34-vscode-extension-ms-python-python-2024.15.2024091301 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.

Or, build yourself:

nix-build -A vscode-extensions.ms-python.python https://github.com/r-ryantm/nixpkgs/archive/709289df7096cbda811d4e358e88ace3e1286189.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/709289df7096cbda811d4e358e88ace3e1286189#vscode-extensions.ms-python.python

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/97ddnz922r1zvc4n11qrafkddxzxjg34-vscode-extension-ms-python-python-2024.15.2024091301
ls -la /nix/store/97ddnz922r1zvc4n11qrafkddxzxjg34-vscode-extension-ms-python-python-2024.15.2024091301/bin

---

Pre-merge build results

We have automatically built all packages that will get rebuilt due to
this change.

This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review

---

x86_64-linux

✅ 1 package built:

• vscode-extensions.ms-python.python

---

Maintainer pings

cc @jraygauthier @jfchevrette for testing.

Tip

As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

---

Add a 👍 reaction to pull requests you find important.

[jfchevrette]

@JohnRTitor this looks like a version downgrade

It happened with #389525 too

[JohnRTitor]

OOF. What is wrong with these PRs, and my fault again for not being careful

[JohnRTitor]

Okay, so any idea what's happening here?

Two times doesn't seem like a coincidence, is the updateScript broken? Updates every other thing correctly though, CC @drupol @emaryn as they are involved with #389585

[emaryn]

https://github.com/r-ryantm/nixpkgs/blob/709289df7096cbda811d4e358e88ace3e1286189/pkgs/applications/editors/vscode/extensions/ms-python.python/default.nix#L74

^1.94.0-20240918 does not match the regular expression test("\\^[0-9.]+$").

[drupol]

@JohnRTitor : @emaryn and I have been working on a Python script to update any VSCode extension based on the current VSCode version, you can find it here: #389585

I have no clue on how we could use that script by default to update all the extensions correctly, feel free to have a look.