[Erp5-report] r34053 kazuhiko - /erp5/trunk/products/ERP5/Document/FloatEquivalenceTester.py

[nobody at svn.erp5.org]

Author: kazuhiko
Date: Wed Mar 24 15:48:43 2010
New Revision: 34053

URL: http://svn.erp5.org?rev=34053&view=rev
Log:
no need to support legacy 'order' category in new equivalence testers.

Modified:
    erp5/trunk/products/ERP5/Document/FloatEquivalenceTester.py

Modified: erp5/trunk/products/ERP5/Document/FloatEquivalenceTester.py
URL: http://svn.erp5.org/erp5/trunk/products/ERP5/Document/FloatEquivalenceTester.py?rev=34053&r1=34052&r2=34053&view=diff
==============================================================================
--- erp5/trunk/products/ERP5/Document/FloatEquivalenceTester.py [utf8] (original)
+++ erp5/trunk/products/ERP5/Document/FloatEquivalenceTester.py [utf8] Wed Mar 24 15:48:43 2010
@@ -78,11 +78,6 @@
     if self.getProperty('use_delivery_ratio') and \
         prevision_movement.getDelivery() == decision_movement.getRelativeUrl():
       decision_value *= prevision_movement.getDeliveryRatio()
-
-    # XXX do we need to support order_ratio too?
-    if self.getProperty('use_order_ratio') and \
-        decision_movement.getOrder() == prevision_movement.getRelativeUrl():
-      prevision_value *= decision_movement.getOrderRatio()
 
     delta = decision_value - prevision_value
     # XXX we should use appropriate property sheets and getter methods