in the expr_dev merge), > when you update your working copy, you will need to remove the old *.pyc > files laying around (especially in the old pyomo/util directory). This >

I merged expr_dev last night. I also created the following branches: master_at_exprdev_merge - This branch was created just *before* the expr_dev merge, in case we need to re-direct

reviews in expr_dev PR > > > > Somehow, github has lost the reviews for this PR. We need folks to go > back and in and confirm their review. > > > > --Bill >

walker. Ideally, this would have been done in a PR to encourage a review of whether these fixes address everyone's concerns. But we haven't merged expr_dev yet. --Bill

> the expr_dev merge. > > > > john > > > > *From:* pyomo-developers@googlegroups.com [mailto: > pyomo-developers@googlegroups.com] *On Behalf

No need. I think that John identified the root cause. Checking now. On Monday, April 23, 2018 at 10:42:46 AM UTC-6, Bill Hart wrote: > > The

Here's a quick update, since I know that some of you are waiting on this merge: 1. I'm fighting with an intermittent test failure on python3.5.

days of expr_dev reviews, I wanted to give an update. I think I've resolved all of the "bug" issues and "rename this" issues that we've discussed. >

merge of expr_dev > > > > Cool. I'm not expecting to make any major commits at this point. > > > > I'm in the process of fixing bugs, though. Should I hold

before merging expr_dev. john From: pyomo-developers@googlegroups.com [mailto:pyomo-developers@googlegroups.com] On Behalf Of Gabriel Hackebeil Sent: Wednesday, February

in the expr_dev branch * See (https://github.com/Pyomo/pyomo/pull/272) for the PR related to this branch * See (http://pyomo.readthedocs.io/en/expr_dev/) for the online documentation

in the expr_dev branch. I don't think it's worth doing a PR for master. After all, this is a latent bug that we haven't seen since, well, Coopr3! > > --Bill > >

on the expr_dev branch. But the fact that these are so poorly tested suggests that they are not used in practice. Should we keep these transformations? Can you point to examples where

to the expr_dev >>> branch where this capability is being developed. And I'd like to work with >>> developers this month to confirm that their code that walks

> The expr_dev branch is where pyomo5 expressions have been developed. At > this point, most of the tests in Pyomo pass on my laptop. That means that > I'm not testing parts