Running flask in a thread with Kivy causes no requests to be printed out

Expected Behavior

Server errors or I see a traceback. I’m trying to run a little flask app as part of a kivy frontend (goal to make a multiplayer card game app). In a later endpoint I typed njwfnof to simulate an error and nothing happened when the endpoint was hit. Is this intended?

class FlaskThread(Thread):
    def __init__(self, *args, **kwargs):
        self.root = kwargs.pop('root')
        super().__init__(*args, **kwargs)

    def run(self):
        app.root = self.root
        app.run(
            host='127.0.0.1', port=8888, debug=True, use_debugger=True,
            # setting use_reloader to False because it can't be True if not run in main thread
            use_reloader=False)

Actual Behavior

Server stays up but nothing happens

Environment

• Python version: 3.6.4
• Flask version: Flask 1.0.2
• Werkzeug version: 0.14.1

[s1113950]

aHa! I found it: https://github.com/kivy/kivy/blob/master/kivy/logger.py#L324 yeah looks like kivy’s logger is blocking other loggers, since flask logs things under the flask namespace. Time to close this issue!

[RonnyPfannschmidt]

i strongly suspect that the kivy logging setup might in turn cause flask not to apply its default logging setup as logging was “set up” by kivy - but i am completely unfamiliar with kivy