Re: [Netstack] pep8

I've just figured out that, I already fixed all of those files at patch set3. Files are available to review. []'s Juliano Martinez On Saturday, June 16, 2012 at 3:35 PM, Juliano Martinez wrote: > I will start from the end to begin and will send commit after every two file. > > []'s > > Juli

Re: [Netstack] pep8

I will start from the end to begin and will send commit after every two file. []'s Juliano Martinez On Saturday, June 16, 2012 at 2:48 PM, Gary Kotton wrote: > Hi, > I can do some if you guys wish. > Thanks > Gary > > On 06/16/2012 07:54 PM, Juliano Martinez wrote: > > Sumit, > > > > Follo

Re: [Netstack] pep8

Hi, I can do some if you guys wish. Thanks Gary On 06/16/2012 07:54 PM, Juliano Martinez wrote: Sumit, Follow the list of files that need to be fixed: quantum/plugins/cisco/db/l2network_db.py quantum/plugins/cisco/db/l2network_models.py quantum/plugins/cisco/db/models.py quantum/plugins/cisco/

Re: [Netstack] pep8

FWIW, the python-keystoneclient project took the hit and has been migrating with the rapid velocity of PEP8, but in keystone itself we locked down to the 1.01 version for a while. The indentation on tests took the longest to get fully resolved in the client (did that work myself). Kind of a pai

Re: [Netstack] pep8

Sumit, Follow the list of files that need to be fixed: quantum/plugins/cisco/db/l2network_db.py quantum/plugins/cisco/db/l2network_models.py quantum/plugins/cisco/db/models.py quantum/plugins/cisco/db/nexus_db.py quantum/plugins/cisco/db/nexus_models.py quantum/plugins/cisco/db/services_db.py qu

Re: [Netstack] pep8

Yes, pep8 seems to be revving their versions quite frequently :) The current strategy, discussed on the list, is that we'll roll with the punches and just fix the new issues as pep8 flags them. This encourages us to keep improving the style-quality of the code base. In this case, pep8 started fl