Guido kindly updated PEP-257 for us[1]. So now the hacking guide content
accurately matches PEP-257 (no extra line required at the end of a multi-line
docstring).
This alone should resolve the patch and comments that initiated this discussion.
With regards to automating the checks and gates, we
On Thu, Feb 27, 2014 at 9:29 AM, Ben Nemec wrote:
> On 2014-02-27 08:05, Ziad Sawalha wrote:
>>
>> On Feb 26, 2014, at 11:47 AM, Joe Gordon wrote:
>>
>>> On Wed, Feb 26, 2014 at 9:05 AM, David Ripton wrote:
On 02/26/2014 11:40 AM, Joe Gordon wrote:
> This is missing the point
On Thu, Feb 27, 2014 at 6:05 AM, Ziad Sawalha
wrote:
>
> On Feb 26, 2014, at 11:47 AM, Joe Gordon wrote:
>
>> On Wed, Feb 26, 2014 at 9:05 AM, David Ripton wrote:
>>> On 02/26/2014 11:40 AM, Joe Gordon wrote:
>>>
This is missing the point about manually enforcing style. If you pass
the
On 2014-02-27 08:05, Ziad Sawalha wrote:
On Feb 26, 2014, at 11:47 AM, Joe Gordon wrote:
On Wed, Feb 26, 2014 at 9:05 AM, David Ripton
wrote:
On 02/26/2014 11:40 AM, Joe Gordon wrote:
This is missing the point about manually enforcing style. If you
pass
the 'pep8' job there is no need to
On Feb 26, 2014, at 11:47 AM, Joe Gordon wrote:
> On Wed, Feb 26, 2014 at 9:05 AM, David Ripton wrote:
>> On 02/26/2014 11:40 AM, Joe Gordon wrote:
>>
>>> This is missing the point about manually enforcing style. If you pass
>>> the 'pep8' job there is no need to change any style.
>>
>>
>> I
On Wed, Feb 26, 2014 at 9:05 AM, David Ripton wrote:
> On 02/26/2014 11:40 AM, Joe Gordon wrote:
>
>> This is missing the point about manually enforcing style. If you pass
>> the 'pep8' job there is no need to change any style.
>
>
> In a perfect world, yes.
While there are exceptions to this, t
On 02/26/2014 11:40 AM, Joe Gordon wrote:
This is missing the point about manually enforcing style. If you pass
the 'pep8' job there is no need to change any style.
In a perfect world, yes.
In the real world, there are several things in PEP8 or our project
guidelines that the tools don't enf
On Wed, Feb 26, 2014 at 6:39 AM, Ziad Sawalha
wrote:
>
> On Feb 25, 2014, at 5:18 PM, Kevin L. Mitchell
> wrote:
>
>> On Tue, 2014-02-25 at 00:56 +, Ziad Sawalha wrote:
>>> Seeking some clarification on the OpenStack hacking guidelines for
>>> multi-string docstrings.
>>>
>>>
>>> Q: In OpenS
On Feb 25, 2014, at 5:18 PM, Kevin L. Mitchell
wrote:
> On Tue, 2014-02-25 at 00:56 +, Ziad Sawalha wrote:
>> Seeking some clarification on the OpenStack hacking guidelines for
>> multi-string docstrings.
>>
>>
>> Q: In OpenStack projects, is a blank line before the triple closing
>> quo
On Feb 25, 2014, at 4:08 PM, Joe Gordon wrote:
> On Mon, Feb 24, 2014 at 4:56 PM, Ziad Sawalha
> wrote:
>> Seeking some clarification on the OpenStack hacking guidelines for
>> multi-string docstrings.
>>
>> Q: In OpenStack projects, is a blank line before the triple closing quotes
>> recommen
On Tue, 2014-02-25 at 00:56 +, Ziad Sawalha wrote:
> Seeking some clarification on the OpenStack hacking guidelines for
> multi-string docstrings.
>
>
> Q: In OpenStack projects, is a blank line before the triple closing
> quotes recommended (and therefore optional - this is what PEP-257
> s
On Mon, Feb 24, 2014 at 4:56 PM, Ziad Sawalha
wrote:
> Seeking some clarification on the OpenStack hacking guidelines for
> multi-string docstrings.
>
> Q: In OpenStack projects, is a blank line before the triple closing quotes
> recommended (and therefore optional - this is what PEP-257 seems to
Seeking some clarification on the OpenStack hacking guidelines for multi-string
docstrings.
Q: In OpenStack projects, is a blank line before the triple closing quotes
recommended (and therefore optional - this is what PEP-257 seems to suggest),
required, or explicitly rejected (which could be o
13 matches
Mail list logo
