GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
I have noticed that flask-rq does not use context-locals to save the redis connection, which means that everytime one request comes in, we are having a new connection.
What I need here is one connection manager so I do not have to handle connections myself.
Any reasons? So flask-rq is just a config manager? I do not see anything else meaningful here.
Indeed. This extension is not meaningful at all. I was about to submit a pull request that removes the custom connection behavior, but then realized that with that removed, there's virtually no code left.
@fengsp @malthe I agree with you that using an app context would make sense. I plan to get some work done on this the coming days/weeks. Out of curiosity: are you using flask-script?