Am 2013-07-16 12:54, schrieb Cédric Krier: >> nitpicking: >> > >> > uom should be "unit of measurement". >> > >> > "measure" is something different than "measurement", see [1], I would >> > associate it with set-theory and calculus. > Yes probably I'm confuse with the french. > But it doesn't seem to be incorrect: > https://en.wikipedia.org/wiki/Unit_of_measure which directly refers to "Unit of measrurement" ;-) >> > "quantity" seems to be the correct term (according to wikipedia). Thus I >> > propose: >> > >> > class Quantity(namedtuple('Quantity', ['amount', 'uom'])): > For me, the definition is not so clear about what is the quantity. Is it > the couple or the part in front of the unit? > > Anyway, I'm in favor of consistency and as quantity is already used in > many places. It will be confusing to introduce a new Object with the > same name for something different. > > So for me, this new object must be named to describe the result of a > measurement (and not generate collisions). Clearly, the scope of this thread is not the instance method on Uom any more. I'm not sure about the use of "quantity" in tryton. At a glance it seems it is always used in conjunction with "uom".
IMHO it would make sense to introduce such a class into tryton iff it is used consistently in the base modules to replace all instances of dimensionful numbers (which seems like a huge task), so some "purging" of current use of quantity and uom would have to happen anyway. Having "Measure"- or "Measurement"-instances as stock.move- or bom-quantities would surely look strange, and it somehow pollutes the namespace if one was to really deal with "Measurements" (e.g. in quality-assurance). mfg Robert
