Skip to content
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

requirements didn't get automatically downloaded by extension in marketplace #7836

Closed
allisonChilton opened this issue Oct 9, 2019 · 3 comments
Assignees
Labels
area-debugging bug Issue identified by VS Code Team member as probable bug regression Bug didn't exist in a previous release

Comments

@allisonChilton
Copy link

allisonChilton commented Oct 9, 2019

Python debugger wouldn't start even after several reinstalls and reboots. I finally traced the problem back to this line:

C:\Python37\python.exe c:\Users\allis\.vscode\extensions\ms-python.python-2019.10.41019\pythonFiles\ptvsd_folder_name.py Traceback (most recent call last): File "c:\Users\allis\.vscode\extensions\ms-python.python-2019.10.41019\pythonFiles\ptvsd_folder_name.py", line 53, in <module> ptvsd_folder_name() File "c:\Users\allis\.vscode\extensions\ms-python.python-2019.10.41019\pythonFiles\ptvsd_folder_name.py", line 22, in ptvsd_folder_name with open(REQUIREMENTS, "r", encoding="utf-8") as reqsfile: FileNotFoundError: [Errno 2] No such file or directory: 'c:\\Users\\allis\\.vscode\\extensions\\ms-python.python-2019.10.41019\\requirements.txt'

Manually adding the requirements.txt from the github repo fixed the issue

@allisonChilton allisonChilton added triage-needed Needs assignment to the proper sub-team bug Issue identified by VS Code Team member as probable bug labels Oct 9, 2019
@kimadeline
Copy link

Hi @allisonChilton 👋 Thank you for reporting this issue, investigating it and adding the workaround! requirements.txt is indeed not shipped in the extension package, so we'll have to add a fallback.

@kimadeline kimadeline added area-debugging needs PR regression Bug didn't exist in a previous release labels Oct 9, 2019
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Oct 9, 2019
@kimadeline kimadeline added this to the 2019 - October Sprint 1 milestone Oct 9, 2019
@kimadeline kimadeline self-assigned this Oct 9, 2019
@karthiknadig
Copy link
Member

For anyone looking, the workaround is to add requirements.txt file with this content:

jedi==0.15.1
parso==0.5.1
isort==4.3.21
ptvsd==5.0.0a5
pyparsing==2.4.0
six==1.12.0
packaging==19.2

to this location on windows:
%USERPROFILE%/.vscode\extensions\ms-python.python-2019.10.41019\

or this location on Linux/Mac:
$HOME/.vscode/extensions/ms-python.python-2019.10.41019/

@beaukinstler
Copy link

beaukinstler commented Oct 15, 2019

For anyone looking, the workaround is to add requirements.txt file with this content:

jedi==0.15.1
parso==0.5.1
isort==4.3.21
ptvsd==5.0.0a5
pyparsing==2.4.0
six==1.12.0
packaging==19.2

to this location on windows:
%USERPROFILE%/.vscode\extensions\ms-python.python-2019.10.41019\

or this location on Linux/Mac:
$HOME/.vscode/extensions/ms-python.python-2019.10.41019/

Here's a link to the file in the repo, just to add another source of reference.
requirements.txt

@ghost ghost removed the needs PR label Oct 21, 2019
@ericsnowcurrently ericsnowcurrently removed their assignment Oct 21, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-debugging bug Issue identified by VS Code Team member as probable bug regression Bug didn't exist in a previous release
Projects
None yet
Development

No branches or pull requests

5 participants