miracle2k/webassets — Issue #82: Environment.updater doesn't work when set to False
Author: andrewwatts
Created: 2011-12-12 07:56:30+00:00
State: open

my understanding of the documentation located at [http://elsdoerfer.name/files/docs/webassets/environment.html#webassets.env.Environment.updater][1]. is that if environment.updater is set to False. then assets are not built. However when this is the case, there are numerous errors that take place.

1. bundle._build raises a BuildError if the output path doesn't exist.
2. the bundle is still attempting to build and raises the following errors in merge.py:apply_filters
* filters try to access disk and raise errors if directories do not exist or the app server user is denied permission
* filters try to run programs that are not necessarily installed on the app server, eg: sass.

I've found that setting updater to 'never' solves issue 1. But so far I have not found an easy solution to number 2, personally, i would expect that if updater is set to `False` or `never` that filters never even attempt run, so there are no disk seeks or attempts to execute programs that are not installed on the app server, eg: sass.

Is there a way to ensure filters are not run in "production" mode or if updater is set to `False` or `never`?

Thanks

[1]: http://elsdoerfer.name/files/docs/webassets/environment.html#webassets.env.Environment.updater