Skip to content

Commit

Permalink
Add a readme note about profiler behavior changes after python 3.12
Browse files Browse the repository at this point in the history
  • Loading branch information
albertyw authored and 50-Course committed Jan 15, 2024
1 parent 001b5d5 commit 7bc0f26
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -150,7 +150,7 @@ Before diving into the stack trace to figure out where this request is coming fr

### Profiling

Turn on the SILKY_PYTHON_PROFILER setting to use Python's built-in cProfile profiler. Each request will be separately profiled and the profiler's output will be available on the request's Profiling page in the Silk UI.
Turn on the SILKY_PYTHON_PROFILER setting to use Python's built-in `cProfile` profiler. Each request will be separately profiled and the profiler's output will be available on the request's Profiling page in the Silk UI. Note that as of Python 3.12, `cProfile` cannot run concurrently so [django-silk under Python 3.12 and later will not profile if another profile is running](https://github.com/jazzband/django-silk/pull/692) (even its own profiler in another thread).

```python
SILKY_PYTHON_PROFILER = True
Expand Down

0 comments on commit 7bc0f26

Please sign in to comment.