Closed whart222 closed 4 years ago
This PR is simple, but it will impact Pyomo. I'm queueing up the PR, but I don't think we should merge it until Pyomo has been updated to not rely on pyutilib.enum
Can we pull in enum / enum34 as a deprecation layer? I know that there are dependent packages that use pyutilib's enum (notably, IDAES).
The problem is that the packages are not equivalent. In particular, pyutilib.enum has an EnumValue type, which Pyomo uses to check whether it's using an enum type. I don't see an obvious way to recreate that semantics, but I'll explore whether a deprecation warning would work.
Superseded by #101
Fixes: #64
Summary/Motivation:
Removes the pyutilib.enum package, which has a different license from PyUtilib itself.
Changes proposed in this PR:
Legal Acknowledgement
By contributing to this software project, I agree to the following terms and conditions for my contribution: