As discussed with @jgmelber. This reverts to pulling the latest nightly wheel instead of whatever version was previously fixed in quick_setup.sh.
We decided that using the latest wheel of main should be sufficiently stable, and it is preferrable to have everyone on the latest version. People trying to run bleeding-edge programming examples from the repo with an outdated compiler pulled from quick_setup.sh has lead to a lot of headaches, and keeping the version in quick_setup.sh updated is laborious.
There are arguments to keep a version hard-coded in quick_setup.sh, s.t. the repository commit and compiler commit are coupled together, but it seems generally using latest seems to be a better trade-off.
Another stage of this could be to only release wheels after testing them and passing all tests (but this might be redundant with the tests we run on main already anyways).
As discussed with @jgmelber. This reverts to pulling the latest nightly wheel instead of whatever version was previously fixed in quick_setup.sh.
We decided that using the latest wheel of main should be sufficiently stable, and it is preferrable to have everyone on the latest version. People trying to run bleeding-edge programming examples from the repo with an outdated compiler pulled from quick_setup.sh has lead to a lot of headaches, and keeping the version in quick_setup.sh updated is laborious.
There are arguments to keep a version hard-coded in quick_setup.sh, s.t. the repository commit and compiler commit are coupled together, but it seems generally using latest seems to be a better trade-off.
Another stage of this could be to only release wheels after testing them and passing all tests (but this might be redundant with the tests we run on main already anyways).