Mainly because you can't run pip3 install -c requirements-lock.txt on its own it seems. It requires the -r flag.
That is a lot more inconvenient than running `bundle install` and if you use Docker it gets a lot more tricky because a new lock file would get generated on every build which kind of defeats the purpose of it, because ideally you'd want to use the existing lock file in version control, not generate a new one every time you build your image.
Otherwise pip freeze won't find any dependencies.
So you end up having to run something like this:
Mainly because you can't run pip3 install -c requirements-lock.txt on its own it seems. It requires the -r flag.That is a lot more inconvenient than running `bundle install` and if you use Docker it gets a lot more tricky because a new lock file would get generated on every build which kind of defeats the purpose of it, because ideally you'd want to use the existing lock file in version control, not generate a new one every time you build your image.