-
Notifications
You must be signed in to change notification settings - Fork 320
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
Analyzer Python compatibility check might fail, resulting in Python2 fallback #4289
Comments
Another important issue is that it is not clear which package manager is being run and with which python version. Without any previous knowledge of the code and as a noob user, I had to write some debugging code in the Pip.kt code to show the python version being used and found this
Possible improvements / suggestions
|
This is a fixup for c885541. Not relying on the script anymore implicitly resolved issue #4289. Signed-off-by: Sebastian Schuberth <[email protected]>
This is a fixup for c885541. Not relying on the script anymore implicitly resolved issue #4289. Signed-off-by: Sebastian Schuberth <[email protected]>
The |
If there is an error with parsing the Python file into a Python3 ast, the
python_compatibility.py
script fails:ort/analyzer/src/main/resources/scripts/python_compatibility.py
Line 46 in ee69cd7
I wasn't able to debug this on first glance. Perhaps I should have enabled debug level logging to get a proper warning. I'm now trying to debug this issue some more to come up with ideas for usability improvements.
Thanks to @edulix for pinpointing the issue.
Possible improvements
print(e)
python_compatibility.py
script locally to find the troublesome filesThe text was updated successfully, but these errors were encountered: