Closed ctrueden closed 2 days ago
Hi @ctrueden
We will look into it next week!
Yes, I don't see any reason to constrain the dependencies here.
I relaxed them: https://github.com/Labelings/Labeling/commit/d160bc685199e44cf3bb52e27878ff718c71b2a9
v0.1.14 released 🎉
Hi @jdeschamps,
I'm trying to cut a new release of PyImageJ and I'm running into CI failures when trying to pull in labeling
version 0.1.14
.
└─ labeling [0.1.12|0.1.14] would require
└─ pillow <10 with the potential options
├─ pillow [3.0.0|3.2.0|...|6.2.1] would require
│ └─ python [2.7* |>=2.7,<2.8.0a0 ], which can be installed;
├─ pillow [3.0.0|3.2.0|...|5.3.0] would require
│ └─ python [3.5* |>=3.5,<3.6.0a0 ], which can be installed;
├─ pillow [3.0.0|3.4.2|...|5.1.0] would require
│ └─ python 3.6* , which can be installed;
├─ pillow 3.2.0 would require
│ └─ freetype 2.5* , which does not exist (perhaps a missing channel);
When looking at the conda-forge/labeling-feedstock recipe I can see that pillow<10
is still pinned. Our builds are pulling labeling from conda-forge instead of pypi directly. Can you update this to no longer pin pillow <10
?
Ah yes, the duplicate dependency management between conda-forge recipes and the project itself. Fun stuff. I filed conda-forge/labeling-feedstock#6 to hopefully help with this.
Doh :facepalm:! I should have done that. Thanks for filing that PR Curtis :).
This issue can be safely closed now with version 0.1.14
on conda-forge
.
Pillow is now on version 10.3.0, which includes support for Python 3.12.
From imagej/pyimagej#306
@jdeschamps Would you have time to make a new release of this project with the dependencies fixed, so that PyImageJ can work with 3.12? Or do you think we should go with @BptGrm's idea of forking the Labeling code into pyimagej itself?