diff options
| author | Matt Robenolt <matt@ydekproductions.com> | 2015-08-01 11:59:43 -0700 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2015-08-01 19:10:41 -0400 |
| commit | 514fee82a18e2b8fed0b6e31a95bd7a1a94980ab (patch) | |
| tree | e9094aa3300941e5e474709f298ba99d2d5795d2 /docs/howto/deployment/wsgi | |
| parent | 3bdaaf6777804d33ee46cdb5a889b8cc544a91f1 (diff) | |
Removed obsolete note about sentry/raven not handling WSGI properly.
2.0.7 was released in 2012.
Diffstat (limited to 'docs/howto/deployment/wsgi')
| -rw-r--r-- | docs/howto/deployment/wsgi/index.txt | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/docs/howto/deployment/wsgi/index.txt b/docs/howto/deployment/wsgi/index.txt index 105825b7b4..27243e248c 100644 --- a/docs/howto/deployment/wsgi/index.txt +++ b/docs/howto/deployment/wsgi/index.txt @@ -85,7 +85,6 @@ to combine a Django application with a WSGI application of another framework. .. note:: Some third-party WSGI middleware do not call ``close`` on the response - object after handling a request — most notably Sentry's error reporting - middleware up to version 2.0.7. In those cases the + object after handling a request. In those cases the :data:`~django.core.signals.request_finished` signal isn't sent. This can result in idle connections to database and memcache servers. |