-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"make python-env" fails on current Homebrew #7489
Comments
@elastic/beats Time to go to python 3? |
As a workaround, one can set
|
Maybe we should set VIRTUALENV_PARAMS in the Makefile for the time being. Having to remember to set an env variable or setup a private virtualenv as workaround is not really user-friendly. |
I have set this variable and it works but it shows the warning: At least, it seems that everything worked as expected for the "make create-metricset". |
Update: now I had to use "export PYTHON_EXE=/usr/bin/python2" too to avoid:
Using "VIRTUALENV_PARAMS", the "make python-env" was fine but for "make update" in metricbeat a "...beats/metricbeat/build/python-env/build/ve/" directory was created using python3. So I check the dev-tools/mage/pytest.go source and then set the PYTHON_EXE variable for him. |
This should be fixed by #14798 |
#14798 finished, we are now in the Python 3 age 🙂, what should solve this problems. |
Since some time,
python
defaults to Python 3 when using Homebrew on OSX. Python 3 is also the default on Ubuntu 18.04.make python-env
defaults to usepython
, and when that points to a Python 3 binary, promptly fails, trying to installfunctools32
:beats/libbeat/tests/system/requirements.txt
Line 13 in a8da186
Even after fixing that (and
enum34
), the tests and other Python scripts won't run on Python 3 (see #5950).As a workaround, one can create the virtualenv manually using Python 2
The text was updated successfully, but these errors were encountered: