-
-
Notifications
You must be signed in to change notification settings - Fork 525
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
Unable to run tests against local build of Python #394
Comments
The issue's already been reported as pypa/virtualenv#456. |
@jaraco Thanks for the report. I am triaging bugs atm and if I understand your problem correctly it's not an actual bug in tox, but a question how to work around a problem, until upstream is fixed? If I got it wrong I'll relabel. |
One way to think about it is that the dependence on virtualenv is a cause of the issue. If one were to use venv or rwt as a mechanism for loading dependencies, the issue would not be present. For example, I was able to work around this issue by not using tox:
or
So in that sense, it's more than just a question, but an issue that lies with tox, but for which the solution is almost certainly to be solved upstream. It's conceivable that tox will add an option to use If this were my project, I would want this ticket to remain an open ticket or to be closed but with a label indicating that it's pending an upstream change, with a slight preference for the former given that there are potentially some things tox could do to address the issue. |
@jaraco Thank you for the clarification. We'll definitely leave this open until the issue is solved one way or the other. |
I think this now has been fixed in virtualenv, if not please raise an issue there. |
Due to pypa/setuptools#836, I'm trying to make a local build of Python and test against that. By following the directions for compiling, I've build a local copy in ~/p/cpython/python.exe. In the setuptools checkout, I've updated the config to indicate
basepython=/Users/jaraco/p/cpython/python.exe
(I couldn't use~
as it wouldn't expand that).But now when I invoke tox, I get this error:
I can replicate this error by simply trying to invoke virtualenv:
So it seems the issue is with virtualenv. The same issue doesn't exist with
venv
:When setuptools used pytest-runner, this issue would have been avoided by directly using the local python environment to invoke pytest, but with tox, virtualenv is a requirement.
I guess I need to file a bug upstream, but I welcome any suggestions on how I might be able to work around the issue in tox.
The text was updated successfully, but these errors were encountered: