anyoptimization
Relaxing strong requirement for cma==3.2.2
Pymoo has a requirement of cma==3.2.2. Is there any reason to fix the version, rather than using cma>=3.2.2 as is usually expected from a library? Is pymoo not compatible with cma 3.3.0? This leads to conflicts with any library that might want to use cma 3.3.0 (or future newer versions).
This is the release notes:
Release 3.3.0 implements
- diagonal acceleration via diagonal decoding (option CMA_diagonal_decoding, by default still off).
- fmin_lq_surr2 for running the surrogate assisted lq-CMA-ES.
- optimization_tools.ShowInFolder to facilitate rapid experimentation.
- verb_disp_overwrite option starts to overwrite the last line of the display output instead of continuing adding lines to avoid screen flooding with longish runs (off by default).
- various smallish improvements, bug fixes and additional features and functions.
It doesn't look like it should be an issue, but it should be tested.
Great! I agree that an update makes sense. I have added the dependency because I had once a version break and tried to avoid this in the future.
Can one of you please quickly test if nothing breaks? If yes I am more than happy to update the dependency.
I am getting this error message ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. pymoo 0.6.1.1 requires cma==3.2.2, but you have cma 3.3.0 which is incompatible.
