$ pipenv run --no-interactive

For example, with Docker:

Traceback (most recent call last):
  File "/usr/local/bin/pipenv", line 11, in <module>
    load_entry_point('pipenv==3.3.6', 'console_scripts', 'pipenv')()
  File "/usr/local/lib/python3.6/site-packages/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.6/site-packages/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.6/site-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/pipenv/cli.py", line 962, in run
    c.interact()
  File "/usr/local/lib/python3.6/site-packages/pexpect/pty_spawn.py", line 740, in interact
    mode = tty.tcgetattr(self.STDIN_FILENO)
termios.error: (25, 'Inappropriate ioctl for device')

[relwell]

How about a --no-interactive flag that doesn’t open a new shell?

On Feb 4, 2017, at 2:25 PM, Kenneth Reitz [e-mail] wrote:

or perhaps we can add a flag to run (e.g. $ pipenv run pytest --which), which would output the path to the executable, for environments like Docker.

― You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[techalchemy]

@marioBZ7 sorry, I didn’t realize the issue with ‘interactivity’ isn’t that you don’t want to give input (which is what PIPENV_YES addresses) but instead that you just need to use pipenv in docker.

I don’t know what you’re talking about

I would ask that you be a bit courteous, we are triaging a lot of issues and since most of them come down to a simple answer we don’t always invest a lot of time in each one.

This is a decent overview of how to use pipenv in docker, but essentially you will want to pass --system to prevent the creation of a virtualenv at all.