[issue7730] ssl has bad coding style

djc added the comment: Thanks! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailma

[issue7730] ssl has bad coding style

Ezio Melotti added the comment: Ok, done in r77595 (trunk), r77596 (release26-maint), r77597 (py3k) and r77598 (release31-maint). -- assignee: -> ezio.melotti resolution: -> fixed stage: -> committed/rejected status: open -> closed versions: +Python 2.6, Python 3.1, Python 3.2

[issue7730] ssl has bad coding style

Martin v. Löwis added the comment: I think dropping the spaces after the function names is fine in this case; the module is inconsistent in this matter. -- nosy: +loewis status: pending -> open ___ Python tracker

[issue7730] ssl has bad coding style

Ezio Melotti added the comment: There should be no space between the name of the function and the '(' in both the cases. However the PEP 8 also says that "Consistency within one module or function is most important" and we usually avoid this kind of refactoring because they just make svn blam

[issue7730] ssl has bad coding style

Changes by djc : -- type: -> feature request ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue7730] ssl has bad coding style

New submission from djc : Sorry to be nitpicking here, but it kind of sticks out when you take your first look at ssl.py. While PEP 8 only talks about whitespace before the function call argument list parenthesis, I think this should also go for function definition. ssl has a lot of definition