Warnings are emitted when running tox for the second time

[thedrow]

Because of #5 I tried to run tox without this plugin first.
I get the following warnings:

WARNING:test command found but not installed in testenv
  cmd: /home/omer/.local/share/virtualenvs/myproject--RkZn49j/bin/python
  env: /home/omer/Documents/Projects/myproject/.tox/py36
Maybe you forgot to specify a dependency? See also the whitelist_externals envconfig setting.
py36 inst: /home/omer/Documents/Projects/myproject/.tox/dist/myproject-0.1.0.zip
WARNING:test command found but not installed in testenv
  cmd: /home/omer/.local/share/virtualenvs/myproject--RkZn49j/bin/pip
  env: /home/omer/Documents/Projects/myproject/.tox/py36
Maybe you forgot to specify a dependency? See also the whitelist_externals envconfig setting.
WARNING:test command found but not installed in testenv
  cmd: /home/omer/.local/share/virtualenvs/myproject--RkZn49j/bin/pip
  env: /home/omer/Documents/Projects/myproject/.tox/py36
Maybe you forgot to specify a dependency? See also the whitelist_externals envconfig setting.

After that, pytest runs normally.

[tonybaloney]

Which version of tox-pipenv are you running? This is just a warning that the temporary virtualenv path (which is a random folder created by pew) is not within the .tox subdirectory.

This issue should be resolved in 1.2.0

[thedrow]

I'm using tox-pipenv 1.2.1.

[tonybaloney]

I did dig into this, the warning doesn't impact the use case, it means that the command you're running isn't within the tox "whitelisted" directories. Because of where pipenv is typically installed into you'll see this on build.
The test should work as desired.

Need to look into how to add the commands to the whitelist

[tonybaloney]

The warning is specific to the pip and the python binaries that pipenv will use.

One option would be to do a "which pip" and add it to the whitelist and some equivalent for Windows

[kevinkjt2000]

To get rid of these warnings, I added this line to my [testenv]:

whitelist_externals = {homedir}/.local/share/virtualenvs/bowser-*

I think that if this plugin somehow overrode the {envdir} tox variable, then there would be no need for the user of tox-pipenv to do any extra work. I also have no idea how difficult that would be compared to the one-liner above.