Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #73908 > unrolled thread

PEP8 and 4 spaces

Back to article view | Back to comp.lang.python

Contents

  PEP8 and 4 spaces Tobiah <tshepard@rcsreg.com> - 2014-07-03 10:31 -0700
    Re: PEP8 and 4 spaces Roy Smith <roy@panix.com> - 2014-07-03 13:46 -0400
    Re: PEP8 and 4 spaces Grant Edwards <invalid@invalid.invalid> - 2014-07-03 19:02 +0000
      Re: PEP8 and 4 spaces Tim Chase <python.list@tim.thechases.com> - 2014-07-03 14:40 -0500
        Re: PEP8 and 4 spaces Tobiah <toby@tobiah.org> - 2014-07-03 14:23 -0700
          Re: PEP8 and 4 spaces Emile van Sebille <emile@fenx.com> - 2014-07-03 16:15 -0700
            Re: PEP8 and 4 spaces Grant Edwards <invalid@invalid.invalid> - 2014-07-04 14:28 +0000
              Re: PEP8 and 4 spaces Marko Rauhamaa <marko@pacujo.net> - 2014-07-04 17:54 +0300
                Re: PEP8 and 4 spaces Chris Angelico <rosuav@gmail.com> - 2014-07-05 00:58 +1000
                Re: PEP8 and 4 spaces Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-04 16:00 +0100
                  Re: PEP8 and 4 spaces Marko Rauhamaa <marko@pacujo.net> - 2014-07-04 18:12 +0300
                Re: PEP8 and 4 spaces Simon Ward <simon+python@bleah.co.uk> - 2014-07-04 19:52 +0100
                Re: PEP8 and 4 spaces Michael Torrie <torriem@gmail.com> - 2014-07-05 16:03 -0600
                Re: PEP8 and 4 spaces Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-05 23:50 +0100
              Re: PEP8 and 4 spaces Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-04 15:57 +0100
              Re: PEP8 and 4 spaces Emile van Sebille <emile@fenx.com> - 2014-07-04 08:57 -0700
              Re: PEP8 and 4 spaces Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-04 17:06 +0100
                Re: PEP8 and 4 spaces Maciej Dziardziel <fiedzia@gmail.com> - 2014-07-04 09:19 -0700
                  Re: PEP8 and 4 spaces Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-07-04 16:56 +0000
      Re: PEP8 and 4 spaces Tobiah <toby@tobiah.org> - 2014-07-03 14:28 -0700
    Re: PEP8 and 4 spaces Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-07-04 01:02 +0000
      Re: PEP8 and 4 spaces Chris Angelico <rosuav@gmail.com> - 2014-07-04 11:19 +1000
      Re: PEP8 and 4 spaces Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-07-04 18:35 +1200
        Re: PEP8 and 4 spaces wxjmfauth@gmail.com - 2014-07-04 01:47 -0700
          Re: PEP8 and 4 spaces Marko Rauhamaa <marko@pacujo.net> - 2014-07-04 12:21 +0300
            Re: PEP8 and 4 spaces wxjmfauth@gmail.com - 2014-07-04 03:10 -0700
        Re: PEP8 and 4 spaces Roy Smith <roy@panix.com> - 2014-07-04 09:47 -0400
          Re: PEP8 and 4 spaces Mihamina Rakotomandimby <mihamina.rakotomandimby@rktmb.org> - 2014-07-04 16:59 +0300
          Re: PEP8 and 4 spaces Mark Lawrence <breamoreboy@yahoo.co.uk> - 2014-07-04 16:12 +0100
          Re: PEP8 and 4 spaces George Silva <georger.silva@gmail.com> - 2014-07-04 12:14 -0300
            Re: PEP8 and 4 spaces Roy Smith <roy@panix.com> - 2014-07-04 12:31 -0400
              Re: PEP8 and 4 spaces George Silva <georger.silva@gmail.com> - 2014-07-04 13:37 -0300
          Re: PEP8 and 4 spaces Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-07-05 11:14 +1200
    Re: PEP8 and 4 spaces Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-04 19:00 -0700
      Re: PEP8 and 4 spaces Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-04 19:47 -0700
        Re: PEP8 and 4 spaces Chris Angelico <rosuav@gmail.com> - 2014-07-05 13:03 +1000
        Re: PEP8 and 4 spaces Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-07-05 20:57 +1200
          Re: PEP8 and 4 spaces alister <alister.nospam.ware@ntlworld.com> - 2014-07-05 09:48 +0000
        OT: Flashlights [was Re: PEP8 and 4 spaces] Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-07-05 10:15 +0000
          Re: OT: Flashlights [was Re: PEP8 and 4 spaces] Rick Johnson <rantingrickjohnson@gmail.com> - 2014-07-06 08:41 -0700
            Re: OT: Flashlights [was Re: PEP8 and 4 spaces] Chris Angelico <rosuav@gmail.com> - 2014-07-07 08:25 +1000
      Re: PEP8 and 4 spaces Ian Kelly <ian.g.kelly@gmail.com> - 2014-07-05 12:57 -0600
        Re: PEP8 and 4 spaces Roy Smith <roy@panix.com> - 2014-07-05 15:07 -0400
      Re: PEP8 and 4 spaces Robert Kern <robert.kern@gmail.com> - 2014-07-05 21:07 +0100
      Re: PEP8 and 4 spaces Chris Angelico <rosuav@gmail.com> - 2014-07-06 09:27 +1000
        Re: PEP8 and 4 spaces Dan Sommers <dan@tombstonezero.net> - 2014-07-06 01:18 +0000
          Re: PEP8 and 4 spaces Chris Angelico <rosuav@gmail.com> - 2014-07-06 11:28 +1000

