John Siirola

I would be all for removing "call to evaluate". Unfortunately, if we remove it, we probably need to remove it from *all* Expression objects (ParamData supports it for consistency with...

pyutilib uses nose to collect / run the test harness. Generally, run the test suite using `nosetests`, although `python setup.py nosetests` also works. Note that `python setup.py test` has been...

That has nothing to do with pyutilib. You are running nosetests within a pylint source tree: those are all pylint tests.

You are correct: if you want to run the PyUtilib tests, you either execute nosetests within the pyutilib source tree, or you can run ``` nosetests pyutilib ``` The failing...

I am in favor of allowing Var objects to live outside the tree of active blocks that defines the current call to `solve()`. I am even potentially amenable to allowing...

Seconding @adam-a-a's comment: it would be helpful if the Warnings / Cautions included the thresholds for each of the warnings; e.g.: ``` Warning: 3 Variables with extreme Jacobian values (1e8)...

We have been debating this on the developer's call. I think we are leaning toward a slightly different (and a little more general) implementation: Users want to (easily) create custom...

I think the correct behavior is for `get_interval()` to return `(None, None, None)` for Sets with no ranges. That *should* cause the LP writer (and all the other writers) to...

Thinking about this PR, I am wondering if we should remove the sorting from `tabular_writer` all together? That was originally there because of Python < 3.7 when `dict` ordering was...

One additional thought: this would break backwards compatibility for the generated ostream, but not functional compatibility. This change could impact tests that rely on diffing those strings.