)]}'
{"openstack/compute/v2/_proxy.py":[{"author":{"_account_id":1112,"name":"Everett Toews","email":"everett.toews@rackspace.com","username":"everett-toews"},"change_message_id":"a9d2f9025fa0e626e5ca53eadb06929f0b965a4b","unresolved":false,"context_lines":[{"line_number":72,"context_line":""},{"line_number":73,"context_line":"        :param value: Either the id of a flavor or a"},{"line_number":74,"context_line":"                      :class:`~openstack.compute.v2.flavor.Flavor` instance."},{"line_number":75,"context_line":"        :attrs kwargs: The attributes to update on the flavor represented"},{"line_number":76,"context_line":"                       by ``value``."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"        :returns: The updated flavor"}],"source_content_type":"text/x-python","patch_set":1,"id":"3acd31a7_789779ec","line":75,"updated":"2015-05-04 22:06:28.000000000","message":"How are users supposed to know what attributes they can update and what types/formats those updates take?","commit_id":"089c7153da01fdd145041fb872192cae1d191c8c"},{"author":{"_account_id":8736,"name":"Terry Howe","email":"terrylhowe@gmail.com","username":"terrylhowe"},"change_message_id":"78581813b740f8b4d6a25f9f3f7bc80247ed1013","unresolved":false,"context_lines":[{"line_number":72,"context_line":""},{"line_number":73,"context_line":"        :param value: Either the id of a flavor or a"},{"line_number":74,"context_line":"                      :class:`~openstack.compute.v2.flavor.Flavor` instance."},{"line_number":75,"context_line":"        :attrs kwargs: The attributes to update on the flavor represented"},{"line_number":76,"context_line":"                       by ``value``."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"        :returns: The updated flavor"}],"source_content_type":"text/x-python","patch_set":1,"id":"3acd31a7_b32d1d97","line":75,"in_reply_to":"3acd31a7_789779ec","updated":"2015-05-05 13:31:21.000000000","message":"Yeh, good question.  I would think the resource class would be the best place to document that.  Trying to document that here would surely be outdated and wrong often.","commit_id":"089c7153da01fdd145041fb872192cae1d191c8c"},{"author":{"_account_id":8257,"name":"Brian Curtin","email":"brian@python.org","username":"briancurtin"},"change_message_id":"3c85d5234ead9d39279ea4eb3466e4f1dc716905","unresolved":false,"context_lines":[{"line_number":72,"context_line":""},{"line_number":73,"context_line":"        :param value: Either the id of a flavor or a"},{"line_number":74,"context_line":"                      :class:`~openstack.compute.v2.flavor.Flavor` instance."},{"line_number":75,"context_line":"        :attrs kwargs: The attributes to update on the flavor represented"},{"line_number":76,"context_line":"                       by ``value``."},{"line_number":77,"context_line":""},{"line_number":78,"context_line":"        :returns: The updated flavor"}],"source_content_type":"text/x-python","patch_set":1,"id":"3acd31a7_5c8ed179","line":75,"in_reply_to":"3acd31a7_b32d1d97","updated":"2015-05-05 18:29:08.000000000","message":"This really should be automated, and we can maybe write a sphinx extension to handle it by just wording it that kwargs takes props on flavor.Flavor, and then the extension pulls off the names of those props on the class. That\u0027s much bigger than this change, of course.\n\nIn a similar area, another change I have out right now for the query parameters on list proxies manually adds the possible params to be sent in based on the documentation. Those aren\u0027t known anywhere else as props so I don\u0027t know how to automate or do those better either, but right now they have to be manually listed in the docstring.\n\nI don\u0027t know if the answer is to manually list all of them or to list none of them right now. I think it might be enough for right now to leave this as-is because the kwargs points to value and value points to the Resource class which has the props listed.","commit_id":"089c7153da01fdd145041fb872192cae1d191c8c"}]}