Currently sqlalchemy-imageattach uses Werkzeug for two reasons:
[x] Context locals: we can simply bring it from Werkzeug as like Celery have done.
[x] 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.
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.