This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients Rob Taft, rkm, terry.reedy, xtreak
Date 2020-05-30.03:01:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1590807716.58.0.753554131312.issue40805@roundup.psfhosted.org>
In-reply-to
Content
Sorry, but I believe you were misdirected*.  mock, as opposed to unittest.mock, pytest, flask, and werkzeug  are 3rd party modules.  The error report seems to be missing part of the stacktrace at both ends.  What line is your file resulted in the error?  (This time we can guess == @patch. @What called _lookup_app_object in flask?  (I have no idea.)

However, once contextlib._GeneratorContextManager calls next(self.gen), the rest of the trace is outside the stdlib.  At the end, the RuntimeError is raised by flask, not by python, because the flask _app_ctx_stack.top does not exist.  If you do not understand their error message, ask flask people.

* I assume that cjw296 *glanced* at your report, saw 'RuntimeError', and too quickly assumed 'cpython error'.  flask could have defined, for instance, FlaskRuntimeError for its error reporting.
History
Date User Action Args
2020-05-30 03:01:56terry.reedysetrecipients: + terry.reedy, xtreak, rkm, Rob Taft
2020-05-30 03:01:56terry.reedysetmessageid: <1590807716.58.0.753554131312.issue40805@roundup.psfhosted.org>
2020-05-30 03:01:56terry.reedylinkissue40805 messages
2020-05-30 03:01:56terry.reedycreate