Man, the length that people go to break things on windows.
#uv prohibits scripts with name of python3.
Most techniques to create a #python3 alias don't work, so I made the library python3-alias - which can be built with `python -m build` but `uv sync` refuses.
Use cases is a Makefile you don't own has `python3 blah blah` and you can't change it to `py blah blah` or run windows store installs.
If you got a working alternative, I'm curious otherwise, this is more behavior like `sh` library that if you even import it on windows it shits bricks, because, hey if there is even one linux or mac library in the venv you should fdisk the users computer because f*k 'em
♡ 0 ↻ 0I'm trying to think of a better option, but I'm thinking of a few cases where module-does-not-exit is the responsibility of the calling code. But another way to look at it, python has an assumption of being somewhat cross plat and if you do, then all the linux only library should be treated like `[extras]` and if import gets modulenotfound, then you keep going until you attempt to do a thing with the library.
♡ 0 ↻ 0