Circular routes on PyAssets with parents

[mattysmith22]

An asset can be its own parent, and you can create circular dependencies with the parenting (a -> b -> c -> a). This doesn't make logical sense, but it is not a significant problem right now. As long as we take care with any code in the future that traverses these dependencies!

I personally am not intending on fixing this before release.

[mattysmith22]

My current plan for this is to do something as follows.

If a child wants to assign asset x as its parent, then x must have no parent of its own. This does limit how deep it can go to a depth of 1, but it is easier to do that then have sprawling parent-child depencency trees. It depends on whether that would be necessary?

[mattysmith22]

The main question is whether this would be failure or something that would be fixed automatically. It would be relatively simple to make it do the fix so that it assigns the parents parent if necessary. E.g. if the syntax a(b(c),d) meant asset A which is parents to assets B and D and asset B being parent to c it could automatically change the former to a(b,c,d)