)]}'
{".zuul.yaml":[{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"46744bdb9dfdf07654f7b6fca4068cbf0c1c1467","unresolved":false,"context_lines":[{"line_number":1,"context_line":"- project:"},{"line_number":2,"context_line":"    templates:"},{"line_number":3,"context_line":"      - openstack-python3-train-jobs"},{"line_number":4,"context_line":"      - publish-openstack-docs-pti"},{"line_number":5,"context_line":"      - release-notes-jobs-python3"},{"line_number":6,"context_line":"    check:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"7faddb67_ed3a87e5","line":3,"updated":"2019-07-08 13:43:54.000000000","message":"I suspect this should just be removed in favour of the cinderlib-tox-py3* jobs, since otherwise we\u0027re duplicating tests (these ones run against PyPI versions of os-brick and cinder, while the others run against master, but I don\u0027t think it\u0027s intentional that we have both).","commit_id":"fc2740ac7049944b206bba65ddb55987388b6ba1"},{"author":{"_account_id":4257,"name":"Zane Bitter","email":"zbitter@redhat.com","username":"zaneb"},"change_message_id":"b72b9af925c5743ff36a9433c8f9e67faa97e645","unresolved":false,"context_lines":[{"line_number":1,"context_line":"- project:"},{"line_number":2,"context_line":"    templates:"},{"line_number":3,"context_line":"      - openstack-python3-train-jobs"},{"line_number":4,"context_line":"      - publish-openstack-docs-pti"},{"line_number":5,"context_line":"      - release-notes-jobs-python3"},{"line_number":6,"context_line":"    check:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"7faddb67_14fbe778","line":3,"in_reply_to":"7faddb67_427e05e5","updated":"2019-07-16 20:24:31.000000000","message":"Yeah, there were always bound to be a couple of special cases that will have to be migrated manually each release.\n\nWe could look at moving these templates into openstack-zuul-jobs (we have comparable templates like openstack-python3-train-jobs-neutron there already), but it may not be worth it if only one project is consuming it.","commit_id":"fc2740ac7049944b206bba65ddb55987388b6ba1"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"1994c03ab3037aa92a3f3762a6f33b435b519141","unresolved":false,"context_lines":[{"line_number":1,"context_line":"- project:"},{"line_number":2,"context_line":"    templates:"},{"line_number":3,"context_line":"      - openstack-python3-train-jobs"},{"line_number":4,"context_line":"      - publish-openstack-docs-pti"},{"line_number":5,"context_line":"      - release-notes-jobs-python3"},{"line_number":6,"context_line":"    check:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"7faddb67_427e05e5","line":3,"in_reply_to":"7faddb67_ed3a87e5","updated":"2019-07-08 14:59:57.000000000","message":"I think you are right. It\u0027s may cause confusion with our cycle goal stating projects should be using this template, but with the nature of this project it doesn\u0027t really add much benefit to be running the tests with the PyPi versions of the code.\n\nThis unfortunately means this is going to be an ongoing thing that we will get automatically proposed updates each cycle for the new template, and we will have to manually update the cinderlib-tox-* jobs as our supported runtimes change. But looks like that\u0027s just what we will have to do.","commit_id":"fc2740ac7049944b206bba65ddb55987388b6ba1"}],"tox.ini":[{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"8aed17cdef5b1d6acae20f8bcc3512e27110e327","unresolved":false,"context_lines":[{"line_number":1,"context_line":"[tox]"},{"line_number":2,"context_line":"minversion \u003d 2.0"},{"line_number":3,"context_line":"envlist \u003d py27,py37,pep8"},{"line_number":4,"context_line":"skipsdist \u003d True"},{"line_number":5,"context_line":"setenv \u003d VIRTUAL_ENV\u003d{envdir}"},{"line_number":6,"context_line":""}],"source_content_type":"text/x-properties","patch_set":3,"id":"7faddb67_373c62be","line":3,"range":{"start_line":3,"start_character":15,"end_line":3,"end_character":21},"updated":"2019-07-08 23:44:54.000000000","message":"Why is py36 being removed?\n\nAlso, I\u0027m wondering if \"py3\" should be used here instead so that the default py3 interpreter will be used, as available on the test host.","commit_id":"a18218ad0d49d0dda91a0ac610a81ae9f0d2f302"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"e2976b0e7ce0ed8c4fd2eb7923137c96c85efcea","unresolved":false,"context_lines":[{"line_number":1,"context_line":"[tox]"},{"line_number":2,"context_line":"minversion \u003d 2.0"},{"line_number":3,"context_line":"envlist \u003d py27,py37,pep8"},{"line_number":4,"context_line":"skipsdist \u003d True"},{"line_number":5,"context_line":"setenv \u003d VIRTUAL_ENV\u003d{envdir}"},{"line_number":6,"context_line":""}],"source_content_type":"text/x-properties","patch_set":3,"id":"7faddb67_775dfae7","line":3,"range":{"start_line":3,"start_character":15,"end_line":3,"end_character":21},"in_reply_to":"7faddb67_179846be","updated":"2019-07-09 00:08:57.000000000","message":"Thanks Sean. I was trying to find any previous discussion for context... py37 isn\u0027t available by default in the LTS versions of the popular distros that developers use; but py36 is... So, a bit wonky to slide in a default; sure devs can use \"tox -epy3\" or \"tox -epy36\" to run python3 tests alone...","commit_id":"a18218ad0d49d0dda91a0ac610a81ae9f0d2f302"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"3acc31f3d65fc10c907995d7c18b99f1238081e7","unresolved":false,"context_lines":[{"line_number":1,"context_line":"[tox]"},{"line_number":2,"context_line":"minversion \u003d 2.0"},{"line_number":3,"context_line":"envlist \u003d py27,py37,pep8"},{"line_number":4,"context_line":"skipsdist \u003d True"},{"line_number":5,"context_line":"setenv \u003d VIRTUAL_ENV\u003d{envdir}"},{"line_number":6,"context_line":""}],"source_content_type":"text/x-properties","patch_set":3,"id":"7faddb67_179846be","line":3,"range":{"start_line":3,"start_character":15,"end_line":3,"end_character":21},"in_reply_to":"7faddb67_373c62be","updated":"2019-07-08 23:57:16.000000000","message":"There have been various discussion on this, but basically, no need to require developers to have both py36 and py37 installed to be able to run local default tests. They can always run py36 if they want to, but it doesn\u0027t make much sense making both of them the default for local tox runs.\n\npy3 probably could be used, but then that would work with py35, and since py37 is the highest that we must support for train, it\u0027s good to be explicit about it.","commit_id":"a18218ad0d49d0dda91a0ac610a81ae9f0d2f302"}]}