Skip to content

Conversation

ncoghlan
Copy link
Contributor

Additional changes needed to backport:

  • dropped legacy SVN support from patchcheck
  • use subprocess.PIPE to silence expected error output
  • don't try to use subprocess.Popen as a context manager
  • don't try to pass a keyword argument to str.split()

(cherry picked from commit 482f7a2)

Additional changes needed to backport:

- dropped legacy SVN support from patchcheck
- use subprocess.PIPE to silence expected error output
- don't try to use subprocess.Popen as a context manager
- don't try to pass a keyword argument to str.split()

(cherry picked from commit 482f7a2)
@ncoghlan
Copy link
Contributor Author

@brettcannon, @benjaminp I already merged the 3.x backports to make make patchcheck git PR-branch friendly, but there were a few more adjustments needed to get it to play nice with 2.7, so I'd like someone else to take a quick look before I land it.

@ncoghlan
Copy link
Contributor Author

On second thoughts, having a discrepancy in behaviour between 2.7 and the other active branches concerns me more than any potential glitches in the backport, so I've gone ahead and merged this one as well.

@ncoghlan ncoghlan deleted the backport-482f7a2-2.7 branch March 12, 2017 09:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants