| 1 |
On Sun, Jan 19, 2014 at 2:45 PM, Alexander Berntsen <alexander@××××××.net>wrote: |
| 2 |
|
| 3 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 4 |
> Hash: SHA256 |
| 5 |
> |
| 6 |
> On 19/01/14 22:22, Sebastian Luther wrote: |
| 7 |
> > The usual doc string style used in portage is: |
| 8 |
> > |
| 9 |
> > """ text """ |
| 10 |
> > |
| 11 |
> > Please use that for new functions. Also make sure you don't use |
| 12 |
> > spaces to indent the last """. |
| 13 |
> > |
| 14 |
> As mentioned by Mike in another thread, we should use PEP 257[0]. I |
| 15 |
> will convert old code to conform to this... sometime... soon... (I |
| 16 |
> promise!) |
| 17 |
> |
| 18 |
> So if new patches could just do that right away, that would be neat. |
| 19 |
> |
| 20 |
|
| 21 |
Does pylint or pyflakes point out if you mess it up? |
| 22 |
|
| 23 |
Automation for the win. |
| 24 |
|
| 25 |
-A |
| 26 |
|
| 27 |
|
| 28 |
> |
| 29 |
> [0] <http://www.python.org/dev/peps/pep-0257/> |
| 30 |
> - -- |
| 31 |
> Alexander |
| 32 |
> alexander@××××××.net |
| 33 |
> http://plaimi.net/~alexander |
| 34 |
> -----BEGIN PGP SIGNATURE----- |
| 35 |
> Version: GnuPG v2.0.22 (GNU/Linux) |
| 36 |
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 37 |
> |
| 38 |
> iF4EAREIAAYFAlLcVaAACgkQRtClrXBQc7XjTwD/UsCQo+SJdiCX/QsMC8jFDPic |
| 39 |
> k0jEAN6DA5xML6/nJYQA/36FszMfVMZ/vzg5VF9FS6BDWwGm/Qy2whyqLiF3FOrX |
| 40 |
> =+5Yy |
| 41 |
> -----END PGP SIGNATURE----- |
| 42 |
> |
| 43 |
> |
Archives