)]}'
{"openstack/common/versionutils.py":[{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"bb82c08c649f3a86676ade0587351a721f1ae4b1","unresolved":false,"context_lines":[{"line_number":154,"context_line":"            else:"},{"line_number":155,"context_line":"                # There are no plans to remove this function, but it is"},{"line_number":156,"context_line":"                # now deprecated."},{"line_number":157,"context_line":"                msg \u003d self._deprecated_msg_with_no_alternative_no_removal"},{"line_number":158,"context_line":"        return msg, details"},{"line_number":159,"context_line":""},{"line_number":160,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"1a6ced46_5dd564b7","line":157,"updated":"2015-03-25 21:56:07.000000000","message":"We should provide a global value \"NEVER\" or something similar, as \"remove_in\u003d0\" is not clear when re-reading code.\n\nThis is likely a followup.","commit_id":"7f263be4b1d6c74b248cdbb539accb394695e1b3"},{"author":{"_account_id":11748,"name":"Chris St. Pierre","email":"cstpierr@cisco.com","username":"stpierre"},"change_message_id":"136ec28f0046d859bab8e9082a9ee2f46ddd13a9","unresolved":false,"context_lines":[{"line_number":154,"context_line":"            else:"},{"line_number":155,"context_line":"                # There are no plans to remove this function, but it is"},{"line_number":156,"context_line":"                # now deprecated."},{"line_number":157,"context_line":"                msg \u003d self._deprecated_msg_with_no_alternative_no_removal"},{"line_number":158,"context_line":"        return msg, details"},{"line_number":159,"context_line":""},{"line_number":160,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"fa963961_df394943","line":157,"in_reply_to":"1a6ced46_5dd564b7","updated":"2015-03-26 21:13:01.000000000","message":"Given that the default remove_in is 2, what about \"remove_in\u003dNone\"? That seems clearer to me, and doesn\u0027t require an additional global value.","commit_id":"7f263be4b1d6c74b248cdbb539accb394695e1b3"},{"author":{"_account_id":2903,"name":"Morgan Fainberg","email":"morgan.fainberg@gmail.com","username":"mdrnstm"},"change_message_id":"854582eea6429b4a1d76799496498cba8b56a099","unresolved":false,"context_lines":[{"line_number":154,"context_line":"            else:"},{"line_number":155,"context_line":"                # There are no plans to remove this function, but it is"},{"line_number":156,"context_line":"                # now deprecated."},{"line_number":157,"context_line":"                msg \u003d self._deprecated_msg_with_no_alternative_no_removal"},{"line_number":158,"context_line":"        return msg, details"},{"line_number":159,"context_line":""},{"line_number":160,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"fa963961_4deeac23","line":157,"in_reply_to":"fa963961_df394943","updated":"2015-03-27 00:08:14.000000000","message":"Works for me as well. Just a clear way to say \"this will not be removed\", I\u0027d like to keep the remove_in\u003d0 compatibility but remove_in\u003dNone or remove_in\u003d0 should be a minor change to the if checks above.","commit_id":"7f263be4b1d6c74b248cdbb539accb394695e1b3"}]}