Cleaned up the debugpy contrib metadata a little more

This commit is contained in:
Griatch 2025-05-25 11:09:51 +02:00
parent 3ea57fd901
commit bb54ed75f7
3 changed files with 13 additions and 4 deletions

View file

@ -17,6 +17,7 @@ This upgrade requires running `evennia migrate` on your existing database
- [Feat][pull3756]: Updated German translation (JohnFi) - [Feat][pull3756]: Updated German translation (JohnFi)
- [Feat][pull3757]: Add more i18n strings to `DefaultObject` for easier translation (JohnFi) - [Feat][pull3757]: Add more i18n strings to `DefaultObject` for easier translation (JohnFi)
- [Feat][pull3783]: Support users of `ruff` linter by adding compatible config in `pyproject.toml` (jaborsh) - [Feat][pull3783]: Support users of `ruff` linter by adding compatible config in `pyproject.toml` (jaborsh)
- [Feat][pull3777]: New contrib `debugpy` for debugging Evennia with in VSCode with `debugpy` adapter (electroglyph)
- [Fix][pull3677]: Make sure that `DefaultAccount.create` normalizes to empty - [Fix][pull3677]: Make sure that `DefaultAccount.create` normalizes to empty
strings instead of `None` if no name is provided, also enforce string type (InspectorCaracal) strings instead of `None` if no name is provided, also enforce string type (InspectorCaracal)
- [Fix][pull3682]: Allow in-game help searching for commands natively starting - [Fix][pull3682]: Allow in-game help searching for commands natively starting
@ -88,6 +89,7 @@ This upgrade requires running `evennia migrate` on your existing database
[pull3757]: https://github.com/evennia/evennia/pull/3757 [pull3757]: https://github.com/evennia/evennia/pull/3757
[pull3768]: https://github.com/evennia/evennia/pull/3768 [pull3768]: https://github.com/evennia/evennia/pull/3768
[pull3783]: https://github.com/evennia/evennia/pull/3783 [pull3783]: https://github.com/evennia/evennia/pull/3783
[pull3777]: https://github.com/evennia/evennia/pull/3777
[issue3688]: https://github.com/evennia/evennia/issues/3688 [issue3688]: https://github.com/evennia/evennia/issues/3688
[issue3687]: https://github.com/evennia/evennia/issues/3687 [issue3687]: https://github.com/evennia/evennia/issues/3687
[issue3788]: https://github.com/evennia/evennia/issues/3788 [issue3788]: https://github.com/evennia/evennia/issues/3788

View file

@ -1,4 +1,4 @@
# debugpy # DebugPy VSCode debugger integration
Contribution by electroglyph, 2025 Contribution by electroglyph, 2025
@ -24,12 +24,13 @@ From the venv where you installed Evennia run:
In your Evennia mygame folder, open up `/commands/default_cmdsets.py` In your Evennia mygame folder, open up `/commands/default_cmdsets.py`
add `from evennia.contrib.utils.debugpy.cmd import CmdDebugPy` somewhere near the top. add `from evennia.contrib.utils.debugpy import CmdDebugPy` somewhere near the top.
in CharacterCmdSet.at_cmdset_creation add this under `super().at_cmdset_creation()`: in `CharacterCmdSet.at_cmdset_creation` add this under `super().at_cmdset_creation()`:
`self.add(CmdDebugPy)` `self.add(CmdDebugPy)`
### Add "remote attach" option to VS Code debugger ### Add "remote attach" option to VS Code debugger
Start VS Code and open your launch.json like this: Start VS Code and open your launch.json like this:

View file

@ -0,0 +1,6 @@
"""
VSCode Evennia debugger adapter - electroglyph, 2025
"""
from .cmd import CmdDebugPy # noqa