Kian Kasad 7038687b20 chore(python): use debugpy-adapter executable for nvim-dap-python (#6080) ...

## Description

Uses a less hacky and now officially-supported way of getting the
debugpy DAP adapter path for nvim-dap-python.

Since https://github.com/mfussenegger/nvim-dap-python/pull/184,
nvim-dap-python can start the debugpy adapter using the
`debugpy-adapter` executable. Since
[Mason](f7c1c2fde2/packages/debugpy/package.yaml (L17))
and [now debugpy itself](https://github.com/microsoft/debugpy/pull/1870)
provide this executable, there's no need to get the `python` executable
from debugpy's venv.

I've gone with just `"debugpy-adapter"` rather than
`LazyVim.get_pkg_path("debugpy", "debugpy-adapter")` so that a
system-wide installation of debugpy can also be used.

## Related Issue(s)

<!--
  If this PR fixes any issues, please link to the issue here.
  - Fixes #<issue_number>
-->

## Screenshots

<!-- Add screenshots of the changes if applicable. -->

## Checklist

- [x] I've read the
[CONTRIBUTING](https://github.com/LazyVim/LazyVim/blob/main/CONTRIBUTING.md)
guidelines.

2025-10-19 12:47:17 +02:00

..

config

chore(main): release 15.8.1 (#6641)

2025-10-18 08:34:17 +02:00

plugins

chore(python): use debugpy-adapter executable for nvim-dap-python (#6080)

2025-10-19 12:47:17 +02:00

util

fix(treesitter): better check on windows if microsoft build tools is installed

2025-10-15 19:43:44 +02:00

health.lua

feat(treesitter): add installation instructions to get a C compiler on windows

2025-10-15 08:42:05 +02:00

init.lua

…

types.lua

…