-
-
Notifications
You must be signed in to change notification settings - Fork 529
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
ERROR: InterpreterNotFound: pypy #48
Comments
Original comment by @hpk42 I've applied your fix and added a test. thanks. |
Original comment by @hpk42 can you provide a download/repository including the tox.ini and a full output of a tox run? |
Original comment by @mchaput Yes, it's definitely on the path. It's in the PATH variable and as I said I can type pypy on the command line to run it. My [testenv] section //does// have deps=nose. |
Original comment by @hpk42 Usually tox finds pypy.exe if it is on the path. Are you sure it's on the PATH? As to the pasted output you should make sure to define deps=nose in your [testenv] section to avoid picking up global installation which might or might not be present. |
Original comment by @mchaput No, same error. If I do {{{ it doesn't work either. But if I do {{{ I get the following: {{{ ...then it proceeds to run the tests. |
Original comment by @hpk42 Does it work if you add a section like this: [testenv:pypy] }}} ? |
On my Windows box I have pypy.exe in the path (i.e. typing
pypy
at the command line works), but if I addpypy
to the tox envlist, I getThe text was updated successfully, but these errors were encountered: