Riot

Bug Fixes

- Fixed the `shell` command to use the correct virtual environment instead of always defaulting to the base one.

Bug Fixes

- Fix issue with `riot shell` not passing required environment variables
- Fix issues with `riot shell` always trying to source `~/.bashrc`

New Features

- The shell command now uses the system default shell as specified by the `SHELL` variable instead of enforcing the use of bash.

New Features

- Inject riot virtualenv instance data into each run via environment variables:
- `RIOT`: always set to `"1"`
- `RIOT_PYTHON_HINT`: the Python version hint provided to riot, e.g. `"3.6"`
- `RIOT_PYTHON_VERSION`: the actual Python found/used by riot, e.g. `"3.6.10"`
- `RIOT_VENV_HASH`: the short hash for the running virtualenv instance, e.g. `"d36fc71"`
- `RIOT_VENV_IDENT`: the string identifier used to create the virtualenv, e.g. `"pytest_pytest-cov_mock_typing-extensions"`
- Note: This is only set if the virtualenv instance has defined packages
- `RIOT_VENV_NAME`: the name of the virtualenv instance running, e.g. `"test"`, `"mypy"`, etc
- `RIOT_VENV_PKGS`: the string of packages + versions this virtualenv instance provided to the `pip install` command, e.g. `"'pytest' 'pytest-cov' 'flask>=2.0.0'"`
- Note: this may be empty if only parent virtualenv packages are used
- `RIOT_VENV_FULL_PKGS`: the full list of packages this virtualenv instance and all of it's parents provided to the `pip install` command, e.g. `"'pytest' 'pytest-cov' 'flask>=2.0.0'"`

- Add short hash to command summary.

New Features

- Match pattern against `VenvInstance.name` and `VenvInstance.short_hash`. This allows you to `riot run <hash>` to run only a specific instance.

See release notes for more details: https://ddriot.readthedocs.io/en/latest/release_notes.html#release-notes-0-9-0