ERROR: InterpreterNotFound: pypy

Issue #48 on hold
Matt Chaput
created an issue

On my Windows box I have pypy.exe in the path (i.e. typing {{{pypy}}} at the command line works), but if I add {{{pypy}}} to the tox envlist, I get

{{{
ERROR: InterpreterNotFound: pypy
}}}

Comments (10)

  1. Matt Chaput reporter

    No, same error. If I do

    [testenv:pypy]
    basepython=c:/pypy/pypy
    

    it doesn't work either. But if I do

    [testenv:pypy]
    basepython=c:/pypy/pypy.exe
    

    I get the following:

    GLOB sdist-make: E:\My Dropbox\workspace\whoosh\setup.py
    pypy sdist-reinst: E:\My Dropbox\workspace\whoosh\.tox\dist\Whoosh-2.5.0.zip
    WARNING:test command found but not installed in testenv
      cmd: C:\Python27\Scripts\pip.EXE
      env: E:\My Dropbox\workspace\whoosh\.tox\pypy
    Maybe forgot to specify a dependency?
    pypy runtests: commands[0]
    WARNING:test command found but not installed in testenv
      cmd: C:\Python27\Scripts\nosetests.EXE
      env: E:\My Dropbox\workspace\whoosh\.tox\pypy
    Maybe forgot to specify a dependency?
    

    ...then it proceeds to run the tests.

  2. Holger Krekel repo owner

    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.

  3. Matt Chaput reporter
    • changed status to open

    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.

  4. Log in to comment