How to download the .vsix file for older versions?

[Jmateusribeiro]

Hi, How can I download the .vsix file of version 2022.16.1?

In the version history of the extension, there's just versions greater than 2022.19.13111132

[brettcannon]

You can modify the URI template https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ms-python/vsextensions/python/{version}/vspackage by replacing {version} with the version you want to download, e.g. https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ms-python/vsextensions/python/2022.16.1/vspackage for 2022.16.1.

If you don't know which version you want and you have specific VS Code version restrictions, see the comment below on how figure out which version of the extension you want.

[Jmateusribeiro]

Perfect! Many Thanks

[khtad]

I see the source for the extension, but I don't see the actual .vsix files. Is that an oversight on my part, or do I need to build them with node.js?

[brettcannon]

@khtad the VSIXs are at marketplace.visualstudio.com as outlined above.

[andrewivan123]

How do i get the linux versions?

[brettcannon]

The VSIXs are platform-agnostic, so there is no specific Linux version.

[gabry801]

Is there a way to "browse" all the older available ?? (eg: browse all 2022.20.x or 2021.x.y)

[brettcannon]

https://github.com/microsoft/vscode-python/releases lists all the releases we have made.

[dschuster-ae]

yeah, but they don't build the .visx, as far as I can see.

[brettcannon]

To tell what version of the extension is definitely supported by a specific version of VS Code, you can look at https://github.com/microsoft/vscode-python/releases and align the N.M.0 release to the date of the VS Code release (we always aim to release the same day as VS Code), then grab the latest bugfix version for that release. So for VS Code 1.74, that was released in December 2022 (it's called the "November release" because the bulk of the work was done in November). If you check the release date for 2022.20.0, you will see they align. You then might notice there's a 2022.20.1 bugfix release which is also compatible.

If you want to know how to tell definitively, pull up the tag for a release and check https://github.com/microsoft/vscode-python/blob/main/package.json for the engines.vscode version compatibility with VS Code (so the "vscode" key within the "engines" key). That SemVer compatibility expression is what the Marketplace uses to decide what version of the extension to give you automatically in VS Code (this obviously doesn't work when downloading manually).

[illbebach]

When I look at the https://github.com/microsoft/vscode-python/releases I see release numbers like

• 2023.8.0
• 2023.6.1
• 2023.6.0
  etc.

Yet when I visit the marketplace page at https://marketplace.visualstudio.com/items?itemName=ms-python.python I see a completely different version history. Such as:

• 2023.9.11371007
• 2023.9.11361009
• 2023.9.11351004
• 2023.9.11321009
• 2023.9.11311005

We have a built a utility to download many extensions using the marketplace pages, for offline use. Yet this one extension directs us to versions above, which appear to always be pre-release versions.

Can you get the versions on the Marketplace page to match the versions in Release?
Thanks

[brettcannon]

We do automatic pre-releases almost every weeknight, hence all of the 2023.9 releases that push stable releases out of view. We don't control the Marketplace, so there isn't anything we can do about what gets listed on the website (we have filed a feature request to make the distinction between pre-release and stable), but the stable releases are still available even if they are not listed.

Do note that any even-number minor version is a stable release and an odd number is a pre-release.

[Maximigz]

Can VS code have a functionality to automatically check the compatibility and present only the available extensions for the particular VS Code version?
And 2. Can someone think of a script or a diagnosis function to test the issues with XHR and present the most relevant solutions?

[brettcannon]

@Maximigz that would be a feature request on VS Code if you're wanting that while looking in the extension explorer (I don't see how you could do that in the browser since it has no idea what version of VS Code you're running).