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

imports not working can't change python intepreter #23173

Closed
edenpage11 opened this issue Apr 3, 2024 · 4 comments
Closed

imports not working can't change python intepreter #23173

edenpage11 opened this issue Apr 3, 2024 · 4 comments
Assignees
Labels
triage-needed Needs assignment to the proper sub-team

Comments

@edenpage11
Copy link

Type: Bug

When i pip installed exifread and reverse_geocoder, they say not resolved. I have my intepreter set as python3.12.2 in the bottom right corner and all the settings, but typing python --version in my terminal shows it as 3.9.13. I have uninstalled and reinstalled, closed and reopened, idk what else to do, I also can run the program if I change it to 3.9.13 in the bottom right corner and the not resolved errors go away

VS Code version: Code 1.87.2 (863d2581ecda6849923a2118d93a088b0745d9d6, 2024-03-08T15:20:17.278Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info
Item Value
CPUs 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz (8 x 2995)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
Load (avg) undefined
Memory (System) 15.85GB (5.77GB free)
Process Argv --crash-reporter-id b84be46c-f11e-428a-ac42-896d8d8b8bc8
Screen Reader no
VM 33%
Extensions (19)
Extension Author (truncated) Version
nodejs-bundle 1Yi 1.0.0
svelte-bundle 1Yi 1.0.0
svelte-intellisense ard 0.7.1
vscode-svelte-snippets fiv 0.5.0
svg joc 1.5.3
rainbow-csv mec 3.11.0
debugpy ms- 2024.2.0
isort ms- 2023.10.1
python ms- 2024.2.1
vscode-pylance ms- 2024.4.1
jupyter ms- 2024.2.0
vscode-jupyter-cell-tags ms- 0.1.8
vscode-jupyter-slideshow ms- 0.1.5
live-server ms- 0.4.13
powershell ms- 2024.0.0
vs-code-prettier-eslint rve 6.0.0
vscode-standard sta 2.1.3
svelte-vscode sve 108.3.4
vscode-surround yat 1.5.0
A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:30899288
vscaac:30438847
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
ccp2r3:30993541
dsvsc020:30976470
pythonait:31006305
7ghi1836:30988842
dsvsc021:30996838
g1icg217:30999571

@edenpage11
Copy link
Author

edenpage11 commented Apr 3, 2024

image

deleting and reopening the terminal also didn't fix it

@vscodenpa vscodenpa added the triage-needed Needs assignment to the proper sub-team label Apr 3, 2024
@benibenj benibenj assigned karthiknadig and unassigned benibenj Apr 3, 2024
@vscodenpa vscodenpa removed the triage-needed Needs assignment to the proper sub-team label Apr 3, 2024
@karthiknadig karthiknadig transferred this issue from microsoft/vscode Apr 3, 2024
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Apr 3, 2024
@karthiknadig
Copy link
Member

@edenpage11 we use whatever python you have on PATH in your terminal environment when you are using global python. You can use where python to see which python is being used.

Here are some of our recommendations based on best practices.

  1. Use virtual environment: In your case you are installing packages using pip binary directly. Just like how python can point to different python depending on how the PTH environment variable is set, pip can point to different locations. Installing packages into global environment can actually break your global python install. So, we recommend always creating virtual environment for each of the projects. You can do this using Python: Create Environment command from command palette and selecting Venv. When you use virtual environments, Python extension can make sure that python means the python in your virtual environment.
  2. Always use python -m pip install instead of pip install. Read this for more details on why: https://snarky.ca/why-you-should-use-python-m-pip/

Here is an example in my case, it really depends on what PATH env variable is doing for global environments:
image

Here is a virtual environment. With virtual environments, Python extension can "activate" it and add it to PATH in such a way that python is going to be the one in the virtual environment.
image

@github-actions github-actions bot added the info-needed Issue requires more information from poster label Apr 3, 2024
@edenpage11
Copy link
Author

edenpage11 commented Apr 3, 2024

Is there a way to make it default to the 3.12? I don't want it to run the 3.9 at all

Using the where python also didn't print any paths

@github-actions github-actions bot removed the info-needed Issue requires more information from poster label Apr 3, 2024
@karthiknadig
Copy link
Member

karthiknadig commented Apr 3, 2024

@edenpage11 You can do it two ways.

Option 1

set PATH environment variable using this UI in windows:
image

image

image

image

You will need to add the folder containing the python you want at the top:
image

NOTE: You need to add the path folder containing the python, not the path to python binary itself.

Option 2

Uninstall the python 3.9. You can find where it is installed by using python -c "import sys;print(sys.executable)"

@karthiknadig karthiknadig closed this as not planned Won't fix, can't repro, duplicate, stale Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage-needed Needs assignment to the proper sub-team
Projects
None yet
Development

No branches or pull requests

4 participants