Skip to content

vscode keeps prompt “python quit unexpectly” #4701

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.

Sign up for GitHub

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

Jump to bottom
Closed
iXingo opened this issue Mar 10, 2019 · 3 comments
Closed

vscode keeps prompt “python quit unexpectly” #4701

iXingo opened this issue Mar 10, 2019 · 3 comments
Labels
area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. bug Issue identified by VS Code Team member as probable bug

Comments

@iXingo
Copy link

iXingo commented Mar 10, 2019 •
edited
Loading

Environment data

  • VS Code version: 1.32.1
  • Extension version (available under the Extensions sidebar): python 2019.2.5558
  • OS and version: macOS X Mojave version 10.14.3
  • Python version (& distribution if applicable, e.g. Anaconda): python3.7.2 (installed by Homebrew)
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): integrated terminal
  • Relevant/affected Python packages and their versions: removed all the python extension but the python 2019.2.5558

Expected behaviour

normal

Actual behaviour

keeps prompt me "python quit unecpectly"

Steps to reproduce:

  1. install python3 using home-brew (python3.7.2)
  2. open a python3 file (.py)
    ##actually I can get expected result using debug, but the prompt still keeps remind me, when I switch to Jedi, vscode can work fine##

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

nothing

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)

Nothing

image
@ghost ghost added the triage-needed Needs assignment to the proper sub-team label Mar 10, 2019
@DonJayamanne DonJayamanne self-assigned this Mar 11, 2019
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Mar 11, 2019
@ghost
Copy link

ghost commented Mar 11, 2019 •
edited by ghost
Loading

I'm experiencing what it appears to be the same thing, here's my report: https://pastebin.com/t1HM4Z54

@iXingo
Copy link
Author

iXingo commented Mar 12, 2019

I'm experiencing what it appears to be the same thing, here's my report: https://pastebin.com/t1HM4Z54

Can not open your link...

@DonJayamanne DonJayamanne mentioned this issue Mar 15, 2019
Closed
@DonJayamanne DonJayamanne added bug Issue identified by VS Code Team member as probable bug area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. upstream-language server and removed triage labels Mar 15, 2019
@DonJayamanne DonJayamanne removed their assignment Mar 15, 2019
@luabud
Copy link
Member

luabud commented Sep 11, 2019

Closing in favour of microsoft/python-language-server#740

@luabud luabud closed this as completed Sep 11, 2019
@ghost ghost removed the needs upstream fix label Sep 11, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Sep 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@DonJayamanne @iXingo @luabud