Implement `for_packages_append` on `Resource` about commoncode HOT 3 CLOSED

Another possibility could be to add and pass a add_to_package(resource, ...) method as an argument to the assemble(..., package_adder=add_to_package, ...) functions?
With a default that would be using a list-backed implementation... and then in SCIO you would have a Django db-backed implmentation of the same function and you would call it when you call assemble?

I like this approach better than the one I posted before. It makes more sense to pass in the package adding function as an argument into assemble than to add a method to Resource that deals with an attribute that may not be there.

from commoncode.

re:

A solution would be to create a method on the Resource class named for_packages_append that appends a package_uid to Resource.for_packages

This can work.

An alternative could be use a new Codebase argument that would be the Resource class to use... today this class is crafted based on the provided attributes

Another possibility could be to add and pass a add_to_package(resource, ...) method as an argument to the assemble(..., package_adder=add_to_package, ...) functions?
With a default that would be using a list-backed implementation... and then in SCIO you would have a Django db-backed implmentation of the same function and you would call it when you call assemble?

from commoncode.

This has been implemented and merged in nexB/scancode-toolkit#3035
Thanks!

from commoncode.