Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: Current Version
    • Fix Version/s: TAG 2014/15
    • Component/s: OIOIOI
    • Labels:
      None

      Activity

      Hide
      Olaf Tomalka added a comment -
      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?
      Show
      Olaf Tomalka added a comment - 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?
      Hide
      Szymon Acedański added a comment -
      I think we don't...

      On Tue, Nov 4, 2014, 18:45 Olaf Tomalka (JIRA) <sio2-jira@dasie.mimuw.edu.pl>
      wrote:

      > Olaf Tomalka
      > <https://jira.sio2project.mimuw.edu.pl/secure/ViewProfile.jspa?name=ritave>
      > *commented* on an issue Re: Use Python version of lessc
      > <https://jira.sio2project.mimuw.edu.pl/browse/SIO-1577> 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? [image:
      > Add Comment]
      > <https://jira.sio2project.mimuw.edu.pl/browse/SIO-1577#add-comment> Add
      > Comment
      > <https://jira.sio2project.mimuw.edu.pl/browse/SIO-1577#add-comment>
      >
      > The SIO2 project <https://jira.sio2project.mimuw.edu.pl/browse/SIO> / [image:
      > Improvement] <https://jira.sio2project.mimuw.edu.pl/browse/SIO-1577>
      > SIO-1577 <https://jira.sio2project.mimuw.edu.pl/browse/SIO-1577> Use
      > Python version of lessc
      > <https://jira.sio2project.mimuw.edu.pl/browse/SIO-1577>
      > This message was sent by Atlassian JIRA (v6.1#6144-sha1:2e50328) [image:
      > Atlassian logo]
      >
      Show
      Szymon Acedański added a comment - I think we don't... On Tue, Nov 4, 2014, 18:45 Olaf Tomalka (JIRA) < sio2-jira@dasie.mimuw.edu.pl > wrote: > Olaf Tomalka > < https://jira.sio2project.mimuw.edu.pl/secure/ViewProfile.jspa?name=ritave > > *commented* on an issue Re: Use Python version of lessc > < https://jira.sio2project.mimuw.edu.pl/browse/SIO-1577 > 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? [image: > Add Comment] > < https://jira.sio2project.mimuw.edu.pl/browse/SIO-1577#add-comment > Add > Comment > < https://jira.sio2project.mimuw.edu.pl/browse/SIO-1577#add-comment > > > The SIO2 project < https://jira.sio2project.mimuw.edu.pl/browse/SIO > / [image: > Improvement] < https://jira.sio2project.mimuw.edu.pl/browse/SIO-1577 > > SIO-1577 < https://jira.sio2project.mimuw.edu.pl/browse/SIO-1577 > Use > Python version of lessc > < https://jira.sio2project.mimuw.edu.pl/browse/SIO-1577 > > This message was sent by Atlassian JIRA (v6.1#6144-sha1:2e50328) [image: > Atlassian logo] >

        People

        • Assignee:
          Szymon Acedański
          Reporter:
          Szymon Acedański
          TAG Developer:
          Olaf Tomalka
        • Votes:
          0 Vote for this issue
          Watchers:
          2 Start watching this issue

          Dates

          • Due:
            Created:
            Updated:
            Resolved: