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 has been archived by the owner on Oct 23, 2023. It is now read-only.
I was able to trace it to middleware.common_exception_handling witch allow reraise StopIteration . But since python 3.5 generators should return to stop iteration (https://www.python.org/dev/peps/pep-0479/#converting-the-exception-inside-next). This is than catched by contexmanager decorator and this warning is produced.
It prevents us to simply use -W error to find out problems when we update requirements of our project.
The text was updated successfully, but these errors were encountered:
Having the same error, py.test logs are flooding. We hacked out Sentry from our tests to keep cleaner test output, but I'd really like to not have a special setup for being able to see the output.
We use
raven.contrib.flask.Sentry
to handle our error on flask app on python 3.5. But it produces warningsI was able to trace it to
middleware.common_exception_handling
witch allow reraiseStopIteration
. But since python 3.5 generators should return to stop iteration (https://www.python.org/dev/peps/pep-0479/#converting-the-exception-inside-next). This is than catched bycontexmanager
decorator and this warning is produced.It prevents us to simply use -W error to find out problems when we update requirements of our project.
The text was updated successfully, but these errors were encountered: