You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In nevergrad==1.0.4, colorama was added to the dependencies and locked the version to 0.4.0.
This means that this library cannot be used in apps that have a dependency on colorama > 0.4.0, unless they adopt a dependency manager that is OK with such conflicts (Poetry is not). We are pinned to nevergrad==1.0.3 to work around this.
However, none of the code in this project directly depends on colorama. The only place colorama shows up is in the file specifying the project dependencies.
In general, it is nice if the allowable versions of subdependencies is left up to the dependencies. And any issues with subdependency version compatibility are resolved in the upstream dependency probjects.
In this particular case, it looks like some people are having issues with this subdependency: #1492. I cannot reproduce what those individuals are experiencing on my Linux machine. But from my perspective, it isn't really nevergrad's responsibility to fix those issues, and they can just be forwarded to the dependency projects. Anyone experiencing subdependency issues can lock them themselves and comment on an issue in the upstream projects.
The text was updated successfully, but these errors were encountered:
I think bayesian-optimization has now fixed the problem. It may be that we can just update the version of bayesian-optimization that nevergrad depends on and remove the colorama specification.
In
nevergrad==1.0.4
, colorama was added to the dependencies and locked the version to 0.4.0.This means that this library cannot be used in apps that have a dependency on colorama > 0.4.0, unless they adopt a dependency manager that is OK with such conflicts (Poetry is not). We are pinned to
nevergrad==1.0.3
to work around this.However, none of the code in this project directly depends on colorama. The only place colorama shows up is in the file specifying the project dependencies.
In general, it is nice if the allowable versions of subdependencies is left up to the dependencies. And any issues with subdependency version compatibility are resolved in the upstream dependency probjects.
In this particular case, it looks like some people are having issues with this subdependency: #1492. I cannot reproduce what those individuals are experiencing on my Linux machine. But from my perspective, it isn't really nevergrad's responsibility to fix those issues, and they can just be forwarded to the dependency projects. Anyone experiencing subdependency issues can lock them themselves and comment on an issue in the upstream projects.
The text was updated successfully, but these errors were encountered: