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
don't rely on distutils.sysconfig directly to determine Python lib dir #156
Conversation
reviewed, looks good. |
…hrough run_cmd to get correct version
@fgeorgatos: You reviewed too early. ;-) |
"""Prepare by determining Python site lib dir.""" | ||
|
||
# we can't simply import distutils.sysconfig, because then we would be talking to the system Python | ||
cmd = ' '.join(['python -c "', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if you think it helps readability, being the dict one line below (as we do in other dictionary items);
other than that, I have no more remarks, at least from a visual check of the code. It seems like a code factorization effort, good.
@boegel looks fine by me |
Fixed bugs, tested, works as expected now, so merging it in. |
don't rely on distutils.sysconfig directly to determine Python lib dir
We shouldn't rely on
distutils.sysconfig.get_python_lib()
directly to determine the Python library dir 'lib/python%(python_version)s/site-packages', since that will return the value for the system Python, not for the Python module that was loaded.