• Now all data be ready for publish, We had made our blog alive now. Haha.



  • These days CCP GFW blocked all the IPs from US and when I switch my IP in google Cloud, the disk data cannot be restore again. I have to restart my blog totally, Now the website is still building…



Why does running the Flask dev server run itself twice?- Stack Overflow

Python PingBook 1 months ago (10-23) 14 0

Question

I’m using Flask for developing a website and while in development I run flask using the following file:

#!/usr/bin/env python
from datetime import datetime
from app import app
import config

if __name__ == ‘__main__’:
print ‘################### Restarting @’, datetime.utcnow(), ‘###################’
app.run(port=4004, debug=config.DEBUG, host=’0.0.0.0′)

When I start the server, or when it auto-restarts because files have been updated, it always shows the print line twice:

################### Restarting @ 2014-08-26 10:51:49.167062 ###################
################### Restarting @ 2014-08-26 10:51:49.607096 ###################

Although it is not really a problem (the rest works as expected), I simply wonder why it behaves like this? Any ideas?

Answer

The Werkzeug reloader spawns a child process so that it can restart that process each time your code changes. Werkzeug is the library that supplies Flask with the development server when you call app.run().

See the restart_with_reloader() function code; your script is run again with subprocess.call().

If you set use_reloader to False you’ll see the behaviour go away, but then you also lose the reloading functionality:

app.run(port=4004, debug=config.DEBUG, host=’0.0.0.0′, use_reloader=False)

You can disable the reloader when using the flask run command too:

FLASK_DEBUG=1 flask run –no-reload

You can look for the WERKZEUG_RUN_MAIN environment variable if you wanted to detect when you are in the reloading child process:

import os
if os.environ.get(‘WERKZEUG_RUN_MAIN’) == ‘true’:
print ‘################### Restarting @ {} ###################’.format(
datetime.utcnow())

However, if you need to set up module globals, then you should instead use the @app.before_first_request decorator on a function and have that function set up such globals. It’ll be called just once after every reload when the first request comes in:

@app.before_first_request
def before_first_request():
print ‘########### Restarted, first request @ {} ############’.format(
datetime.utcnow())

Do take into account that if you run this in a full-scale WSGI server that uses forking or new subprocesses to handle requests, that before_first_request handlers may be invoked for each new subprocess.




Copyright from PingBook Blog, If not specified, they are original. This site uses BY-NC-SAProtocol authenticated.
For reprinting, please indicate the link of the original text:Why does running the Flask dev server run itself twice?- Stack Overflow
LIKE (0)
[1725641479@qq.com]
SHARE (0)
PingBook
Author:
We create, We sharing! Tag every value data your sharing
Submit comments
Cancel comments
emoji picture bold strikethrough center italic check in

Hi,you need to provide your name and email adress!

  • Name (Required)
  • Email (Required)
  • Website