[Python-Dev] Avoiding whitespace conflicts
Georg Brandl
g.brandl at gmx.net
Sun Mar 20 19:14:20 CET 2011
On 20.03.2011 18:05, skip at pobox.com wrote:
>
> Ben> Ned Deily <nad at acm.org> writes:
> >> As a side note, if you are prone to accidentally adding extra
> >> whitespace (like I am), you can add the whitespace check hook into
> >> your local copy of Mercurial so that you will be warned about
> >> whitespace problems immediately when you commit things to your local
> >> repos rather than later when you try to push them up to the
> >> python.org repo.
>
> Ben> Even earlier that the attempt to commit, one can configure the text
> Ben> editor to show whitespace in order to be aware of it at the point
> Ben> where it's easiest to change:
>
> ...
>
> I wasn't aware that TABs were verboten in .rst files. If svn was configured
> to reject TABs I simply never stumbled on it with my edits. I did some
> searching but found nothing in the dev guide to suggest there were any
> restrictions on the whitespace in .rst files. Now that I know, it's not
> difficult to avoid.
I probably thought it would be obvious, since reST relies on structural
indentation just like Python. I've now added this in "Documenting Python".
cheers,
Georg
More information about the Python-Dev
mailing list