Skip to content

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

Closed

Description

@allisonChilton

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

Activity

  1. added
    triage-neededNeeds assignment to the proper sub-team
    bugIssue identified by VS Code Team member as probable bug
    on Oct 9, 2019
  2. kimadeline commented on Oct 9, 2019

    @kimadeline

    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.

  3. ghost removed
    triage-neededNeeds assignment to the proper sub-team
    on Oct 9, 2019
  4. karthiknadig commented on Oct 10, 2019

    @karthiknadig
    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/

  5. beaukinstler commented on Oct 15, 2019

    @beaukinstler

    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

  6. locked as resolved and limited conversation to collaborators on Oct 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

area-debuggingbugIssue identified by VS Code Team member as probable bugregressionBug didn't exist in a previous release

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions