Fixed backwards compatibility checker#12181
Conversation
|
|
||
| cd /work/venv | ||
| virtualenv -p python3 | ||
| source /work/venv/bin/activate |
There was a problem hiding this comment.
If we do a virtualenv why not do pip install instead of exporting PYTHONPATH?
Also, why not relative paths?
There was a problem hiding this comment.
python, python2, python3 are different now, as their corresponding pip, pip2, pip3
Maybe it would be better to make 2 different virtual env's for python2 and python3. Will try that.
There was a problem hiding this comment.
Why do we want to go for a virtual env here ?
There was a problem hiding this comment.
Nevermind. It was just an attempt to insure python and pip are in sync.
lebeg
force-pushed
the
fix_bcc
branch
2 times, most recently
from
981ff8c to
0d6c687
Compare
| version=$1 | ||
| echo "Installing MXNet "$version | ||
| pip install mxnet==$version --user | ||
| pip3 install mxnet==$version --user |
There was a problem hiding this comment.
Does this resolve the Python module not found issues we are seeing in the MBCC Train Stage on Jenkins ?
|
Can you please indicate the testing done? |
|
Closing due to #12223 |
4 participants
Description
The script was reporting missing mxnet installation.
Checklist
Essentials
Changes