The only port of LESS to python is not 1:1 compatible with standard lessc, resulting in compilation errors on our files
Due to
https://github.com/lesscpy/lesscpy/issues/54 our base/static/less/navbar.less fails to compile.
Seeing as the lesscpy project is slowly dying, implementation of new features / bugfixes might not happen.
What I am getting around to is: when developing for SIO2 we would have to keep in mind the differences between the implementations, or make changes to lesscpy ourselves.
Do we really want to do that just to have 1 dependency less?
Due to https://github.com/lesscpy/lesscpy/issues/54 our base/static/less/navbar.less fails to compile.
Seeing as the lesscpy project is slowly dying, implementation of new features / bugfixes might not happen.
What I am getting around to is: when developing for SIO2 we would have to keep in mind the differences between the implementations, or make changes to lesscpy ourselves.
Do we really want to do that just to have 1 dependency less?