)]}'
{"quantum/policy.py":[{"author":{"_account_id":2592,"name":"Mark McClain","email":"mark@mcclain.xyz","username":"markmcclain"},"change_message_id":"c59e1239db60a1ba5a002f7db29c3327f7e892b1","unresolved":false,"context_lines":[{"line_number":20,"context_line":"\"\"\""},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"from quantum.api.v2 import attributes"},{"line_number":23,"context_line":"from quantum.common import config"},{"line_number":24,"context_line":"from quantum.common import exceptions"},{"line_number":25,"context_line":"import quantum.common.utils as utils"},{"line_number":26,"context_line":"from quantum.openstack.common import cfg"}],"source_content_type":"text/x-python","patch_set":1,"id":"AAAAM3%2F%2FJus%3D","line":23,"updated":"2013-02-05 15:01:36.000000000","message":"Why are we relying on import side effects.  Why not use a more explicit import?\n\ncfg.CONF.import_opt(\u0027policy_file\u0027, \u0027quantum.common.config\u0027)\n\n(Yes I know this essentially does the same thing, but explicitness will result in an error if the option is renamed or moved.)","commit_id":"b195634cb2c1e9401e8fc998d023113cc9cf7b5f"},{"author":{"_account_id":1267,"name":"Alexei Ababilov","display_name":"Alexei Ababilov","email":"ilovegnulinux@gmail.com","username":"aababilov"},"unresolved":false,"context_lines":[{"line_number":20,"context_line":"\"\"\""},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"from quantum.api.v2 import attributes"},{"line_number":23,"context_line":"from quantum.common import config"},{"line_number":24,"context_line":"from quantum.common import exceptions"},{"line_number":25,"context_line":"import quantum.common.utils as utils"},{"line_number":26,"context_line":"from quantum.openstack.common import cfg"}],"source_content_type":"text/x-python","patch_set":1,"id":"AAAAM3%2F%2FJqM%3D","line":23,"in_reply_to":"AAAAM3%2F%2FJus%3D","updated":"2013-02-05 15:30:13.000000000","message":"Done","commit_id":"b195634cb2c1e9401e8fc998d023113cc9cf7b5f"}]}
