)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":2,"name":"Monty Taylor","email":"mordred@inaugust.com","username":"mordred"},"change_message_id":"443bde4d2fcae3c39e7ba09ddff047b7d5a9f223","unresolved":false,"context_lines":[{"line_number":8,"context_line":""},{"line_number":9,"context_line":"In patch 789888 we began relying on EntryPoint.resolve(), which only"},{"line_number":10,"context_line":"exists in setuptools \u003e\u003d 12, breaking support for setuptools \u003c 12.  This"},{"line_number":11,"context_line":"includes the default virtualenv installations from may LTS distributions."},{"line_number":12,"context_line":"As ep.load with arguments is deprecated we will attempt to use"},{"line_number":13,"context_line":"ep.resolve if it exists and fall back to ep.load(false) if it does not."},{"line_number":14,"context_line":"setuptools 11 is the odd release out, as this was when load with"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"9a68dd71_e4353846","line":11,"updated":"2016-01-21 13:43:08.000000000","message":"#notaminusone - s/may/many/ ... only if you respin for another reason","commit_id":"d19459daa8616dd18fde016c2970ffc41ff4ccdd"}],"pbr/tests/test_integration.py":[{"author":{"_account_id":4190,"name":"lifeless","email":"robertc@robertcollins.net","username":"lifeless"},"change_message_id":"f997a679ce89eb32e4206be67031af1bbcd65e6f","unresolved":false,"context_lines":[{"line_number":240,"context_line":"        (\u0027Jessie\u0027, {\u0027modules\u0027: [\u0027pip\u003d\u003d1.5.6\u0027, \u0027setuptools\u003d\u003d5.5.1\u0027]}),"},{"line_number":241,"context_line":"        # Wheezy has pip1.1, which cannot be called with \u0027-m pip\u0027"},{"line_number":242,"context_line":"        # So we\u0027ll use a different version of pip here."},{"line_number":243,"context_line":"        (\u0027WheezyPrecise\u0027, {\u0027modules\u0027: [\u0027pip\u003d\u003d1.4.1\u0027, \u0027setuptools\u003d\u003d0.6c11\u0027]})"},{"line_number":244,"context_line":"    ]"},{"line_number":245,"context_line":""},{"line_number":246,"context_line":"    @testtools.skipUnless("}],"source_content_type":"text/x-python","patch_set":2,"id":"ba63e191_00bb7a28","line":243,"updated":"2016-01-20 05:57:57.000000000","message":"I am confuse: your docs prose and the scenarios above suggest 0.7.2 is the minimum, but this test shows setuptools 0.6c11 working?\n\nAlso, it occurs to me we should document this magic glue we\u0027ve concocted.","commit_id":"81727aa1dec0d27a8eeb81daafaba8e354ea593f"},{"author":{"_account_id":12612,"name":"Sachi King","email":"nakato@nakato.io","username":"nakato"},"change_message_id":"fadd9bb812618288b04556990c1c0797f797b8ef","unresolved":false,"context_lines":[{"line_number":240,"context_line":"        (\u0027Jessie\u0027, {\u0027modules\u0027: [\u0027pip\u003d\u003d1.5.6\u0027, \u0027setuptools\u003d\u003d5.5.1\u0027]}),"},{"line_number":241,"context_line":"        # Wheezy has pip1.1, which cannot be called with \u0027-m pip\u0027"},{"line_number":242,"context_line":"        # So we\u0027ll use a different version of pip here."},{"line_number":243,"context_line":"        (\u0027WheezyPrecise\u0027, {\u0027modules\u0027: [\u0027pip\u003d\u003d1.4.1\u0027, \u0027setuptools\u003d\u003d0.6c11\u0027]})"},{"line_number":244,"context_line":"    ]"},{"line_number":245,"context_line":""},{"line_number":246,"context_line":"    @testtools.skipUnless("}],"source_content_type":"text/x-python","patch_set":2,"id":"9a68dd71_2f1108ad","line":243,"in_reply_to":"ba63e191_00bb7a28","updated":"2016-01-21 00:08:54.000000000","message":"0.7.2 is the minimum version only if a project is using environment markers, as that is the version when \u0027evaluate_marker\u0027 was added to setuptools.  \n\nWe could, attempt to backport/vendor an early version of evaluate_markers into PBR for use with 0.6c11, if that isn\u0027t too big a can of worms.\n\nI\u0027m focusing on 0.6c11, as this is what Debian Wheezy and Precise have packaged in their virtualenv package.\n\nIf a project does not use environment markers, then PBR continues to work with 0.6c11, and potentially older, but I don\u0027t see older in use anywhere.","commit_id":"81727aa1dec0d27a8eeb81daafaba8e354ea593f"}],"pbr/util.py":[{"author":{"_account_id":4190,"name":"lifeless","email":"robertc@robertcollins.net","username":"lifeless"},"change_message_id":"8fd852c910600af6adce7383cd88d9780f47edd9","unresolved":false,"context_lines":[{"line_number":564,"context_line":"                # can, otherwise fall back to load."},{"line_number":565,"context_line":"                # Setuptools 11 will throw a deprication warning, as it"},{"line_number":566,"context_line":"                # uses _load instead of resolve."},{"line_number":567,"context_line":"                cmdclass \u003d ep.load(False)"},{"line_number":568,"context_line":"            dist.cmdclass[ep.name] \u003d cmdclass"},{"line_number":569,"context_line":""},{"line_number":570,"context_line":"    for cmd, _ in dist.get_command_list():"}],"source_content_type":"text/x-python","patch_set":4,"id":"9a68dd71_656d4acb","line":567,"updated":"2016-01-24 23:47:26.000000000","message":"Should we try:\n\n resolve\n _load(False)\n load(False)\n\nto avoid the deprecation warning?","commit_id":"d19459daa8616dd18fde016c2970ffc41ff4ccdd"},{"author":{"_account_id":12612,"name":"Sachi King","email":"nakato@nakato.io","username":"nakato"},"change_message_id":"0080608ce5f4173ff075df84a48ac4fd51acc7c0","unresolved":false,"context_lines":[{"line_number":564,"context_line":"                # can, otherwise fall back to load."},{"line_number":565,"context_line":"                # Setuptools 11 will throw a deprication warning, as it"},{"line_number":566,"context_line":"                # uses _load instead of resolve."},{"line_number":567,"context_line":"                cmdclass \u003d ep.load(False)"},{"line_number":568,"context_line":"            dist.cmdclass[ep.name] \u003d cmdclass"},{"line_number":569,"context_line":""},{"line_number":570,"context_line":"    for cmd, _ in dist.get_command_list():"}],"source_content_type":"text/x-python","patch_set":4,"id":"9a68dd71_45c92658","line":567,"in_reply_to":"9a68dd71_656d4acb","updated":"2016-01-25 00:32:25.000000000","message":"I\u0027m probably overstating the DepWarning in the comment as DepricationWarning will not bubble up without the user changing the default warnings filter in Python\u003e\u003d2.7.\n\nUltimately I don\u0027t think it\u0027s worth testing for _load for this one specific combination of versions, as the only time it will bubble up is Python\u003c2.7 and Setuptools 11.x, and I feel safer not attempting to use _load, as I can be fairly certain that on setuptools\u003c12 that load(false) will do the right thing, but if we order \"resolve()-\u003e_load()-\u003eload(False)\" I need to validate all versions of setuptools \u003c 11 do not have _load or if it has _load it does what we\u0027re expecting of it still.","commit_id":"d19459daa8616dd18fde016c2970ffc41ff4ccdd"}]}
