)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"74c4e3269485e23997f0537058c0199edc3d96ee","unresolved":false,"context_lines":[{"line_number":9,"context_line":"Latest releases of python construct have demonstrated significant"},{"line_number":10,"context_line":"improvements and we\u0027d like to remove limitations on versions for"},{"line_number":11,"context_line":"Python 3."},{"line_number":12,"context_line":"Each project can adjust upper limit directly if needed."},{"line_number":13,"context_line":"Also setting upper boundaries to 2.10.56 wihch is the latest"},{"line_number":14,"context_line":"version and limiting up to version 2.10.54 for Python 2.7."},{"line_number":15,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"1f493fa4_0d438143","line":12,"range":{"start_line":12,"start_character":0,"end_line":12,"end_character":55},"updated":"2020-04-30 13:20:53.000000000","message":"This isn\u0027t quite accurate. All official projects should be using this upper-constraints file which is what will set the upper limit for the projects.\n\nBut this looks good and is how we\u0027ve handled other libraries that have dropped py2 support to allow py3 runtimes to use the newer versions while restricting the (very few) projects still running py2 to use the last version available for that runtime.\n\nSwift is really the only one that should be still using py2, so if this isn\u0027t used by swift, we can just drop the cap and use the latest version in the upper constraints. But until we clean up the other py2 upper constraints, I think this is probably the best route to go.","commit_id":"769bb033c6ccb2ab11a867a97b2fa29b56b5572d"}]}