blueprint already registered about flask-empty HOT 6 OPEN

Ugh I didn't realize this could happen, that's frustrating. How would you even "destroy the whole application object"?

from flask-empty.

Obviously with app.destroy()

No just kidding, but there is a teardown_appcontext() which "Registers a function to be called when the application context ends. These functions are typically also called when the request context is popped."

But destroying the app-context wouldn't be the solution to this anyways … so I don't know if we are overlooking something more fundamental? Maybe we can ask for help?

So funny when old GitHub issues pop up and your issue-context got destroyed and you have to recreate it again ;P glad you replied :)

from flask-empty.

Obviously with app.destroy()

No just kidding, but there is a teardown_appcontext() which "Registers a function to be called when the application context ends. These functions are typically also called when the request context is popped."

But destroying the app-context wouldn't be the solution to this anyways … so I don't know if we are overlooking something more fundamental? Maybe we can ask for help?

So funny when old GitHub issues pop up and your issue-context got destroyed and you have to recreate it again ;P glad you replied :)

This is all a bit above my head tbh. I just want to name my blueprints what I want 😂 I didn't realize anything is "persistent" when you stop and re-run the application.

from flask-empty.

from flask-empty.

Can you show a minimal example? add_blueprint_list is not called by flask-security.

from flask-empty.

I seem to be having this problem too. I was getting this error on some nested blueprints (which in my code are only explicitly registered once). I came across this and removed flask_login, and that stopped the error. I'm still not sure what is going on exactly.

from flask-empty.