This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients belopolsky, brett.cannon, dmalcolm, eric.araujo, mark.dickinson, pitrou
Date 2010-08-13.22:47:12
SpamBayes Score 0.0642141
Marked as misclassified No
Message-id <>
I wonder how to have sane code reuse between patchcheck and Mercurial hooks. Mark seems to have started seconding Dirkjan with hooks, see e.g., so I wonder if we’re going to use only hooks (pro: they will be invoked on every push, whereas patchcheck is opt-in, con: they would require that contributors clone the hooks repo and set them up) or still maintain patchcheck, which has pros (no setup, does not require a VCS) and cons (not automatic, not widely used, whereas hooks can be part of the new python-dev policy).
Date User Action Args
2010-08-13 22:47:14eric.araujosetrecipients: + eric.araujo, brett.cannon, mark.dickinson, belopolsky, pitrou, dmalcolm
2010-08-13 22:47:14eric.araujosetmessageid: <>
2010-08-13 22:47:13eric.araujolinkissue8912 messages
2010-08-13 22:47:12eric.araujocreate