Makefile used pip instead of pip3


#1

Not sure if I did something wrong, but following through the docs and running

make requirements

It installed all the requirements under python2 instead of python3. When running the demo, the modules weren't present. I had to go back and install the requirements using pip3 to get it running. Is this intended behavior?


#2

It's not intended, thanks for the report!

I'm not 100% sure pip3 is always the name of pip on all platforms... but I think it's easiest to just change it in the Makefile, and I'll do that now.

I'm usually using a virtualenv in development, when that won't happen.