Merge lp://staging/~openerp-community/openerp-product-variant/fix-pep8-and-relative-import into lp://staging/~anybox/openerp-product-variant/7.0

LGTM

Code review ok with no tests.

But, if I run the flake8 in the branch (as described in http://pad.openerp.com/p/community-review), there are some errors : : https://cloud.theuret.net/public.php?service=files&t=325551f781f972b1eb5d088c259c07f5

Quentin: cannot access that file. I will run flake8 on the module entirely and commit this, I had only done this on __openerp__.py as asked by Nicolas Bessi.

A quick check with flake8 produces only one easily fixable style suggestion:
http://pastie.org/8336327

The space after the comma.

For all the other "problems" it's nagging about the 79 character limit.
Since no lines are longer than 100 characters this is a minimal discomfort imho and restructuring the code manually takes a long time.

Yes the long lines indicate a non-optimal writing. This is code that has been ported, not written from scratch.

Feel free to branch and commit (it's pushed to ~openerp-community team) and start cleaning up. Keep in mind that the larger the commit message the more time it takes to approve it.

Consider also that changing the indentation/line length will not necessarily produce cleaner code but can introduce errors in logic unless you are very careful or use automated tools.

Formatting tools (autopep8) turn the file from somewhat hard to read to impossible to read with the tons of auto-indentation it adds, I think to get a clean result you can only do it manually.

Niels,

I expected this message :)

It was just a remark (that's why I didn't reject the MP) because the title of the branch contains fix-pep8 so I said me maybe you don't run flake8 on your code.

So, for me, the code is good.

I just pushed another flake8 cleanup in our branch (most of us use a vim flake8 plugin, but we limited the line length to 100 instead of 80)

LGTM

The MP's target is an Anybox's branch. Is it normal?