In PR #287 it was observed that the following step fails for the Linux build:
pip install -e ".[examples]"
suggesting a mismatch between the Azure python environment and that running in the Docker container. @rth and @ulupo suggested that applying python -m is a better practice (see also here), but this did not solve the Linux problem.
The goal of this story is to systematically implement this best practice in our CI. Bonus points are included if the Linux build issue can be resolved so that the Jupyter notebooks test does not require manual specification of the packages.
Description
In PR #287 it was observed that the following step fails for the Linux build:
suggesting a mismatch between the Azure python environment and that running in the Docker container. @rth and @ulupo suggested that applying
python -m
is a better practice (see also here), but this did not solve the Linux problem.The goal of this story is to systematically implement this best practice in our CI. Bonus points are included if the Linux build issue can be resolved so that the Jupyter notebooks test does not require manual specification of the packages.