openerp-india team mailing list archive

["Amit Parik \(OpenERP\)" <amp@xxxxxxxxxxx>]

Hello Greame,

I also think that we have to use 0.00 instead of 0 at condition. But
currently I didn't find the proper use case which is provide the problem
by using 0  instead of 0.00. If you have a proper use case which will
see the problem occurs by using 0, So would you please provide it.

Currently I am again setting this as a "New"

Thanks and waiting for your reply!

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

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/938359

Title:
  [6.1] Stock action_consume function

Status in OpenERP Addons (modules):
  New

Bug description:
  There is an annoying bug in this function, but also I think it is
  written wrong.  I don't know if correcting it will fix the bug but it
  should be fixed anyway.

  Basically quantity is a float field, however all the defaults in this
  function create ints.  What I am finding is that whenever a move is
  created I am getting an extra move created for 0.000 which I assume is
  rounding and float comparison.  The old roundup argument which would
  be a duplicate - so I am not reporting that particular bug again still
  unresolved after over a year.  But rather I forgot about that bug and
  was looking at the function and it didn't quite seem right.

  This purely relates to the action_consume function - just look at and
  you will see.  All zero values declared as ints not floats, despite
  all quantity fields I can think of in OpenERP being floats.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/938359/+subscriptions