| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 19/01/14 23:54, Alec Warner wrote: |
| 5 |
> I'm very against add a bunch of extra rules that have to be |
| 6 |
> enforced by hand. I want to make it easy to contribute, not more |
| 7 |
> difficult. If bob can run a tool that tells him all the things |
| 8 |
> that are wrong with his patch, that avoids us having like 1/3rd of |
| 9 |
> the conversations on list ;) |
| 10 |
Feel free to write a tool for this, or to contribute to any of the |
| 11 |
numerous linters and/or editor plug-ins. It would be much appreciated. |
| 12 |
|
| 13 |
As for the difficulty of PEP 257... I have higher hopes for Portage |
| 14 |
contributors than getting stuck at that. If I write a patch that makes |
| 15 |
most of the docstrings follow it, then they can infer 99% of the |
| 16 |
"extra rules" by just looking at the other functions and methods. If |
| 17 |
they fail to comply, we can just mention it. If the docstring |
| 18 |
formatting is the biggest issue with their patch, I doubt they'll have |
| 19 |
a hard time fixing it. |
| 20 |
- -- |
| 21 |
Alexander |
| 22 |
alexander@××××××.net |
| 23 |
http://plaimi.net/~alexander |
| 24 |
-----BEGIN PGP SIGNATURE----- |
| 25 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 26 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 27 |
|
| 28 |
iF4EAREIAAYFAlLcZPQACgkQRtClrXBQc7XizAD/Y/Gxc7N6VkgNFWRgP5lmQ84r |
| 29 |
UwSne2xaqJYphY9x1TcBAIRpjBHB580edLz/8zpT14lqhW3oOmeMz0pNMB8ssW5d |
| 30 |
=+zp5 |
| 31 |
-----END PGP SIGNATURE----- |
Archives