)]}'
{"tox.ini":[{"author":{"_account_id":18955,"name":"dharmendra","email":"dharmendra.kushwaha@gmail.com","username":"dharmendra"},"change_message_id":"4d10db5794e42cd32862a27d9a96f9e89850c998","unresolved":false,"context_lines":[{"line_number":1,"context_line":"[tox]"},{"line_number":2,"context_line":"envlist \u003d py37,py36,py27,pep8,docs"},{"line_number":3,"context_line":"minversion \u003d 2.0"},{"line_number":4,"context_line":"skipsdist \u003d True"},{"line_number":5,"context_line":""}],"source_content_type":"text/x-properties","patch_set":1,"id":"7faddb67_aa429c39","side":"PARENT","line":2,"range":{"start_line":2,"start_character":15,"end_line":2,"end_character":19},"updated":"2019-08-20 08:01:07.000000000","message":"Why to to delete py36 from here, while holding in setup.cfg ?","commit_id":"6ec1956dfaed877bf9e86fa316e265303c187a91"},{"author":{"_account_id":18955,"name":"dharmendra","email":"dharmendra.kushwaha@gmail.com","username":"dharmendra"},"change_message_id":"dde2ea021ffb470ca28cc25ff7e9f291f5c82302","unresolved":false,"context_lines":[{"line_number":1,"context_line":"[tox]"},{"line_number":2,"context_line":"envlist \u003d py37,py36,py27,pep8,docs"},{"line_number":3,"context_line":"minversion \u003d 2.0"},{"line_number":4,"context_line":"skipsdist \u003d True"},{"line_number":5,"context_line":""}],"source_content_type":"text/x-properties","patch_set":1,"id":"7faddb67_636eca01","side":"PARENT","line":2,"range":{"start_line":2,"start_character":15,"end_line":2,"end_character":19},"in_reply_to":"7faddb67_2069b6f7","updated":"2019-08-23 05:51:54.000000000","message":"Agree. Actually my point is, it does not seems meaningful to still having py36 in setup.cfg.\nBut anyway, we can go for that cleanup later.","commit_id":"6ec1956dfaed877bf9e86fa316e265303c187a91"},{"author":{"_account_id":11805,"name":"Corey Bryant","email":"corey.bryant@canonical.com","username":"coreycb"},"change_message_id":"89ef8645fefb1d2ecb1e84ae6d8dae7f7626e82e","unresolved":false,"context_lines":[{"line_number":1,"context_line":"[tox]"},{"line_number":2,"context_line":"envlist \u003d py37,py36,py27,pep8,docs"},{"line_number":3,"context_line":"minversion \u003d 2.0"},{"line_number":4,"context_line":"skipsdist \u003d True"},{"line_number":5,"context_line":""}],"source_content_type":"text/x-properties","patch_set":1,"id":"7faddb67_80d2d1d0","side":"PARENT","line":2,"range":{"start_line":2,"start_character":15,"end_line":2,"end_character":19},"in_reply_to":"7faddb67_636eca01","updated":"2019-08-23 16:06:58.000000000","message":"py36 in setup.cfg needs to stay since Train supports py36, py37 and py27, and that is what the gate tests as well.","commit_id":"6ec1956dfaed877bf9e86fa316e265303c187a91"},{"author":{"_account_id":11805,"name":"Corey Bryant","email":"corey.bryant@canonical.com","username":"coreycb"},"change_message_id":"7db1f07dab91851c9a04f298aa7b5a8f758ee1d3","unresolved":false,"context_lines":[{"line_number":1,"context_line":"[tox]"},{"line_number":2,"context_line":"envlist \u003d py37,py36,py27,pep8,docs"},{"line_number":3,"context_line":"minversion \u003d 2.0"},{"line_number":4,"context_line":"skipsdist \u003d True"},{"line_number":5,"context_line":""}],"source_content_type":"text/x-properties","patch_set":1,"id":"7faddb67_2069b6f7","side":"PARENT","line":2,"range":{"start_line":2,"start_character":15,"end_line":2,"end_character":19},"in_reply_to":"7faddb67_aa429c39","updated":"2019-08-22 14:23:20.000000000","message":"envlist is just the default that is run with \u0027tox\u0027 when you don\u0027t specify a specific environment. You\u0027ll still be able to run \u0027tox -e py36\u0027. The idea is to just run the latest py3 when running \u0027tox\u0027 by default to save developers time.","commit_id":"6ec1956dfaed877bf9e86fa316e265303c187a91"}]}