Closed pp-mo closed 1 year ago
This should be resolved shortly, see the above linked PR.
The 'clize' recipe is poorly maintained and requires attrs >=19.1.0,<20.
If clize
is important to you, I recommend making an issue to add yourself as a maintainer:
... where the title would be @conda-forge-admin, please add user @pp-mo
.
If that feedstock's team does not respond within a week, then you can escalate by:
@conda-forge/core
in the bot-created PR ...
This should be resolved, now: please re-open if you have any lingering issues with the conda-forge
package.
:+1: Thanks for responding on this !
This should be resolved shortly, see the above linked PR.
The 'clize' recipe is poorly maintained and requires attrs >=19.1.0,<20. If
clize
is important to you, I recommend making an issue to add yourself as a maintainer:
Unfortunately, "clize" is not directly used by us, so I don't think becoming a maintainer is practical in this case.
It was just a dependency asked for by another team, who use shared Python environments, which we build.
FWIW, after some discussion, we have managed to stop including it .
Solution to issue cannot be found in the documentation.
Issue
I am using conda/mamba to create an env with a large number of packages, including Jupyter and clize. The latest version of "jupyter_events" requires the "referencing" package, which itself is quite new and requires "attrs>=22.2.0".
The 'clize' recipe is poorly maintained and requires
attrs >=19.1.0,<20
.However, the actual bug is that this restriction cause an env to be created using
clize-4.2.1-pyhd8ed1ab_0
, and not including 'referencing'. Which naturally does not function (crashes when Jupyter is launched). If the deps were correctly recorded, this env create would actually fail, which is in fact the correct answer.So the older recipe builds should really be withdrawn or fixed.
I think both "_0" and "_1" are wrong in this way
Installed packages
Environment info