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 3.11 environments truncated to 3.1 #23670

Closed
gojandrooo opened this issue Jun 12, 2024 · 8 comments
Closed

python 3.11 environments truncated to 3.1 #23670

gojandrooo opened this issue Jun 12, 2024 · 8 comments
Assignees
Labels
triage-needed Needs assignment to the proper sub-team

Comments

@gojandrooo
Copy link

Type: Bug

I updated to latest VS code release on Mac and my python 3.11 environments are not working, they are displaying as python 3.1, seemingly some truncation ocurring

VS Code version: Code 1.90.0 (Universal) (89de5a8d4d6205e5b11647eb6a74844ca23d2573, 2024-06-04T19:34:44.157Z)
OS version: Darwin arm64 23.5.0
Modes:

System Info
Item Value
CPUs Apple M1 Pro (10 x 2400)
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
webgl: enabled
webgl2: enabled
webgpu: enabled
Load (avg) 2, 2, 2
Memory (System) 16.00GB (0.14GB free)
Process Argv --crash-reporter-id 62fdaa20-6999-4a4f-93a8-7397e0f3e41a
Screen Reader no
VM 0%
Extensions (19)
Extension Author (truncated) Version
copilot Git 1.201.0
copilot-chat Git 0.16.1
vscode-azureresourcegroups ms- 0.9.1
vscode-docker ms- 1.29.1
vscode-kubernetes-tools ms- 1.3.16
debugpy ms- 2024.6.0
python ms- 2024.8.0
vscode-pylance ms- 2024.6.1
jupyter ms- 2024.5.0
jupyter-hub ms- 2023.10.1003012305
jupyter-keymap ms- 1.1.2
jupyter-renderers ms- 1.0.18
vscode-ai ms- 0.48.0
vscode-ai-remote ms- 0.48.0
vscode-jupyter-cell-tags ms- 0.1.9
vscode-jupyter-slideshow ms- 0.1.6
remote-containers ms- 0.369.0
azure-account ms- 0.12.0
vscode-yaml red 1.15.0
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
vscaat:30438848
c4g48928:30535728
azure-dev_surveyonecf:30548226
vscrpc:30673769
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
jchc7451:31067544
chatpanelc:31048052
dsvsc021:30996838
bdiig495:31013172
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
pythonprt:31056678
dwnewjupytercf:31046870
2f103344:31071589
26j00206:31048877

@vscodenpa vscodenpa added the triage-needed Needs assignment to the proper sub-team label Jun 12, 2024
@vscodenpa vscodenpa removed the triage-needed Needs assignment to the proper sub-team label Jun 13, 2024
@SantiagoMorandi
Copy link

Facing the same issue since yesterday on most of my python 3.11 envs on VS code (1.90.1) on Ubuntu

@DaanVanHauwermeiren
Copy link

I am facing a similar issue.

For reproducibility, an example of my environment file:

name: project-XYZ
channels:
  - defaults
  - conda-forge
dependencies:
  - python==3.11
  - pip
  # - ...

installing a new environment via

conda create -f environment.yml

This will make a correct environment with the correct python env.
But VSCode will not recognize as 3.11 but as 3.1.

A workaround is to first setup the conda environment:

conda create -n project-XYZ python=3.11

Then update with environment file:

conda env update --file environment.yml --prune

The environment is now correctly recognized by VSCode.

@adammj
Copy link

adammj commented Jun 19, 2024

Same for 3.12.3 displayed as 3.1.undefined. I'm also using conda.

@DonJayamanne
Copy link

DonJayamanne commented Jun 24, 2024

@gojandrooo @SantiagoMorandi @DaanVanHauwermeiren @adammj
I'm sorry for not getting back to you on this, we did identify an issue in the area of detecting the version and it was resolved in a subsequent release.
See here #23580 & here microsoft/vscode-jupyter#15754

Please can you update to the latest version of the Python extension and verify whether this has been resolved.

@DonJayamanne DonJayamanne transferred this issue from microsoft/vscode Jun 24, 2024
@DonJayamanne DonJayamanne added the info-needed Issue requires more information from poster label Jun 24, 2024
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Jun 24, 2024
@karthiknadig
Copy link
Member

Duplicate of #23649

Please try the pre-release, which has a potential fix for this.

@karthiknadig karthiknadig closed this as not planned Won't fix, can't repro, duplicate, stale Jun 24, 2024
@DaanVanHauwermeiren
Copy link

@DonJayamanne
I did an update of VSCode + all the relevant extensions to the latest version. Seems to work now.

@gojandrooo
Copy link
Author

@gojandrooo @SantiagoMorandi @DaanVanHauwermeiren @adammj I'm sorry for not getting back to you on this, we did identify an issue in the area of detecting the version and it was resolved in a subsequent release. See here #23580 & here microsoft/vscode-jupyter#15754

Please can you update to the latest version of the Python extension and verify whether this has been resolved.

updated Python extension to v2024.9.11761016 (pre-release) and conda environments >= 3.10 now working properly. Thank you!

@github-actions github-actions bot removed the info-needed Issue requires more information from poster label Jun 24, 2024
@SantiagoMorandi
Copy link

Just updated Python extension to the pre-release version and the issue is resolved now.

Thank you!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
triage-needed Needs assignment to the proper sub-team
Projects
None yet
Development

No branches or pull requests

8 participants