Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

nushell doesn't work with debugpy (python debugger)

Aperta
#1,853 7 commenti 8 reazioni 2 assegnatari Vedi su GitHub

@anthonykim1 ci sta già lavorando.

Dal 4/3/2025.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

bug needs repro

Does this issue occur when all extensions are disabled?: Well. I need Python extension to make it run.

The issue description (system details at the bottom):

Seems like even though it says that nushell is supported now in VSCode in August release (here is the announce), it still can't be used as one of Internal Terminals when you try to debug python script. It gets call with a sequence not compatible with nushell syntax like this one.

a) Pixi's environemnt python bad command example:

cmd /C "c:\dev\data_processing\.pixi\envs\default\python.exe c:\Users\360ci\.vscode\extensions\ms-python.debugpy-2024.12.0-win32-x64\bundled\libs\debugpy\adapter/../..\debugpy\launcher 54917 -- c:\dev\data_processing\test.py "

b) Conda's environment python bad command example:

c: && cd c:\dev\sfms && cmd /C "c:\programs\miniconda\envs\data_proc\python.exe c:\Users\360ci\.vscode\extensions\ms-python.debugpy-2024.12.0-win32-x64\bundled\libs\debugpy\adapter/../..\debugpy\launcher 50270 -- c:\dev\sfms\test.py "

Screenshot:
Image

It DOES work when you just try to run the script because comparing with debug sequence it doesn't have nushell incompatible command in this case. Because when you try to just run it correctly forms the line. Here is example of the command which works

Conda's good and compatible command when you just run without debugger:

C:/programs/miniconda/envs/data_proc/python.exe c:/dev/sfms/test.py

@anthonykim1, I saw you latest work on having nushell and julia integrated into VSCode, but I think there is a small chance that I misunderstand how it is expected to work?

The isssue is also discussed here in nushell repo:
https://github.com/nushell/nushell/issues/14022
Here is also one of my comments on this problem with some advices from one of the authors:
https://github.com/nushell/nushell/issues/2775#issuecomment-2412005812

@IanManske point outed here that the problem in these lines where nushell is not supported:
https://github.com/microsoft/vscode/blob/321e1e5b8a0af43a0ee7549713f606936a1ac9ac/src/vs/workbench/contrib/debug/node/terminals.ts#L81

Details

  • VS Code Version: 1.94.2
  • OS Version: Win10: 10.0.19045 Build 19045
  • Plugins: Python plugin, but no nushell plugin (is it needed?)

Steps to Reproduce:

  1. Install nushell in your system.
  2. Go to Settings, to to Terminal > Integrated > Default Profile: Windows, set up "path" to installed nushell
  3. Have a small python program like print("Hello nu in vscode")
  4. Click on the "Run" arrow, selecting "Python Debugger: Debug Python File"
  5. Get error message caused by ill-formed command Error: × Invalid literal complaining (see the above the full command it calls) about "" or "&&" symbols in the string.
Lingua principale
Python
Stelle
2.5k
Fork
202
Merge medio
5g 1h
PR unite (30g)
1

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/debugpy

Tutte le issue di microsoft/debugpy

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.