Open Stack

On 02/15/2013 10:51 AM, Julien Danjou wrote:
> On Thu, Feb 14 2013, Sandy Walsh wrote:
> 
>> So, which option is best?
>> 1. Drop support for Swift < 1.7.5 in CM?
>> 2. Solicit ideas for crafting an elegant way to make that code Hacking Compliant?
>> 3. Disable Hacking checks for this file?
> 
> 4. Fix/enhance hacking.py to handle such cases?
> 

I think that would fall under #3. But it's such a nasty chunk of code
trying to catch that situation would be difficult. Also, I want to keep
hacking.py the same as nova's, until it can get moved into Oslo. Don't
want to maintain a different version if possible.