You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently sqlalchemy-imageattach uses Werkzeug for two reasons:
Context locals: we can simply bring it from Werkzeug as like Celery have done.
WSGI app that serves static files: it’s only a small part of Werkzeug, so we can independently implement it again from scratch.
Werkzeug is a foundation of web frameworks, and there are similar ones for the same purpose e.g. WebOb. Users of web frameworks based on other foundations (for example, Pyramid is based on WebOb instead of Werkzeug) might get inconvenient by Werkzeug dependency.
The text was updated successfully, but these errors were encountered:
Currently sqlalchemy-imageattach uses Werkzeug for two reasons:
Werkzeug is a foundation of web frameworks, and there are similar ones for the same purpose e.g. WebOb. Users of web frameworks based on other foundations (for example, Pyramid is based on WebOb instead of Werkzeug) might get inconvenient by Werkzeug dependency.
The text was updated successfully, but these errors were encountered: