Ick. I think I do. I fear that the Coopr 3.5 dependency on the version of PyUtilib is specified as a >= and not a ==. Bill just cut a new release of PyUtilib, and I suspect that the new version is not backwards-compatible with the old, so Coopr is failing.
Bill: Can you confirm, and is it possible to back-patch PyUtilib 5.x so that I can still work with Coopr 3.x? Otherwise, can we cut a Coopr 3.5.1 release of just the Coopr metapackage that switches to an “==” dependency on PyUtilib? This just further reinforces that we need to get Pyomo 4.0 out asap.
Andreas: One possible workaround is to switch to Pyomo trunk. A rough procedure would be something like:
1) uninstall all coopr packages from your Python’s lib\site-packages directory. You can use “pip uninstall” for this, but you need to uninstall each of the ~dozen coopr.* packages individually.
2) make sure that you still have Pyutilib 5.0 installed. I would look in the pyutilib/setup.py file to verify, but there is probably an easier way.
3) do an subversion checkout of coopr trunk: “svn checkout https://software.sandia.gov/svn/pyomo/pyomo/trunk pyomo” into whatever directory you want
4) cd into that directory and run “python setup.py install”
Alternatively, after uninstalling both coopr.* and pyutilib from your python, you can use the “pyomo_install” script from the project download page to set up a “virtual” python installation pointing at pyomo trunk (this is what the developers do when working on the code).
john
--
You received this message because you are subscribed to the Google Groups "Pyomo Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
pyomo-forum...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
We are hoping that 4.0 will be out before the 24th.
I think the issue that we updated pyutilib.autodist and there were some app changes that impacted coopr.
Well have a new coopr/pyomo release within a week.
Bill
--