mssql-cli refers to "python" directly, which may not be available.

The startup script tries to run `python` (https://github.com/dbcli/mssql-cli/blob/67a3a4364383d11776bb0a397ceae7bc19200e41/mssql-cli#L16)
This is not available in some environments. For example fedora uses only version-specific `python3`. [PEP-0394](https://peps.python.org/pep-0394/) says basically that `python3` is more likely to exist than bare `python` (which may not be guaranteed to point at python3)

But the ideal solution would be to generate an entry point that uses the "current installation" python, like pip and other apps do. So when I install mssql-cli in a venv, the binary points at the local python, not my system one.

Start with the startup script at mssql-cli#L16 and inspect how the project packages and installs its command entry point. Done means an installed mssql-cli uses the current installation's Python, including in a virtual environment, without relying on a bare `python` executable; verify behavior in an environment where only version-specific Python is available.

Scritto dal modello di indicizzazione a partire dal testo della issue.