-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Output caching is effectively disabled in Windows #64
Comments
In the generated sourcemap file, does
Please check, since I have no Windows machine to test. |
Ok, first line could be changed. What about that first Generally, what ( |
My development environment ist MacOSX, and there
That's btw. the reason why I have to remove the |
Oh, I see. That's make sense now. A total mess on |
@frostbtn have you been able to find a fix on Windows? |
I found no easy and safe way to fix it, unfortunately. I don't think I will have more input on this issue in the nearest future. |
sass_processor.processor.SassProcessor.is_latest has this code:
And this
os.path.sep
inside the join makes a priori invalid path in Windows (like/d:/path/path
), soos.path.isfile
what follows always returnsFalse
, forcing full compilation on every page request (whenSASS_PROCESSOR_ENABLED
isTrue
, i.e. in development).I can't seem to track down why this code is here. Does
libsass
generate some strange paths in their map file?Removing these lines makes everything work as expected... in Windows. I have no easy way to test it on *nix, hence the question.
The text was updated successfully, but these errors were encountered: