A Bower-centric static file server for WSGI
BowerStatic is a WSGI-based framework that you can integrate with your WSGI-using web application or framework to help it serve static resources.
content_typeof response to be None, e.g. for HTTP-401.
Added references to Morepath and Pyramid extensions that integrate BowerStatic.
Don’t try to pick up any directories that start with a period (.) as bower packages.
Added an example on how to integrate BowerStatic with a Flask application.
Fixed documentation describing WebOb integration to new reality as of 0.7.
Ability to support custom renderers:
Breaking change: renderers will receive the resource argument instead of the url. Renderers can be used to render resources inline.
The publisher and injector have been refactored into PublisherTween and a Publisher, and an InjectorTween and an Injector. The Tween versions are the ones intended for use by web frameworks that already use WebOb (such as Morepath and Pyramid) as an alternative to using WSGI-based integration.
The WSGI-based integration has remained unchanged; you can still use bower.wrap (or bower.injector and bower.publisher).
On some platforms and filesystems (such as Linux ext3, Mac OS X) os.path.getmtime() returns timestamps with the granularity of seconds instead of subseconds such as Linux ext4. We go for second granularity now by default for autoversioning as this should be good enough during development.
The test for autoversioning was assuming sub-second granularity and this test failed. This test is now skipped on Mac OS X. What didn’t help was weird code in BowerStatic that cut off the last bit of the microsecond isoformat – this was removed.
This fixes bug #20. (Thanks to Michael Howitz for the bug report)
Display a nicer error messages when a component depends on another one that doesn’t exist. Thanks for Michael Howitz for the improvement.
Internal toposort module was not imported relative to package, which could lead to errors in some circumstances. Thanks TylorS for reporting! Fixes issue #24.