Skip to content

Debugging program won't start in integrated terminal when using pipenv #4248

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

Closed
rawfox opened this issue Feb 1, 2019 · 1 comment
Closed

Comments

@rawfox
Copy link

rawfox commented Feb 1, 2019

Environment data

Version: 1.30.2 (user setup)
Commit: 61122f88f0bf01e2ac16bdb9e1bc4571755f5bd8
Date: 2019-01-07T22:54:13.295Z
OS: Windows_NT x64 10.0.17763
Python version: 3.7.1
Extension: Name: Python, Id: ms-python.python, Version: 2019.1.0

Expected behaviour

Run python program in integrated terminal

Actual behaviour

Won't start program in integrated terminal. Timeout waiting for debugger connection.
image

Steps to reproduce:

  • create new folder
  • from integrated terminal run command "pipenv install pylint" (inside that folder)
  • create helloworld.py
  • run in mode "Python: Current File (Integrated Terminal)"

Comments and possible cause:

  • Program does work when started in "Python: Current File (External Terminal)" mode
  • First command that gets executed is penv shell, and it used to be ...\activate.ps (What is the reason behind this change?). Seems like command for executing program is broken into two pieces one executing in powershell and the other in pipenv shell. See:

githubissue

  • There is a workaround: stop waiting for debugger (clicking on red square in top right corner), and starting again in same mode:
    image
@ghost ghost added the triage-needed Needs assignment to the proper sub-team label Feb 1, 2019
@DonJayamanne
Copy link

Duplicate of #4203

@DonJayamanne DonJayamanne marked this as a duplicate of #4203 Feb 1, 2019
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Feb 1, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Mar 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants