John Siirola

We have fixed this issue for the NL and LP interfaces. It is not clear if this is resolved in the direct / APPSI interfaces (I haven't tested it yet),...

Note that #839 points out that `display()` outputs deactivated blocks in a manner that makes it difficult to see that the blocks were deactivated.

I still think that removing a specialized `AbsExpression` and just using the `UnaryFunctionExpression` interface would be a net reduction in code and special cases. However, at this point, `AbsExpression` has...

Some questions: 1. Is it true that a writer should always be able to ignore Components that do not inherit from ActiveComponent? The rationale is that if the component affected...

Here is an argument for allowing variables on deactivated blocks. Consider a Disjunction containing two disjuncts `m.A` and `m.B`. There are two binary (Boolean) indicator variables (`m.A.indicator_var` and m.B.indicator_var`). When...

@blnicho: with (1), I want to draw a distinction between an error triggered because an unknown ctype is present on the model, and an error because an unknown ctype is...

As of 6.7.0, this has been addressed in the LP and NL writers (following from #1032). We still need to update the BAR, GAMS, and APPSI writers for consistency.

This is still waiting for the BAR and GAMS writer updates, and probably for the overall deprecation of the original implementation of `generate_standard_repn` (or at least porting that function over...

@emma58 is correct. This is still an open enhancement idea, with no concrete path toward implementation.

I am reopening this. This is a definite issue with packaging in Pyomo. Clearly, the `test-solvers` command has never been used by anyone that did not work with a checkout...