Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove werkzeug as a dependency #445

Open
bloodearnest opened this issue Apr 18, 2019 · 1 comment
Open

Remove werkzeug as a dependency #445

bloodearnest opened this issue Apr 18, 2019 · 1 comment

Comments

@bloodearnest
Copy link
Contributor

We used werkzeug for WSGI responses and for local thread/greenlet context, but it would be good to remove it. This would mean some simple WSGI boilerplate for endpoints, but also need a replacement for the local context.

The obvious choice for this is the new stdlib contextvars, (with pre 3.7 backport), so we should see if that would enable dropping werkzeug

@bloodearnest
Copy link
Contributor Author

I had a look at this, and while we don't use werkzeug.local any more, we do still use it for a bunch of wsgi/http stuff that's non-trivial, like content negotiation, so we'd need to implement that ourselves if we want to remove it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant