A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2011-July/112380.html below:

[Python-Dev] [Python-checkins] peps: Restore whitespace characters lost via email transmission.

[Python-Dev] [Python-checkins] peps: Restore whitespace characters lost via email transmission.Georg Brandl g.brandl at gmx.net
Wed Jul 20 21:10:01 CEST 2011
On 07/20/11 17:05, Éric Araujo wrote:
> Le 20/07/2011 16:40, P.J. Eby a écrit :
>> PEP 12 prescribes four-space indents for PEPs, actually, wherever it
>> mentions an specific indentation depth.
> 
> Ah, thanks.  I see in my docutils docs that David Goodger used three and
> four-space indents (three for indenting the body of a directive, four
> for other cases).
> 
>> (I'm a bit surprised that three-space indents are mandated for
>> anything involving documenting Python in reST, though, since that
>> would mean you'd also have to indent your code samples by three
>> spaces, or else have an editor that supports two different tab widths.)
> 
> I don’t remember this being a pain.  Maybe it’s because the reST I tend
> to edit has much more reST indents than Python code example indents, so
> I don’t mind typing <Tab><Space>.

Also, chances are that you've tried out your sample code (!) and thus copy
it from a Python file anyway.

Georg

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4