Mark Blakeney

I see that subsequent new release 20240726 fixes the observations mentioned above about the missing/wrong binaries in 20240725 - although that is tangential to the issue raised here.

Why would it be stale? That independent file (which is not part of any release) points to the latest release and should be updated immediately after a new promotion is...

Again, at the present time, https://raw.githubusercontent.com/indygreg/python-build-standalone/latest-release/latest-release.json points to 20241205 release but the current release is 20241016 which breaks my update tool. I still don't understand how this can be a...

Ok, sorry about that. I know little about Github automation/actions so can't really contribute. From what you are saying it seems that metadata file would be not be part of...

To be clear, that file can be fetched and checked very quickly so I can do that (cached for a short period of course) without using the Github API. I...

The only other option I can think of is to not use that file and instead scrape the first release page but that is ugly and slow. I assumed that...

@hugovk thanks - at first sight those links look promising as a replacement for `latest-release.json` but upon inspection it appears they suffer from the same problem. I.e. each release is...

In case anybody else is interested, I found a solution for this. I simply fetch https://github.com/astral-sh/python-build-standalone/releases/latest which redirects to what Github mark as "latest" on the release page then catch...

When you are using a fuzzy finder with any kind of command line tool then you want the prompt to be at the bottom on the terminal close to where...

@mscolnick , the `python-lsp-server` is installed in the same `venv`, e.g: ``` $ uv tool install marimo[recommended,lsp] Resolved 65 packages in 66ms Installed 65 packages in 32ms + altair==5.5.0 +...