Open Slach opened 9 years ago
The comment you linked to shouldn't apply to your case, since you do not configure the sass filter as an "output filter".
I don't see anything obvious wrong.
Look here: https://github.com/miracle2k/webassets/blob/master/src/webassets/filter/sass.py#L163
At this point the working directory should be set to src/assets/scss/
. I would then expect sass to find the include file in the same directory as the theme.scss
file itself. Maybe by calling the command being executed at this point manually, you can figure out why not.
After rollback to old version 3.4.13 of sass , everything work fine... see https://github.com/sass/sass/issues/1745
i have flask application with buildout in src folder
./bin/pip show flask | grep Version
Version: 0.10.1
./bin/pip show flask-assets | grep Version
Version: 0.10
src/setup.py have following strings
src/spf/manage.py
src/spf/env/dev.py
src/spf/init.py
src/spf/assets.py
src/assets/scss/theme.scss
src/assets/scss/_btn-o.scss exists and have 0777 access right
but when i run ./bin/spf_dev assets -v build
i have error
i have read https://github.com/miracle2k/webassets/blob/master/src/webassets/filter/sass.py#L36
but i don't understand why sass don't use src/assets for resolve relative path in @import directive from stdin?
self.append_path('src/assets')