Anthony Sottile
Anthony Sottile
weird -- well if you can come up with a reproducible way to get into the state please comment back!
install / binstall is off topic for this issue -- this issue is about removing `cargo add`
the current default language version uses heuristics about what your python thinks it is -- if it defines itself as "python3" that's what pre-commit will go with (this is common...
your PR and issue are fairly aggressive in tone, please dial it back a notch. everything is currently working exactly as designed and you're being surprised by your python reporting...
> to ask for clarification on your comments. if this is your intent you're not doing a great job at it -- I see very few questions and many attempts...
> Finding sys.version[:2] would only be the first step, after which we'd need to make some executable name that we could attempt to locate. Since the main goal for this...
your `language_version` is `python3` -- when you built it that was satisfied by 3.9.16 -- that will continue to be cached at `python3` -- it's not going to magically understand...
to reiterate -- there isn't a bug in the caching -- you've just provided it a not-specific-enough key
hmm that feels like a pretty annoying regression in npm itself :S -- the output used to be on stdout in the past and was "fixed" in npm 7, seems...
fwiw the other failure is likely the same as #3261 -- a bug in node