cubicweb-container #4965400 yams/cubicweb monkeypatches break cubes not using container [done]

I get this when running tests for cubicweb-skos, which does not use container:

  [...]

  File "/home/dlaxalde/projects/saem/cubes/skos/dataimport.py", line 111, in __init__
    if rschema(rtype).final:
  File "/usr/lib/python2.7/dist-packages/yams/schema.py", line 1233, in rschema
    raise KeyError('No relation named %s in schema'%rtype)
KeyError: 'No relation named container_parent in schema'

Apparently, cubicweb-container just appears to be somewhere in the cubes path (installed system-wide), and its __init__.py is thus loaded triggering some Yams and CubicWeb monkeypatches to be applied.

These monkeypatches should be moved elsewhere.

priorityimportant
typebug
done in<not specified>
load left0.000
closed by#d2c4c11c78f0 Site: move stuff from __init__ there as it may interfere with unconcerned apps
patchSite: move stuff from __init__ there as it may interfere with unconcerned apps [applied]Move Yams and CubicWeb monkeypatches into site_cubicweb.py [rejected]