| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
Alignment is a PITA with hard tabs, so can we at least agree on what |
| 5 |
tab stop to use? I naïvely mentioned in DEVELOPING that it should be |
| 6 |
set to 4, because that's what every Python standard uses. But |
| 7 |
throughout the code it varies. |
| 8 |
|
| 9 |
There are plenty of examples of stuff that's aligned using tabs, see |
| 10 |
UseManager's init comment for an example. Notice how it is obviously |
| 11 |
formatted by somebody using 8 as their tab stop. People who have set |
| 12 |
their tab stop to the Python standard will just see an ugly mess. |
| 13 |
|
| 14 |
It's not a big issue, but if we can agree on a rule, I can add it to |
| 15 |
the DEVELOPING, and people can just change stuff that assumes a wrong |
| 16 |
tab stop. |
| 17 |
|
| 18 |
To avoid bikeshedding I just propose to set it to 4. Any objections? |
| 19 |
- -- |
| 20 |
Alexander |
| 21 |
bernalex@g.o |
| 22 |
https://secure.plaimi.net/~alexander |
| 23 |
-----BEGIN PGP SIGNATURE----- |
| 24 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 25 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 26 |
|
| 27 |
iF4EAREIAAYFAlMytCsACgkQRtClrXBQc7WYKwD+O8RBe5WJIDv6vmonPieJwiI/ |
| 28 |
AfJLP3ihJswJNaQo1UgA/iJKrhTZ2Qq2h6gEnYvhmuD6FBCmI2ynukk51iuzmi3E |
| 29 |
=BXE9 |
| 30 |
-----END PGP SIGNATURE----- |
Archives