s to
>> our pep8.
>>
>>
>>
>>
>>
>> *From:* Anastasia Kuznetsova [mailto:akuznets...@mirantis.com]
>> *Sent:* Wednesday, December 09, 2015 1:13 PM
>> *To:* OpenStack Development Mailing List (not for usage questions)
>> *Subject:* Re: [openstack-dev
sia Kuznetsova [mailto:akuznets...@mirantis.com
> <mailto:akuznets...@mirantis.com>]
> Sent: Wednesday, December 09, 2015 1:13 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [mistral] Improving Mistral pep8 rules files to
>
on adding these rules to our
pep8.
From: Anastasia Kuznetsova [mailto:akuznets...@mirantis.com]
Sent: Wednesday, December 09, 2015 1:13 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [mistral] Improving Mistral pep8 rules files to
match Mistral
t Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [mistral] Improving Mistral pep8 rules
> files to match Mistral guidelines
>
>
>
> Hi Moshe,
>
>
>
> Great idea!
>
>
>
> It is possible to prepare some additional code checks, for example y
Hi all,
Is it possible to add all / some of the special guidelines of Mistral (like
blank line before return, period at end of comment, ...) to our pep8 rules file?
This can save a lot of time for both committers and reviewers.
Thanks!
Hi Moshe,
Great idea!
It is possible to prepare some additional code checks, for example you can
take a look how it was done in Rally project [1].
Before starting such work in Mistral, I guess that we can describe our
addition code style rules in our official docs (somewhere in "Developer
Guide"
