1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Actually I don't like spaces for indentation at all. A tab character and a |
5 |
space character take the same number of bytes, so it takes two-to-eight times |
6 |
as much space per indentation to store the same indentation as a single tab |
7 |
character. On the average project that can add up to several kilobytes of |
8 |
difference. Furthermore, it completely _prevents_ collaborators from enjoying a |
9 |
bit of customization as to the amount of indentation. If I like my indentation |
10 |
to be two spaces, and you like yours to be four, then we can each set our text |
11 |
editors that way and continue to happily share code that uses tabs for indentation. |
12 |
|
13 |
I disagree with both PEP8 and Gentoo SOC styles on the matter. I would love it |
14 |
if someone could explain to me the actual benefit of using spaces over tabs. |
15 |
|
16 |
I'll reply to the rest of the equery refactorization thread in a different email. |
17 |
|
18 |
- -Michael |
19 |
|
20 |
Douglas Anderson wrote: |
21 |
|> [1] http://code.google.com/p/soc/wiki/PythonStyleGuide |
22 |
|> |
23 |
| |
24 |
| I'm with you there, I really like that style guide as well. We should |
25 |
| adopt it :) |
26 |
| |
27 |
| -Doug |
28 |
|
29 |
-----BEGIN PGP SIGNATURE----- |
30 |
Version: GnuPG v2.0.9 (GNU/Linux) |
31 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
32 |
|
33 |
iEYEARECAAYFAkk7COYACgkQzwtr5yY0JZyGFwCcCAI1oRKkfK0W1d5U5AQBQ4D8 |
34 |
fooAoIQS8sH+KRdT8e9TgJ4nXOYXKgae |
35 |
=71ob |
36 |
-----END PGP SIGNATURE----- |