Output caching is effectively disabled in Windows about django-sass-processor

[jrief]

In the generated sourcemap file, does libsass use / or \ in paths?
If it's a normal slash /, then this problem could be solved by replacing the first line against

components = os.path.normpath(srcfilename).split('/')

Please check, since I have no Windows machine to test.

[frostbtn]

libsass generates this:

	"sources": [
		"d:/Projects/py/project/scss/static/project.scss",
		"d:/Projects/py/project/scss/_bootstrap-custom.scss", 

Ok, first line could be changed. What about that first os.path.sep on the second line. It's what makes path invalid on Windows.

Generally, what libsass generates in the source map is already ok to check with os.path.* (down the code). Is libsass generates something strange on Linux? Some relative paths? Could you give an example, should you happen to have a minute for this. I may come up with a fix, I just can't figure out what problem unknown to me is being worked around in these lines.

(libsass's source map is pretty useless with this kind of paths on Windows, as Chrome tries to open something like https://server/d:/Projects/py/project/scss/static/project.scss and this can never be correct. It's a libsass problem for sure, but nobody care, me included. However, 1.5 seconds per page request is a problem, I suppose).

[jrief]

My development environment ist MacOSX, and there libsass creates entries such as

...
"sources": [
    "../../../Users/jrief/Workspace/djangoSHOP/django-shop/example/myshop/static/myshop/css/default.scss",
    "../../../Users/jrief/Workspace/djangoSHOP/django-shop/shop/static/shop/css/_django-shop.scss",
    "../../../Users/jrief/Workspace/djangoSHOP/django-shop/shop/static/shop/css/_variables.scss",
    ...
],
...

That's btw. the reason why I have to remove the ../../.. in front of /Users/. os.path.abspath() unfortunately doesn't work here.

[frostbtn]

Oh, I see. That's make sense now. A total mess on libsass's end.
I shall take a deeper look, if the time will allow.
Let's leave this issue open for the time, maybe someone may have more input.

[jrief]

@frostbtn have you been able to find a fix on Windows?

[frostbtn]

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.