Dirkjan Ochtman schrieb:
> On 05/04/2009 20:29, "Martin v. Löwis" wrote:
>> FYI: this is the list of hooks currently employed:
>> - pre: check whitespace
>> - post: mail python-checkins
>>          inform regular buildbot
>>          inform community buildbot
>>          trigger website rebuild if a PEP was modified
>>          (but then, whether or not the PEPs will be maintained
>>           in hg also needs to be decided)
> 
> All this is easy to do with Mercurial's hook system. One caveat is that 
> stuff (like whitespace) only gets checked at push time, not at commit 
> time (running commit hooks would have to be done on the client, but 
> since we don't sandbox hooks, they would be a liability to distribute by 
> default). People could still set them up locally for pre-commit if they 
> want, of course, but otherwise they may need some trickery to modify the 
> changesets they want to push.

When commits with bad whitespace changes are rejected on push, this is a
pretty good incentive to run the pre-commit hook next time, so that you
don't have to re-do all the commits in that batch :)

Georg


-- 
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.

_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to