|
When performing C/C++ extraction, LGTM tries a bunch of things, and apparently does I tried explicitly setting Python 3, but this apparently did not affect the C/C++ side. PS, why is it so hard to figure out where to report issues with LGTM? I'm not even sure if this is the right place. |
Answered by
tausbn
Jun 18, 2021
Replies: 1 comment 1 reply
|
For this particular case, you could try one of two things
in the (Note: I have not tested the two approaches above. If they don't work, do let us know.) |
1 reply
Answer selected by
criemen
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For this particular case, you could try one of two things
python3 setup.py builddirectly by setting theconfigurestep forcppPATHvariable to put the Python 3 interpreter first. For this, something like puttingin the
before_indexstep might work.(Note: I have not tested the two approaches above. If they don't work, do let us know.)