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

Python won't use 3.7 and is stuck on 2.7. #4159

Closed
mferraro23 opened this issue Jan 26, 2019 · 13 comments
Closed

Python won't use 3.7 and is stuck on 2.7. #4159

mferraro23 opened this issue Jan 26, 2019 · 13 comments

Comments

@mferraro23
Copy link

Environment data

  • VS Code version: 1.30(latest)
  • Extension version (available under the Extensions sidebar): 2018.12.1
  • OS and version: MAC OS Mojave
  • Python version (& distribution if applicable, e.g. Anaconda): 3.7 but only uses 2.7
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): na
  • Relevant/affected Python packages and their versions: 3.7 and 2.7

Expected behaviour

I want to be using python version 3.7.

Actual behaviour

Doesnt let me use python 3.7 only uses 2.7

Steps to reproduce:

Not sure you can reproduce this. I followed all the instructions online on how to make python 3.7 the right interpreter but it wont work.

Logs

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

Nothings wrong with the output i just cannot code using 3.7 it only allows for 2.7 to be used . 

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)

XXX
@ghost ghost added the triage-needed Needs assignment to the proper sub-team label Jan 26, 2019
@DonJayamanne
Copy link

Not sure you can reproduce this. I followed all the instructions online on how to make python 3.7 the right interpreter but it wont work.

Please do provide the steps.
You might have another extension installed it haven't configured something.
Do please provide the steps you have followed, or a video

Please provide the contents of your settings.json file in your workspace.

@mferraro23
Copy link
Author

mferraro23 commented Jan 27, 2019 via email

@DonJayamanne
Copy link

DonJayamanne commented Jan 27, 2019

IN the picture u can see it says using 3.7

What picture?

But when I use it I get errors

How are you using this, that's what I would like to know.
Please provide the instructions here.

Also Please provide the contents of your settings.json file in your workspace.

@mferraro23
Copy link
Author

mferraro23 commented Jan 27, 2019 via email

@DonJayamanne
Copy link

DonJayamanne commented Jan 27, 2019

Can you not see the picture I sent

There is nothing on this site! You can see it as well. Anything you upload will be visible in this page.

Once again how are you running this code?
Please provide the steps, are you using debug, run without debugging, run file in terminal, etc..

@DonJayamanne
Copy link

Do you have the code runner extension installed?

@mferraro23
Copy link
Author

mferraro23 commented Jan 27, 2019 via email

@mferraro23
Copy link
Author

mferraro23 commented Jan 27, 2019 via email

@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Jan 28, 2019
@MattMorgis
Copy link

MattMorgis commented Feb 1, 2019

I am having this issue as well. When using Select Interpreter, it sees all of my conda environments. However, when I am using the integrated terminal, even after using Python: Create Terminal, it still uses the macOS default 2.7 version.

screen shot 2019-01-31 at 9 21 25 pm

@ericsnowcurrently
Copy link
Member

@mferraro23 and @MattMorgis, is this strictly a problem with conda? Which version of conda are you using? Do you still have this problem if you use the latest release of the extension?

@ericsnowcurrently ericsnowcurrently added info-needed Issue requires more information from poster area-terminal feature-interpreter labels Feb 4, 2019
@DonJayamanne
Copy link

@MattMorgis
Please could you try making the following change and letting me know whether it works:

"terminal.integrated.env.osx": {
		"PATH": ""
}

@MattMorgis
Copy link

That seems to have fixed the issue

@ericsnowcurrently
Copy link
Member

Great!

@ghost ghost removed info-needed Issue requires more information from poster triage labels Mar 4, 2019
@ericsnowcurrently ericsnowcurrently removed their assignment Mar 4, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Apr 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants