Run python -m pip instead of pip

[Tonkonozhenko]

When you try to run pip in venv in a directory with a long full path you get an error. To avoid this you need to run python -m pip instead of pip.

[sdispater]

Thanks!

Could you execute black on the poetry/console/commands/develop.py file to make the build pass on Travis?

Also, could you rebase your PR on the develop branch?

[Tonkonozhenko]

I've fixed formatting, but I'm getting an error in travis, hope you can help with it.

[daa]

I had similar issue with tox and found it to be better to call /path/to/python/python /path/to/pip/pip or to put virtualenv to directory with shorter name. Related tox ticket with conversation - https://bitbucket.org/hpk42/tox/issues/66/tox-shouldnt-call-pip-directly-to-avoid .

[daa]

I'd like to inform you that tox recently got a workaround for such cases - tox-dev/tox#794

[daa]

And recently tox moved to using python -m pip by default (tox-dev/tox#935).

[brycedrennan]

@Tonkonozhenko Thanks for this contribution!

To get this across the finish line we need to do the following:

Update the mock used in testing here
Manually test that this works when not mocked

[debdolph]

Works for me. Thank you!

[ghost]

Hello. How should we proceed with this PR?

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[K900]

FYI, this is completely obsoleted now.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.