Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a readme note about profiler behavior changes after python 3.12 #698

Merged
merged 1 commit into from
Jan 15, 2024

Conversation

albertyw
Copy link
Member

Based on the comment from #692

Copy link

codecov bot commented Jan 15, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (6e31aec) 86.67% compared to head (694198f) 86.67%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #698   +/-   ##
=======================================
  Coverage   86.67%   86.67%           
=======================================
  Files          52       52           
  Lines        2117     2117           
=======================================
  Hits         1835     1835           
  Misses        282      282           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@@ -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).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for this MR. I was about to make a patch update prior to this. Good work @albertyw

This would provide detailed context into how the profiler work on different versions on Python, giving the developer a much better context to work with.

@50-Course 50-Course merged commit 7bc0f26 into jazzband:master Jan 15, 2024
19 checks passed
@albertyw albertyw deleted the concurrent-profiler-readme branch January 16, 2024 05:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants