c2c-oerpscenario team mailing list archive

["Tristan Hill \(credativ\)" <stan@xxxxxxxxxxxxx>]

Hi,

I have not found a way to trigger the bad line to run because of the
workflow mentioned above.

However, there would be an error if this line was run.  Please examine
the line:

move.write(cr, uid, [move.id], {'state': 'done'})

in stock/stock.py stock_picking.test_finished for the invalid arguments
it passes.

Thanks

** Changed in: openobject-addons
       Status: Incomplete => New

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/690583

Title:
  stock.picking.test_finished: write() takes at most 6 arguments (8 given)

Status in OpenObject Addons Modules:
  New

Bug description:
  While looking at stock/stock.py: stock_picking.test_finished I noticed the move.write(cr, uid, [move.id], {'state': 'done'}) would cause a "TypeError: write() takes at most 6 arguments (8 given)" exception if executed.  As stock_picking.test_finished is usually only executed after stock_picking.action_move by the workflow, which sets the moves to done, this line of code is not usually executed.

move.write({'state': 'done'}) would appear to be the correct line to use.  This is looking at current trunk, revision 4011.