[trunk] [7.0] stock.check_assign ignores decimal precision

[Holger Brunn (Therp)]

To reproduce:

Create a manufactured product with a bom that includes a quantity which can't be represented as a float proper, i.e. 0.033. Create a production order for this product and confirm the production.

Now have a look on the moves created: You'll find a quantity of 0.033000000000000002 which will cause all sorts of trouble afterwards.

Analysis:

In
http://bazaar.launchpad.net/~openerp/openobject-addons/trunk/view/head:/stock/stock.py#L2189
we update the database directly, thereby circumventing the decimal precision adjustments for product_qty and product_uos_qty. I think changing this to
move.write({'location_id': r[1], 'product_qty': r[0], 'product_uos_qty': product_uos_qty})
already fixes the problem.

[Holger Brunn (Therp) (hbrunn)]

To reproduce, you need python2.6 in most cases