Closed mathstuf closed 6 years ago
Hrm. Seems that breaks CI :/ . How does the Python have a virtualenv
, but no python -m virtualenv
?
The module in the stdlib is called venv. I don't know if presenting the module as virtualenv is a Fedora thing or you might have the external version of this module installed. You can probalby find this out with something like rpm -qa | grep virtualenv
.
venv
is available since Python 3.3. Unfortunately syncserver currently only supports legacy Python.
I think it would be bad to just assume there will be Python 3 available everywhere - especially if things are run in any sort of container.
That's the case in Python3, but I'm still running it with Python2 (since that's the only supported version anyways).
Sorry, probably got carried away with the Python 3 way. Tested it on my Debian box and the change works as desired.
For the Travis builds I think the problem we are running into is that they are starting out in an virtual environment and there seems to be no virtualenv available inside. Adding it to the install sections for Travis seems to fix the problem - see my test commit on top of your change (test results).
Thanks @mathstuf, this change looks reasonable to me, please try including @okin's fix for CI and I'll be happy to merge.
Thanks @mathstuf, this change looks reasonable to me, please try including @okin's fix for CI and I'll be happy to merge.
Thanks @mathstuf, this change looks reasonable to me, please try including @okin's fix for CI and I'll be happy to merge.
I cherry-picked @okin's commit and touched up the commit message a bit.
virtualenv
on Fedora is now a Python3 tool. Without installing Python3, there is novirtualenv
tool. Instead, just rely on the package being installed.