)]}'
{"playbooks/files/project-requirements-change.py":[{"author":{"_account_id":14288,"name":"Matthew Thode","display_name":"prometheanfire","email":"mthode@mthode.org","username":"prometheanfire"},"change_message_id":"b5ce3c9186288e076dc27b965aab82327dc08ec6","unresolved":false,"context_lines":[{"line_number":34,"context_line":"    print(cmd)"},{"line_number":35,"context_line":"    cmd_list \u003d shlex.split(str(cmd))"},{"line_number":36,"context_line":"    kwargs \u003d {}"},{"line_number":37,"context_line":"    if sys.version_info \u003e\u003d (3, ):"},{"line_number":38,"context_line":"        kwargs \u003d {"},{"line_number":39,"context_line":"            \u0027encoding\u0027: \u0027utf-8\u0027,"},{"line_number":40,"context_line":"            \u0027errors\u0027: \u0027surrogateescape\u0027,"}],"source_content_type":"text/x-python","patch_set":1,"id":"9fb8cfa7_c36f20c3","line":37,"updated":"2019-06-23 06:40:45.000000000","message":"I\u0027m not sure, I kinda think we should support running with py27 for as long as we support it.  What happens to older branches?","commit_id":"f094c78968ad746d1785cbcc20acb00c4c6acf21"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"327890c7075682ff0534af56e2a2f5709580eb07","unresolved":false,"context_lines":[{"line_number":34,"context_line":"    print(cmd)"},{"line_number":35,"context_line":"    cmd_list \u003d shlex.split(str(cmd))"},{"line_number":36,"context_line":"    kwargs \u003d {}"},{"line_number":37,"context_line":"    if sys.version_info \u003e\u003d (3, ):"},{"line_number":38,"context_line":"        kwargs \u003d {"},{"line_number":39,"context_line":"            \u0027encoding\u0027: \u0027utf-8\u0027,"},{"line_number":40,"context_line":"            \u0027errors\u0027: \u0027surrogateescape\u0027,"}],"source_content_type":"text/x-python","patch_set":1,"id":"9fb8cfa7_a7ba5d6b","line":37,"updated":"2019-06-20 13:17:25.000000000","message":"Thinking about this more, we now default to python 3 for all tools and gate jobs. I think I\u0027d actually rather see this whole version checking dropped and just make this py3 compatible only.\n\nMaybe an idea for later cleanup.","commit_id":"f094c78968ad746d1785cbcc20acb00c4c6acf21"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"728a1c1a1e13a0aadf0e8b0d5ebbd21eab9786f7","unresolved":false,"context_lines":[{"line_number":34,"context_line":"    print(cmd)"},{"line_number":35,"context_line":"    cmd_list \u003d shlex.split(str(cmd))"},{"line_number":36,"context_line":"    kwargs \u003d {}"},{"line_number":37,"context_line":"    if sys.version_info \u003e\u003d (3, ):"},{"line_number":38,"context_line":"        kwargs \u003d {"},{"line_number":39,"context_line":"            \u0027encoding\u0027: \u0027utf-8\u0027,"},{"line_number":40,"context_line":"            \u0027errors\u0027: \u0027surrogateescape\u0027,"}],"source_content_type":"text/x-python","patch_set":1,"id":"9fb8cfa7_6cf8a1c3","line":37,"in_reply_to":"9fb8cfa7_c36f20c3","updated":"2019-06-24 04:53:16.000000000","message":"This is a generally interesting idea for discussion at the team meeting.\n\n1) Can/Should we separate our tools from the data we maintain WRT py2 vs py3.  Is it okay for example to for requirements-check or generate-constraints to only work until py3 but still generate valid data for py2?\n2) Are we generally ready py3 only early next cycle?","commit_id":"f094c78968ad746d1785cbcc20acb00c4c6acf21"}]}