Releases: getsentry/sentry-python
Releases · getsentry/sentry-python
0.6.6
- Un-break API of internal
Auth
object that we use in Sentry itself.
0.6.5
- Capture WSGI request data eagerly to save memory and avoid issues with uWSGI.
0.6.4
- Fix bug that would lead to an
AssertionError: stack must have at least one layer
, at least in testsuites for Flask apps.
0.6.3
- New integration for Tornado
- Fix request data in Django, Flask and other WSGI frameworks leaking between events.
- Fix infinite recursion when sending more events in
before_send
.
0.6.2
- Fix crash in AWS Lambda integration when using Zappa. This only silences the error, the underlying bug is still in Zappa.
0.6.1
- New integration for aiohttp-server.
- Fix crash when reading hostname in broken WSGI environments.
0.6.0
- Fix bug where a 429 without Retry-After would not be honored.
- Fix bug where proxy setting would not fall back to
http_proxy
for HTTPs traffic.
- A WSGI middleware is now available for catching errors and adding context about the current request to them.
- Using
logging.debug("test", exc_info=True)
will now attach the current stacktrace if no sys.exc_info
is available.
- The Python 3.7 runtime for AWS Lambda is now supported.
- Fix a bug that would drop an event or parts of it when it contained bytes that were not UTF-8 encoded.
- Logging an exception will no longer add the exception as breadcrumb to the exception's own event.
0.5.5
- New client option
ca_certs
.
- Fix crash with Django and psycopg2.
0.5.4
- Fix deprecation warning in relation to the
collections
stdlib module.
- Fix bug that would crash Django and Flask when streaming responses are failing halfway through.
0.5.3
- Fix bug where using
push_scope
with a callback would not pop the scope.
- Fix crash when initializing the SDK in
push_scope
.
- Fix bug where IP addresses were sent when
send_default_pii=False
.