Improve pylint score

Bug #822813 reported by Salvatore Orlando
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Invalid
Medium
Unassigned

Bug Description

pylint job on jenkins reveals 32 files have violations, for a staggering total of 734 violations!
Nova, which is a lot larger than Quantum, has 4720 violations.

Achieving a pylint score of 8/10 would be a good result.

Related branches

Changed in quantum:
importance: Undecided → Low
assignee: nobody → Salvatore Orlando (salvatore-orlando)
status: New → In Progress
milestone: none → diablo-integration-freeze
dan wendlandt (danwent)
Changed in quantum:
milestone: diablo-rbp → none
Revision history for this message
dan wendlandt (danwent) wrote :

This work got abandoned, which is really too bad. I doubt a patch would apply cleanly now, and I do have some concerns about replacing "Exception" with "QuantumException" (since this could change behavior), but I would like to look into keeping a lot of these changes. Perhaps I will get a beer and copy/paste these changes at some point :)

I think we will want to do a pylint/code coverage push early E-4 in prep for our proposal as a "core" project for "F".

Changed in quantum:
importance: Low → Medium
Revision history for this message
Salvatore Orlando (salvatore-orlando) wrote :

The associated branch is now unfortunately too old, which is really really bad as I spent several hours figuring out how to sort out tricky pylint issues :(

I am proposing to mark this bug as Invalid, but we really need to goto into Essex with better pylint scores.

Changed in quantum:
assignee: Salvatore Orlando (salvatore-orlando) → nobody
Revision history for this message
Maru Newby (maru) wrote :

Do we still care about pylint, or is a clean pep8 run sufficient?

Revision history for this message
dan wendlandt (danwent) wrote : Re: [Bug 822813] Re: Improve pylint score

good pylint score is better than worse, but given scarce dev resources, its
not a priority in my mind.

dan

On Tue, Apr 24, 2012 at 1:59 PM, Maru Newby <email address hidden> wrote:

> Do we still care about pylint, or is a clean pep8 run sufficient?
>
> --
> You received this bug notification because you are a member of Netstack
> Core Developers, which is subscribed to quantum.
> https://bugs.launchpad.net/bugs/822813
>
> Title:
> Improve pylint score
>
> Status in OpenStack Quantum (virtual network service):
> In Progress
>
> Bug description:
> pylint job on jenkins reveals 32 files have violations, for a staggering
> total of 734 violations!
> Nova, which is a lot larger than Quantum, has 4720 violations.
>
> Achieving a pylint score of 8/10 would be a good result.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/quantum/+bug/822813/+subscriptions
>

--
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Wendlandt
Nicira, Inc: www.nicira.com
twitter: danwendlandt
~~~~~~~~~~~~~~~~~~~~~~~~~~~

Revision history for this message
Maru Newby (maru) wrote :

Do we leave this bug in place then? Or 'Won't Fix'? I'm not even sure jenkins is running pylint against quantum anymore.

Changed in quantum:
status: In Progress → Confirmed
Revision history for this message
Gary Kotton (garyk) wrote :
Changed in quantum:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.