virtualenv-2.7 hardcoded

[dusty-phillips]

_ensure_virtualenv is assuming that the command virtualenv-2.7 is available, however on my platform it's just called virtualenv. Possibly this should be configurable somewhere, although assuming that the virtualenv command is available should also be safe, since a virtualenv-3.x binary should still be able to create python2.7 capable environments.

Similarly, hardcoding python2.7 is probably fragile in this method, as it may variously be named python, python2, or hippopotamus on different machines.

[dusty-phillips]

I'm getting a similar problem under Fedora now (when I reported this, I was using Arch Linux). The problem now is that viltualenv is not creating a pip-2.7. There is a pip and a pip2.7, but no pip-2.7 in the venv. I cd .buildozer/venv/bin and ln -s pip2.7 pip-2.7 and buildozer works, but this should obviously be automatic.

[inclement]

This was a python-for-android bug, resolved by kivy/python-for-android@5a5e8ea. It adds checking for multiple sensible name possibilities for both pip and virtualenv.