You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 20, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: docs/guides/python/debugging.mdx
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,17 +10,15 @@ updated_at: 2025-03-27
10
10
11
11
# Debugging
12
12
13
-
This guide will walk you through setting up local debugging for Nitric applications written in Python.
13
+
This guide will walk you through setting up local debugging for Nitric applications written in Python, using VSCode.
14
14
15
15
## Local Debugging with Python
16
16
17
-
Debugging serverless-style applications can be challenging due to the way functions are triggered by events. For Python, [`debugpy`](https://github.com/microsoft/debugpy) is used to connect a debugger to the service while it runs.
18
-
19
-
Nitric's local environment behaves as closely as possible to the target cloud environment. While local debugging can help uncover many issues early, unit testing and integration testing are still strongly recommended prior to deploying to production.
17
+
Debugging serverless-style applications can be challenging due to the way functions are triggered by events. For Python, we can use [`debugpy`](https://github.com/microsoft/debugpy) to connect a debugger to the service while it runs.
20
18
21
19
### 1. Modify the Python entry point
22
20
23
-
Add the following lines to the top of the service file (e.g., `main.py`). This starts a debug server that the IDE can attach to.
21
+
Add the following lines to the top of the service file (e.g., `services/api.py`). This starts a debug server that the IDE can attach to.
0 commit comments