Make commands operate in current shell environment (not necessarily in the project Python environment)

I exploring further the tool and I have two comments:

If the default python of the system is version 3.x, and a new project with version 2 is chosen, then the environment testing fails. The reason is that it tries to use the global python which is version 3.x.

Second issue, after creating the environment (assuming no problem with the python version), then make requirements uses the global pip and thus installs everything into the root of conda. I either missed something, or there's some wrong in the flow. It seems not to be possible to activate a conda environment from within the Makefile. So, basically, the user has to activate the environment before runing make requirements.

What do you think?