Page 3 of 3 — ← Prev page 1 2 [3]

#74060 — Re: OT: Flashlights [was Re: PEP8 and 4 spaces]

On Mon, Jul 7, 2014 at 1:41 AM, Rick Johnson
<rantingrickjohnson@gmail.com> wrote:
> Well Steven all i can hope is that one day you and i will be
> working on a project together, and you will ask me for a
> "touch", and when i return with a petrol soaked rag burning
> on the end of twig and proceed to light your hair on fire,
> hopefully at that moment, you will THEN gain a healthy respect
> for logical naming conventions!

Let's reverse that. Suppose you're the one who is asking for something
to illuminate your task - what item will you request? Remember, the
person who provides it will be exactly what you're suggesting of
yourself - a literal-minded genie.

http://tvtropes.org/pmwiki/pmwiki.php/Main/LiteralGenie
http://tvtropes.org/pmwiki/pmwiki.php/Main/JackassGenie

ChrisA

[toc] | [prev] | [next] | [standalone]

#73995

On Fri, Jul 4, 2014 at 8:00 PM, Rick Johnson
<rantingrickjohnson@gmail.com> wrote:
> Strangly, I rather fancy the idea of using tabs in code,,,
> which allow each viewer to view the code in his or her level
> of indention,,, however, i cannot justify using a tab as a
> replacement for a space. Tabs should be used for "tabular"
> data (aka: speadsheets), and since code is NOT tabular data,
> we would be wise to use the space char for indention.

I find it a little curious that nobody ever seems to advocate the use
of vertical tabs instead of repeated newlines. It should offer the
same benefit as horizontal tabs, namely that one could then
independently configure one's editor to separate adjacent code
elements with the desired number of blank lines. But I suppose that
nobody finds that useful enough to bother with in the vertical case.

[toc] | [prev] | [next] | [standalone]

#73996

In article <mailman.11525.1404586681.18130.python-list@python.org>,
 Ian Kelly <ian.g.kelly@gmail.com> wrote:

> On Fri, Jul 4, 2014 at 8:00 PM, Rick Johnson
> <rantingrickjohnson@gmail.com> wrote:
> > Strangly, I rather fancy the idea of using tabs in code,,,
> > which allow each viewer to view the code in his or her level
> > of indention,,, however, i cannot justify using a tab as a
> > replacement for a space. Tabs should be used for "tabular"
> > data (aka: speadsheets), and since code is NOT tabular data,
> > we would be wise to use the space char for indention.
> 
> I find it a little curious that nobody ever seems to advocate the use
> of vertical tabs instead of repeated newlines. It should offer the
> same benefit as horizontal tabs, namely that one could then
> independently configure one's editor to separate adjacent code
> elements with the desired number of blank lines. But I suppose that
> nobody finds that useful enough to bother with in the vertical case.

