Issue #67 resolved

Ordering of resources when multiple libraries involved is not robust

Alberto Valverde González
created an issue

The ordering algorithm of resources implemented in fanstatic.core.sort_resources does not handle well cases when resources of different types from different libraries depend on each other. The following test demonstrates it (can be pasted into test_core.py to run):

{{{

!python

def test_inter_library_dependencies_ordering(): lib1 = Library('lib1', '') lib2 = Library('lib2', '') lib3 = Library('lib3', '') lib4 = Library('lib4', '')

js1 = Resource(lib1, 'js1.js')
js2 = Resource(lib2, 'js2.js', depends=[js1]) 
js3 = Resource(lib3, 'js3.js', depends=[js2])

style1 = Resource(lib3, 'style1.css')
style2 = Resource(lib4, 'style2.css', depends=[style1])

needed = NeededResources()

needed.need(js3)
needed.need(style2)
resources = needed.resources()
assert resources.index(style1) < resources.index(style2)

}}}

The problem seems to be that inside sort_resources a sort key is computed for each library in relation to each other regardless of the kind of resource. Taking the kind of resource (indirectly via the "order" attribute) into account seems to solve it for this case (see attached patch).

Alberto

Comments (3)

  1. Anonymous

    Hi, Is there any planned release for this? We're currently doing a project called VoteIT (https://github.com/VoteIT/voteit.core) and would like to include Fanstatic, but we're using a lot of JS/CSS with interdependencies, and this very issue seems to be the problem.

    I'd be very grateful if it was possible to release a new version on PyPI :)

    Cheers, Robin robin@betahaus.net

  2. faassen

    Hi there, I didn't see this question appear on the issue, so I just ran into it by coincidence. Anyway, I just did a release.

    Next time please try mailing the fanstatic mailing list directly?

  3. Log in to comment