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

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

Re: PEP8 and 4 spaces

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

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: PEP8 and 4 spaces Toby Shepard <tshepard@rcsreg.com> - 2014-07-03 11:02 -0700

#73912 — Re: PEP8 and 4 spaces

On 07/03/2014 10:46 AM, Tim Chase wrote:
>> Any evidence out there that this part of PEP8 is becoming
>> more optional or even obsolete, as I've heard others
>> say about the 80 char line length?
>>
>> Just need ammo for when the hammer of code
>> unification comes down.
>
> I'm not sure you'll get a whole lot of "PEP8 is optional or
> obsolete", though some may protest the 80-char suggestion.
>
> While I prefer tabs for similar reasons you present (I can set them
> to display at whatever width is comfortable), I have Vim configured
> to expand tabs into spaces so that my code conforms to standards.
>
> If you're really picky about it, just create hooks in your VCS (you
> ARE using revision control, right?) that turn
> $STANDARD_NUMBER_OF_SPACES into a tabs at checkout, and then revert
> tabs back to that number of spaces pre-commit.  For git, this SO
> post covers it:
>
> http://stackoverflow.com/questions/2316677/can-git-automatically-switch-between-spaces-and-tabs
>

Very interesting.  Yes, we're using Git.  Thanks for the suggestion.

Tobiah

[toc] | [standalone]

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

csiph-web