Open SwapnilGaikwad opened 3 years ago
@SwapnilGaikwad thanks for reporting the issue @dougxc please advise
@sanzinger is this something already being taking care of with the work to migrate mx and Graal to python 3?
FWIW, I recently changed some of our internal gates to use python3 for pylint, and it seems to work fine with the current version. Not sure what exact python version we're using there, it might be older than 3.8.10.
See https://github.com/oracle/graal/commit/e90430bfc11dd77ac718931fc6215fb95333292e for the change. Might make sense to do this for all our gates, including the GH actions ones.
I just had to explicitly install isort
from pip to work around https://bugzilla.redhat.com/show_bug.cgi?id=1710221, which we seem to be hitting at least in some of our internal CI machines.
That said, I also wouldn't be opposed to updating to a newer pylint version ;)
Describe your environment :
java -Xinternalversion
:Describe the issue
MX_PYTHON_VERSION=3
however, the python packages used for stylechecks, e.g., pylint, are usingpython2.7
. Graal is using pylint 1.9.3 at the moment that fails when installed with python3. Therefore, while switching to python3 fully in GitHub Actions, we will need to update pylint to newer version.AttributeError: 'Import' object has no attribute 'infer_name_module'
error.compiler/mx.compiler/mx_compiler.py
.Code snippet or code repository that reproduces the issue
Output
Output
Output
Expected behavior It would be helpful if Graal uses python3 throughout its CI system including mx & the gates it executes. Current GitHub actions extract python package dependencies from mx/common.json. Therefore, switching to python3 may require updates to both mx and Graal in sync to avoid CI failures.