)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":11224,"name":"Swami Reddy","email":"swamireddy@gmail.com","username":"swamireddy"},"change_message_id":"1f00b8b1a795e9a3588237928861f2fc509a23e1","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     janonymous \u003cjanonymous.codevulture@gmail.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2015-12-20 09:38:06 +0530"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Adding a new check for warn method deprecation."},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Python 3 deprecated the logger.warn method in favor of warning"},{"line_number":10,"context_line":"this change would detect warn usage in the code."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"1a7b0d38_cbd876f2","line":7,"range":{"start_line":7,"start_character":0,"end_line":7,"end_character":6},"updated":"2015-12-23 07:30:01.000000000","message":"Change \"Adding\" to \"Add\"","commit_id":"b2100d648898680ca8d6de7ad2f789a8f8d623b9"}],"hacking/checks/python23.py":[{"author":{"_account_id":16896,"name":"Ondřej Nový","email":"novy@ondrej.org","username":"onovy"},"change_message_id":"9426cb7b73c8125c4be8391b2aa9f2deac1b1e82","unresolved":false,"context_lines":[{"line_number":241,"context_line":"    for token_type, text, start_index, _, _ in tokens:"},{"line_number":242,"context_line":""},{"line_number":243,"context_line":"        if token_type \u003d\u003d tokenize.NAME:"},{"line_number":244,"context_line":"            if text \u003d\u003d \"warn\":"},{"line_number":245,"context_line":"                yield (start_index[1],"},{"line_number":246,"context_line":"                       \"H239: %s is deprecated, use warning\" % text)"},{"line_number":247,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"3a7e1126_9601a53a","line":244,"updated":"2015-12-20 11:11:20.000000000","message":"with this you are searching for call to every method warn. Is there any way to limit it to logger only?","commit_id":"b2100d648898680ca8d6de7ad2f789a8f8d623b9"},{"author":{"_account_id":18015,"name":"Peter Lisák","email":"peter.lisak@gmail.com","username":"peter.lisak"},"change_message_id":"cb462e7b2d4cf8551f9688f5d35459bf690a7b4e","unresolved":false,"context_lines":[{"line_number":241,"context_line":"    for token_type, text, start_index, _, _ in tokens:"},{"line_number":242,"context_line":""},{"line_number":243,"context_line":"        if token_type \u003d\u003d tokenize.NAME:"},{"line_number":244,"context_line":"            if text \u003d\u003d \"warn\":"},{"line_number":245,"context_line":"                yield (start_index[1],"},{"line_number":246,"context_line":"                       \"H239: %s is deprecated, use warning\" % text)"},{"line_number":247,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"3a7e1126_ad41e4aa","line":244,"in_reply_to":"3a7e1126_2cc66468","updated":"2015-12-21 08:01:46.000000000","message":"It seems there is no better way. Others checks (eg. assertEquals) are made in the same way. \n\nBTW pylint (in py3 env) can detect these deprecated functions (warn, assertEquals, ...), but probably there is a reason why is not used.","commit_id":"b2100d648898680ca8d6de7ad2f789a8f8d623b9"},{"author":{"_account_id":14867,"name":"Jaivish Kothari(janonymous)","email":"janonymous.codevulture@gmail.com","username":"Janonymous"},"change_message_id":"a3e33873411b8bab534225b66a9edd3a286afab4","unresolved":false,"context_lines":[{"line_number":241,"context_line":"    for token_type, text, start_index, _, _ in tokens:"},{"line_number":242,"context_line":""},{"line_number":243,"context_line":"        if token_type \u003d\u003d tokenize.NAME:"},{"line_number":244,"context_line":"            if text \u003d\u003d \"warn\":"},{"line_number":245,"context_line":"                yield (start_index[1],"},{"line_number":246,"context_line":"                       \"H239: %s is deprecated, use warning\" % text)"},{"line_number":247,"context_line":""}],"source_content_type":"text/x-python","patch_set":1,"id":"3a7e1126_2cc66468","line":244,"in_reply_to":"3a7e1126_9601a53a","updated":"2015-12-20 14:58:20.000000000","message":"i am not sure how to handle it, the above comment mentions that also. Can you suggest some way for it ?","commit_id":"b2100d648898680ca8d6de7ad2f789a8f8d623b9"}],"tox.ini":[{"author":{"_account_id":16896,"name":"Ondřej Nový","email":"novy@ondrej.org","username":"onovy"},"change_message_id":"9426cb7b73c8125c4be8391b2aa9f2deac1b1e82","unresolved":false,"context_lines":[{"line_number":1,"context_line":"[tox]"},{"line_number":2,"context_line":"minversion \u003d 1.6"},{"line_number":3,"context_line":"skipsdist \u003d True"},{"line_number":4,"context_line":"envlist \u003d py34,py26,py27,pep8,pypy"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"[testenv]"},{"line_number":7,"context_line":"usedevelop \u003d True"}],"source_content_type":"text/x-properties","patch_set":1,"id":"3a7e1126_768bd9c3","line":4,"updated":"2015-12-20 11:11:20.000000000","message":"don\u0027t know why this order should be relevant. can you explain it a bit more please? i read commit message, but it don\u0027t make sense for me","commit_id":"b2100d648898680ca8d6de7ad2f789a8f8d623b9"},{"author":{"_account_id":14867,"name":"Jaivish Kothari(janonymous)","email":"janonymous.codevulture@gmail.com","username":"Janonymous"},"change_message_id":"2f7bb0a52a7e5c330c8a76a1e7ca0a86967d8f8e","unresolved":false,"context_lines":[{"line_number":1,"context_line":"[tox]"},{"line_number":2,"context_line":"minversion \u003d 1.6"},{"line_number":3,"context_line":"skipsdist \u003d True"},{"line_number":4,"context_line":"envlist \u003d py34,py26,py27,pep8,pypy"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"[testenv]"},{"line_number":7,"context_line":"usedevelop \u003d True"}],"source_content_type":"text/x-properties","patch_set":1,"id":"3a7e1126_af5c6a7d","line":4,"in_reply_to":"3a7e1126_2d4c149d","updated":"2015-12-21 13:18:19.000000000","message":"In the bug it is written to erase .testrepository to make the env clean (i.e when testr repo is not initialized), but after the envlist changes are made there is no need to clean testr repo everytime.\nThis could be verified from other project related changes also on this bug fix releases.","commit_id":"b2100d648898680ca8d6de7ad2f789a8f8d623b9"},{"author":{"_account_id":14867,"name":"Jaivish Kothari(janonymous)","email":"janonymous.codevulture@gmail.com","username":"Janonymous"},"change_message_id":"a3e33873411b8bab534225b66a9edd3a286afab4","unresolved":false,"context_lines":[{"line_number":1,"context_line":"[tox]"},{"line_number":2,"context_line":"minversion \u003d 1.6"},{"line_number":3,"context_line":"skipsdist \u003d True"},{"line_number":4,"context_line":"envlist \u003d py34,py26,py27,pep8,pypy"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"[testenv]"},{"line_number":7,"context_line":"usedevelop \u003d True"}],"source_content_type":"text/x-properties","patch_set":1,"id":"3a7e1126_aca8148d","line":4,"in_reply_to":"3a7e1126_768bd9c3","updated":"2015-12-20 14:58:20.000000000","message":"yes, Please find the closed bug mentioned also, it has the relevant details. when tox is ran using py34 after py27 it shows db type errors which is common in most openstack projects also ,only way to solve is to run py34 env first.","commit_id":"b2100d648898680ca8d6de7ad2f789a8f8d623b9"},{"author":{"_account_id":18015,"name":"Peter Lisák","email":"peter.lisak@gmail.com","username":"peter.lisak"},"change_message_id":"cb462e7b2d4cf8551f9688f5d35459bf690a7b4e","unresolved":false,"context_lines":[{"line_number":1,"context_line":"[tox]"},{"line_number":2,"context_line":"minversion \u003d 1.6"},{"line_number":3,"context_line":"skipsdist \u003d True"},{"line_number":4,"context_line":"envlist \u003d py34,py26,py27,pep8,pypy"},{"line_number":5,"context_line":""},{"line_number":6,"context_line":"[testenv]"},{"line_number":7,"context_line":"usedevelop \u003d True"}],"source_content_type":"text/x-properties","patch_set":1,"id":"3a7e1126_2d4c149d","line":4,"in_reply_to":"3a7e1126_aca8148d","updated":"2015-12-21 08:01:46.000000000","message":"Why don\u0027t you also erase .testrepository? In the closed bug it is mentioned: erase the .testrepository *and* run \"tox -e py34\" first.\nOr am i missing something?","commit_id":"b2100d648898680ca8d6de7ad2f789a8f8d623b9"}]}