Run python file in pipenv environment fails

[DonJayamanne]

• Use pipenv for current environment
• Run python file in terminal
  • Open python file , right click and use the menu option Run Python file in terminal
  • The terminal will now open automatically
  • Python Extension will send the text pipenv shell to activate the environment in the terminal
  • The python extension will send the text <python interpreter> <file name> to the terminal
  • Unfortunately there's a race condition here, pipenv shell has not yet completed, and the commands sent later get swallowed up
• End result, file doesn't run in terminal

Causes:

• There's no way to determine when terminal has completed processing previously sent commands.
• VSC is sending messages to the terminal, when its busy

Solutions:

• Python extension adds a delay between the two commands being sent to the terminal (this is what we do today). However pipenv shell takes longer than other activation routines, hence we need a much longer delay (i.e. a bigger magic number), a work around.
• Or, VSC provides some api to let us know the terminal is ready to accept input.

microsoft/vscode#67693

[powellquiring]

I believe I'm stuck on this. In the terminal I see this:

~/om/github.ibm.com/pquiring/vpcibm$ pipenv shell
Launching subshell in virtual environment…
 . /Users/pquiring/Envs/vpcibm-spz4F-UA/bin/activate
~/om/github.ibm.com/pquiring/vpcibm$  . /Users/pquiring/Envs/vpcibm-spz4F-UA/bin/activate
(vpcibm) ~/om/github.ibm.com/pquiring/vpcibm$

How do I work around this? Is it possible to just hard code the python environment? I've had things set up with a specific python and it worked in the past few weeks, but this no longer works:

    {
      "name": "Python vpcibm.py",
      "type": "python",
      "request": "launch",
      "program": "vpcibm.py",
      "console": "integratedTerminal",
      "pythonPath": "/Users/pquiring/Envs/vpcibm-spz4F-UA/bin/python"
    }

The terminal window displays:

 . /Users/pquiring/Envs/jupyter-f2acqZjX/bin/activate
~/om/github.ibm.com/pquiring/portfolio-inbound/scenarios/roadmap/vpc/jupyter$  . /Users/pquiring/Envs/jupyter-f2acqZjX/bin/activate
(jupyter) ~/om/github.ibm.com/pquiring/portfolio-inbound/scenarios/roadmap/vpc/jupyter$

[DonJayamanne]

Solution:

Use new VSC API (proposed API at the time of writing this) to check what information has been written out into terminal before sending other commands.

See here microsoft/vscode#67693 (comment)

[karrtikr]

Closing in favor of #16988, we also are no longer using pipenv shell command.