Personally, I'm holding out for U+00A0 being a valid character in an 
identifier.  Intercourse this underscore stuff.

[toc] | [prev] | [next] | [standalone]

#73997

On 2014-07-05 19:57, Ian Kelly wrote:
> On Fri, Jul 4, 2014 at 8:00 PM, Rick Johnson
> <rantingrickjohnson@gmail.com> wrote:
>> Strangly, I rather fancy the idea of using tabs in code,,,
>> which allow each viewer to view the code in his or her level
>> of indention,,, however, i cannot justify using a tab as a
>> replacement for a space. Tabs should be used for "tabular"
>> data (aka: speadsheets), and since code is NOT tabular data,
>> we would be wise to use the space char for indention.
>
> I find it a little curious that nobody ever seems to advocate the use
> of vertical tabs instead of repeated newlines. It should offer the
> same benefit as horizontal tabs, namely that one could then
> independently configure one's editor to separate adjacent code
> elements with the desired number of blank lines. But I suppose that
> nobody finds that useful enough to bother with in the vertical case.

I do see the occasional person using form feeds to separate sections of code.

-- 
Robert Kern

"I have come to believe that the whole world is an enigma, a harmless enigma
  that is made terrible by our own mad attempt to interpret it as though it had
  an underlying truth."
   -- Umberto Eco

[toc] | [prev] | [next] | [standalone]

#74000

On Sun, Jul 6, 2014 at 4:57 AM, Ian Kelly <ian.g.kelly@gmail.com> wrote:
> I find it a little curious that nobody ever seems to advocate the use
> of vertical tabs instead of repeated newlines. It should offer the
> same benefit as horizontal tabs, namely that one could then
> independently configure one's editor to separate adjacent code
> elements with the desired number of blank lines. But I suppose that
> nobody finds that useful enough to bother with in the vertical case.

How often do you ever have multiple consecutive blank lines? My
newlines are either single (line end) or in pairs (one blank line),
and I don't remember having anything else (at least, not
intentionally). Greater separation than a blank line is provided by
comments, not more whitespace.

ChrisA

[toc] | [prev] | [next] | [standalone]

#74001

On Sun, 06 Jul 2014 09:27:59 +1000, Chris Angelico wrote:

> How often do you ever have multiple consecutive blank lines? My
> newlines are either single (line end) or in pairs (one blank line),
> and I don't remember having anything else (at least, not
> intentionally). Greater separation than a blank line is provided by
> comments, not more whitespace.
> 
> ChrisA

http://legacy.python.org/dev/peps/pep-0008/#id15 says:  "Separate top-level
function and class definitions with two blank lines."

With docstrings occurring inside function definitions, this happens quite a
bit.

Dan

[toc] | [prev] | [next] | [standalone]

#74002

On Sun, Jul 6, 2014 at 11:18 AM, Dan Sommers <dan@tombstonezero.net> wrote:
> On Sun, 06 Jul 2014 09:27:59 +1000, Chris Angelico wrote:
>
>> How often do you ever have multiple consecutive blank lines? My
>> newlines are either single (line end) or in pairs (one blank line),
>> and I don't remember having anything else (at least, not
>> intentionally). Greater separation than a blank line is provided by
>> comments, not more whitespace.
>>
>> ChrisA
>
> http://legacy.python.org/dev/peps/pep-0008/#id15 says:  "Separate top-level
> function and class definitions with two blank lines."
>
> With docstrings occurring inside function definitions, this happens quite a
> bit.

Ah, okay. Still, it's not something that scales up much, the way
horizontal whitespace does. You go to 2 blanks, and extras (sparingly)
between groups, but it's not like indentation, where nesting naturally
requires progressively more space. If you're nesting groups of
functions like that, you probably should be using something other than
whitespace (maybe separate files?).

ChrisA

[toc] | [prev] | [standalone]

Page 3 of 3 — ← Prev page 1 2 [3]

Back to top | Article view | comp.lang.python

csiph-web