disable flake8 on sphinx config. file and in recorded test data files
Fix flake8 warnings and errors
Activate flake8 tests
reduce long lines to 79 chars
remove noqa at end of lines
Add notice explaining that data files used by test ignore pep8
:retab data files used in tests, remove a unused import
Run autopep8 -a -i on data files used in tests

Lines length cannot be corrected though
pep8 sphinx config file
Merge pull request #8 from guewen/7.0-pep8

Fix flake8 warnings and errors
When a sales order is canceled, when one uses the 'New Copy from Quotation' button,
the binding are moved from the old (canceled) order to the new one, so the
synchronizations now happen on the new order.
Correct Python trap with string formatting

It would try to convert the items of a tuple to arguments of the
string formatting, and would raise the following error:

TypeError: not all arguments converted during string formatting
Prevent Binder to bind when external or binding id is missing
When Magento returns no ID when we create an invoice, try to get the invoice's ID otherwise, just consider the job as done, but do not bind with a None ID
It does not implement the import of bundle products, but only add a hook
ConnectorUnit to implement it.
It adds the import of the dependencies of the bundles though.

The PHP part of the connector has been updated in order to add the
bundle information, so it needs to be updated on the Magento instance.

Original MP on Launchpad:
https://code.launchpad.net/~camptocamp/openerp-connector-magento/7.0-next-release-bundle-import-base/+merge/223716
Add a 'to date' boundary to batch jobs

Currently, the batch jobs have a 'from date' boundary only, which is
incremented each time a new batch job is created.

This may cause an issue when many batch jobs are created and don't have
the time to be processed: the same records will be imported several
times.

Example with 4 batch jobs with an interval of 10 minutes (the 30 seconds
difference is a buffer because Magento may commit a new record 'created_at' with a
delay) :

  Batch job 1 from 2014-07-17 10:00:00
  Batch job 2 from 2014-07-17 10:09:30
  Batch job 3 from 2014-07-17 10:19:00
  Batch job 4 from 2014-07-17 10:28:30

A product A is modified on Magento at 2014-07-17 10:25:00
None of the batch job could been executed so far (maybe an interruption
or a high load).  When the batch job 1 will be processed, it will see
that product A has been modified later than 10:00 so it creates an
import job. Turn of batch job 2, it sees the product modified after
10:10, creates an import job... and so on.

This patch adds a 'to' boundary so the batch jobs become:

  Batch job 1 from 2014-07-17 10:00:00 to 2014-07-17 10:10:00
  Batch job 2 from 2014-07-17 10:09:30 to 2014-07-17 10:19:30
  Batch job 3 from 2014-07-17 10:19:00 to 2014-07-17 10:19:00
  Batch job 4 from 2014-07-17 10:28:30 to 2014-07-17 10:28:30

Thus, in the same situation than before, only the batch job 3 would see
the record.
Begin work on sales orders cancellation
makes the cancel exporter more generic to possibly export all the states
magentoerpconnect_order_comment should use the adapter of magento.sale.order

instead of a new adapter on magento.sale.comment
Export the new status when we create a copy from a canceled order