Create environment with lock file?

[acwooding]

When running make create_environment it seems to be using the lock file:

/bin/conda env update -n covid_nlp -f environment.i386.lock.yml
Collecting package metadata (repodata.json): done
Solving environment: done

is this intended behaviour? I ended up having to run make update_environment after because not everything I needed was installed in the checked in lock file (this was done in the covid_nlp repo)

If we do mean to do this, we should probably have some form of CI running that checks if all the packages in the environment.yml are installed in the lock file, or else give instructions to run make update_environment after.

[acwooding]

Don't fix this quite yet. This produced the wacky jupyter conda kernel bug.

[hackalog]

This fixed some behavior, broke other things. Really, you need to do an initial update_environment after the creation to enable the editable pip package, but you need to touch environment.yml first to make that work. I'll have to refactor this makefile again to try and fix.