One thing that came to me as news is that the command which—which is the de-facto tool to
find the path of an executable—is not POSIX compliant. The recent Debian debacle1 around
which brought it to my attention. The POSIX-compliant way of finding an executable program
is command -v, which is usually built into most of the shells.
So, instead of doing this:
which python3.12
Do this:
command -v which python3.12
— ⁂ —
Recent posts
- Hierarchical rate limiting with Redis sorted sets
- Dynamic shell variables
- Link blog in a static site
- Running only a single instance of a process
- Function types and single-method interfaces in Go
- SSH saga
- Injecting Pytest fixtures without cluttering test signatures
- Explicit method overriding with @typing.override
- Quicker startup with module-level __getattr__
- Docker mount revisited