konsti

> If we want to use python and be compatible, we should just use the raw output of platform.mac_ver()[0]. That should take care of the test failing right now. Sounds...

As @samypr100 said, we should pass `platform.mac_ver()[0]` verbatim next to the parsed major/minor and use it in the linehaul information, but i don't have reference devices for `platform.mac_ver()[0]`

Thanks I'm merging it now with the `.` formatting for mac, it's easy enough to change later.

Found an upstream bug: https://github.com/axodotdev/axoupdater/issues/34

Thinking about https://github.com/axodotdev/axoupdater/issues/34 again, should we feature gate the installer, so that pip/conda/distros can turn it off entirely? Seem safer than relying on recipe.

Windows currently uses `C:\Users\Ferris\.cargo\bin`, i expect this to switch to `C:\Users\Ferris\.local\bin`.

> Should it be ~/.astral/bin...? If everybody did that it would require a PATH entry per vendor, which imo would be bad. Normally installing into `~/.astral` and symlinking into PATH...

I've realized this will break people who rely on the current installation location. I'd bundle this with other bigger changes (v0.2 probably) if possible.

@woutervh Is `.local` a hidden folder for you on windows? It looks non-hidden on mine.  @mitsuhiko What made you choose that over `.local/bin`?

What would you think about (sym)linking those binaries to `~/.local/bin`, from the background that it's the XDG standard that users are expected to have in PATH while rye's shim directory...