Error using uninitialized mutable Param as constraint bound about pyomo HOT 2 CLOSED

It looks like we are testing for this case (I commented out the code that checks this and noticed that some unit tests for constraint fail).

Perhaps I'll just change things so that the check is only performed if the constraint bound is constant. This would seem like the easiest way to bypass this in the short term. However, it is still debatable whether the the constant, infinite bound case is worthy of an error.

from pyomo.

I also want to document here that this did not fully fix the issue in Python3. There is another spot in _ConstraintData.set_value(...) that compares the upper and lower bound (self._lower != self._upper) resulting in

ValueError: No value for uninitialized NumericValue object ...

I'm not sure why this does not happen in Python2.

from pyomo.