Looking at this again, I believe this bug may have been fixed (or at
least mitigated) in Sage 9.1, which introduced some changes to the
`sage` entrypoint around the `exec` commands I identified in my original
report. More specifically the changes introduced by this commit:
https://github.com/sagema
Public bug reported:
## Expected behavior:
Running `sage` after installing the `sagemath` command starts Sage, even
if `python3` resolves somewhere other than `/usr/bin/python3` (examples
of when it doesn't: virtual environments, use of the conda package
manager, pyenv)
## Actual behavior:
```
