New Pyomo version bug? #50
Labels
Comp:Build
This issue has to do with the build system of the code/doc (makefiles, cmake, install errors)
Difficulty:3-Expert
This issue is not only complicated, but also complex. It may require special advanced skills.
Priority:1-Critical
This is the highest priority (i.e. it is blocking other work or facing a deadline).
Status:1-New
No one has claimed this issue yet. It is in need of solving.
Type:Bug
Something is wrong or broken. This issue or PR is related to a bug in code.
Here's what I know, last week (2/20/2024) I could run an
osier.CapacityExpansion
problem just fine and the output would look something like thisWorking configurations
Now, the problem still runs but the output is a lot less pretty
Broken configurations
What I have tried
osier
because that's just how genetic algorithms work so it would be nice to turn off whatever error message is causing this.osier
in two fresh conda environments. One with Python 3.9 and the other with Python 3.10. I also tested it with Pyomo versions 6.4.1 and 6.7.1 (see above configurations) -- this behavior is only present with the most recent pyomo version, 6.7.1. Thispyomo
update was released this week which is consistent with the timeline where my code was working fine on Friday and today it is not. Especially since it was previously working on two other machines with more recent versions of pyomo, bet less recent than the current (until I updated them today and now they're broken).pyomo
version insetup.py
under theinstall_requires
parameter, however doing so results in the following error messageWhat needs to change
This issue can be closed when
setup.py
specifies a version ofpyomo<=6.7.0
.OR
Update the way
osier
is installed per the line in the error messageC:\Users\samgd\anaconda3\envs\pyomo64\lib\site-packages\setuptools\__init__.py:80: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
@yardasol would you mind helping with this?
The text was updated successfully, but these errors were encountered: