Skip to content

Error when opening Python interactive window #5929

Closed

Description

@syagev

Environment data

  • VS Code version: 1.35.0
  • Extension version: 2019.5.18678
  • OS and version: Windows_NT x64 10.0.17763
  • Python version: CPython 3.5.4
  • Type of virtual environment used: pipenv
  • Relevant/affected Python packages and their versions: N/A
  • Language Server: Jedi

Expected behaviour

Python Interactive window should open

Actual behaviour

An error is received:

Activating Python 3.5.4 64-bit to run Jupyter failed with Error: Command failed: & C:/Users/styagev/.virtualenvs/OfflineSystem-7MBx2YtQ/Scripts/activate.ps1 && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python C:/Users/styagev/.vscode/extensions/ms-python.python-2019.5.18678/pythonFiles/printEnvVariables.py & was unexpected at this time. .

Steps to reproduce:

Open a Python Interactive window with either "local jupyter server" or remote jupyter server URI

This was working fine before latest update (not sure if it's 2019.5.18426 or 2019.5.18678)

Logs

Output for Python in the Output panel: Nothing relevant

Output from Console under the Developer Tools panel: console.log

Activity

  1. ghost added
    triage-neededNeeds assignment to the proper sub-team
    on Jun 6, 2019
  2. syagev commented on Jun 6, 2019

    @syagev
    Author

    I saw in #5916 and #5743 that the settings.json might be relevant:

    User:

    {
        "workbench.sideBar.location": "right",
        "editor.minimap.enabled": false,
        "files.autoSave": "off",
        "editor.fontSize": 11,
        "terminal.integrated.fontSize": 12,
        "editor.rulers": [
            110
        ],
        "git.enableSmartCommit": true,
        "git.autofetch": true,
        "workbench.colorTheme": "Visual Studio Dark",
        "gitlens.advanced.messages": {
            "suppressShowKeyBindingsNotice": true
        },
        "ai.homepage.openOnStartup": false,
        "window.zoomLevel": 0,
        "diffEditor.renderSideBySide": true,
        "python.dataScience.changeDirOnImportExport": false,
        "python.dataScience.sendSelectionToInteractiveWindow": true,
        "files.trimTrailingWhitespace": true,
        "[markdown]": {
            "files.trimTrailingWhitespace": false
        },
    }
    

    Workspace:

    {
        "python.pythonPath": "C:\\Users\\styagev\\.virtualenvs\\OfflineSystem-7MBx2YtQ\\Scripts\\python.exe"
    }
    

    Project:

    {
        "python.pythonPath": "C:\\Users\\styagev\\.virtualenvs\\OfflineSystem-7MBx2YtQ\\Scripts\\python.exe",
        "python.dataScience.jupyterServerURI": "local",
        "python.testing.pyTestPath": "C:\\Users\\styagev\\.virtualenvs\\OfflineSystem-7MBx2YtQ\\Scripts\\pytest",
        "python.linting.pylintEnabled": true,
        "python.testing.unittestEnabled": false,
        "python.testing.nosetestsEnabled": false,
        "python.testing.pyTestEnabled": true,
        "python.testing.pyTestArgs": [
            "-s",
            "-o",
            "python_files=*_pytest.py"
        ],
        "python.testing.cwd": "${workspaceFolder}"
    }
    
  3. ibakirov commented on Jun 6, 2019

    @ibakirov

    Check update for VS Code Python extension, latest update 2019.5.18678 (5 June 2019) resolves issue.

  4. syagev commented on Jun 6, 2019

    @syagev
    Author

    Already running 2019.5.18678. Still persists.

  5. strake7 commented on Jun 6, 2019

    @strake7

    Experiencing the same on the latest version, 2019.5.18678, as well. Windows 10, Python 3.6.8. Downgraded back to 2019.517517.

  6. ghost added
    triage-neededNeeds assignment to the proper sub-team
    on Jun 6, 2019
  7. luabud commented on Jun 6, 2019

    @luabud
    Member

    This seems to be related to the Python version used. It's working for > 3.7

  8. added
    bugIssue identified by VS Code Team member as probable bug
    and removed
    triage-neededNeeds assignment to the proper sub-team
    on Jun 6, 2019
  9. ghost added
    triage-neededNeeds assignment to the proper sub-team
    on Jun 6, 2019
  10. ghost removed
    triage-neededNeeds assignment to the proper sub-team
    on Jun 6, 2019
  11. locked as resolved and limited conversation to collaborators on Jun 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugIssue 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