Duplicating Startup Jobs about flask-apscheduler HOT 6 CLOSED

I use app.run(use_reloader=False) to prevent flask to create two instances of flask_apscheduler.APScheduler. If I omit use_reload=False jobs are also fired twice for me.
See: http://stackoverflow.com/a/15491587

from flask-apscheduler.

Hi @rj919

I tried to run your code and it runs the job only once on startup, I added the same job through the API it will execute another time, It seems to work as expected.

Maybe I didn't understand well your question, you could rephrase it?

from flask-apscheduler.

After some further investigation, it appears the phenomena is associated with calling the startup file a second time. Whenever a function references the same file that houses the app object for the first time, it re-initializes the startup jobs. So, since the startup job launch:app.logger.debug was referencing it's own file, it was duplicated along with all the other jobs added to the scheduler by commands in launch.py

This may be a feature of how Flask_APScheduler or APScheduler itself retrieves callables. But, it is definitely occurring both in my windows environment and my alpine linux virtualbox.

For most things, I think I can work around this problem by putting the callables in other files, but it may be tricky trying to incorporate the app object into other callables (for say logging) since any reference to the file with the scheduler seems to invoke it a second time.

Thoughts?

from flask-apscheduler.

Now I see the issue, that isn't going to work.

You have to restructure your project, you have to instantiate Flask and APScheduler in one file and initialize them in another file.

For example:

init.py

app = Flask()
scheduler = APScheduler()

jobs.py

from . import app

def job1():
    app.logger.debug('lalala')

lunch.py

from . import app, scheduler

if __name__ == '__main__':
    scheduler.init_app(app)
    app.run()

from flask-apscheduler.

In his example above, even using use_reloader=False it will still happen.

Anyway, it is not a good practice to put everything into one single file.

from flask-apscheduler.

Separating the init from the launch did the trick. And... you make a good point about putting all the configs into an init file being better practice (especially for all these self-referential callables). Thanks!

from flask-apscheduler.