)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":14611,"name":"dasm","display_name":"dasm","email":"dsmigiel@redhat.com","username":"dasm"},"change_message_id":"ce3e22499760c5abe6c1ec9d2b6e16d99137fc75","unresolved":false,"context_lines":[{"line_number":11,"context_line":"was applied to NeutronDbObject, and once when rbac metaclass was"},{"line_number":12,"context_line":"applied, when we were calling type() in rbac metaclass\u0027 __new__."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"To avoid that behaviour, we can introduce a separate base \u0027class\u0027 for"},{"line_number":15,"context_line":"rbac aware objects that would be a result of with_metaclass call using"},{"line_number":16,"context_line":"the rbac metaclass, and NeutronDbOjbect as the actual base. Then we use"},{"line_number":17,"context_line":"the base class in place of NeutronDbObject base class for all objects"},{"line_number":18,"context_line":"that are RBAC aware."},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"This avoids the duplicate call issue."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Change-Id: Ia12f56f7d40c38e679edc21e13871e27ad1820ee"},{"line_number":23,"context_line":"Partially-Implements: blueprint adopt-oslo-versioned-objects-for-db"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"9a89bdaa_e2ccff36","line":20,"range":{"start_line":14,"start_character":0,"end_line":20,"end_character":37},"updated":"2016-09-08 13:57:06.000000000","message":"Thanks for this explanation. I was wondering and trying to understand this. Especially, when documentation describes with_metaclass and add_metaclass [1] are exchangeable.\n\n[1] https://pythonhosted.org/six/#six.with_metaclass","commit_id":"79f8f26e9cbfd96459429fbce214d0d84d013c86"}]}
