Sun, 17 May 2015 21:15:45 -0400 run-tests: drop subprocess _cleanup monkeypatch
Augie Fackler <augie@google.com> [Sun, 17 May 2015 21:15:45 -0400] rev 25156
run-tests: drop subprocess _cleanup monkeypatch This was working around a defect in subprocess in Python 2.5, which we no longer need to worry about.
Sun, 17 May 2015 21:15:04 -0400 run-tests: drop wifexited polyfill
Augie Fackler <augie@google.com> [Sun, 17 May 2015 21:15:04 -0400] rev 25155
run-tests: drop wifexited polyfill os.WIFEXITED exists as of python 2.6 for me, so we no longer need this polyfill.
Mon, 18 May 2015 11:43:10 -0400 test-import: update for no-execbit platforms with 1ef96a3b8b89
Matt Harbison <matt_harbison@yahoo.com> [Mon, 18 May 2015 11:43:10 -0400] rev 25154
test-import: update for no-execbit platforms with 1ef96a3b8b89
Mon, 18 May 2015 11:37:29 -0400 test-treemanifest: add globs for Windows
Matt Harbison <matt_harbison@yahoo.com> [Mon, 18 May 2015 11:37:29 -0400] rev 25153
test-treemanifest: add globs for Windows
Sat, 16 May 2015 14:37:24 -0400 util: drop any() and all() polyfills
Augie Fackler <augie@google.com> [Sat, 16 May 2015 14:37:24 -0400] rev 25152
util: drop any() and all() polyfills
Sat, 16 May 2015 14:34:19 -0400 cleanup: use __builtins__.all instead of util.all
Augie Fackler <augie@google.com> [Sat, 16 May 2015 14:34:19 -0400] rev 25151
cleanup: use __builtins__.all instead of util.all
Sat, 16 May 2015 14:34:04 -0400 check-code: un-ban __builtins__.all now that we're on 2.6
Augie Fackler <augie@google.com> [Sat, 16 May 2015 14:34:04 -0400] rev 25150
check-code: un-ban __builtins__.all now that we're on 2.6
Sat, 16 May 2015 14:30:07 -0400 cleanup: use __builtins__.any instead of util.any
Augie Fackler <augie@google.com> [Sat, 16 May 2015 14:30:07 -0400] rev 25149
cleanup: use __builtins__.any instead of util.any any() is available in all Python versions we support now.
Sat, 16 May 2015 14:31:03 -0400 check-code: un-ban any() now that we're on 2.6
Augie Fackler <augie@google.com> [Sat, 16 May 2015 14:31:03 -0400] rev 25148
check-code: un-ban any() now that we're on 2.6
Sun, 17 May 2015 18:11:02 -0700 walkchangerevs: replace try/except with 'next'
Pierre-Yves David <pierre-yves.david@fb.com> [Sun, 17 May 2015 18:11:02 -0700] rev 25147
walkchangerevs: replace try/except with 'next' Again, this make the code clearer.
Sun, 17 May 2015 18:06:09 -0700 generatorset: use 'next()' to simplify the code
Pierre-Yves David <pierre-yves.david@fb.com> [Sun, 17 May 2015 18:06:09 -0700] rev 25146
generatorset: use 'next()' to simplify the code The 'next()' built-in accept a default value. This remove the needs to check if self non-empty before returning a value.
Sun, 17 May 2015 18:00:38 -0700 revset: use 'next()' to detect end of iteration in 'last'
Pierre-Yves David <pierre-yves.david@fb.com> [Sun, 17 May 2015 18:00:38 -0700] rev 25145
revset: use 'next()' to detect end of iteration in 'last' The 'next()' built-in can return a default value, allow to get rid of the confusing try/except code flow.
Sun, 17 May 2015 17:58:39 -0700 revset: use 'next()' to detect end of iteration in 'limit'
Pierre-Yves David <pierre-yves.david@fb.com> [Sun, 17 May 2015 17:58:39 -0700] rev 25144
revset: use 'next()' to detect end of iteration in 'limit' The 'next()' built-in can return a default value, allow to get rid of the confusing try/except code flow.
Sun, 17 May 2015 17:54:58 -0700 _revancestors: use 'next' to remove the verbose try except clauses
Pierre-Yves David <pierre-yves.david@fb.com> [Sun, 17 May 2015 17:54:58 -0700] rev 25143
_revancestors: use 'next' to remove the verbose try except clauses The 'next()' built-in can return a default value, making the final iteration case simpler and clearer.
Sun, 17 May 2015 17:47:42 -0700 check-code: lift the ban on 'next()'
Pierre-Yves David <pierre-yves.david@fb.com> [Sun, 17 May 2015 17:47:42 -0700] rev 25142
check-code: lift the ban on 'next()' 'next' is supported by Python2.6 the new lowest version supported by Mercurial.
(0) -10000 -3000 -1000 -300 -100 -15 +15 +100 +300 +1000 +3000 +10000 tip