-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Description
-
Poetry version: 1.4.0
-
Python version: 3.10.6
-
OS version and name: ubuntu 22.04.02 LTS
-
I am on the latest stable Poetry version, installed using a recommended method.
-
I have searched the issues of this repo and believe that this is not a duplicate.
-
I have consulted the FAQ and blog for any relevant entries or release notes.
-
If an exception occurs when executing a command, I executed it again in debug mode (
-vvvoption) and have included the output below.
Issue
Starting with this in the pyproject.toml:
python = "^3.8"
ome-zarr = "^0.6"
For poetry update, resolving deps takes 2.5 s.
Then for poetry add distributed, resolving deps takes 1.0 s.
Then for poetry update, resolving deps takes >600 s (didn't wait longer).
On the other hand, starting with this in the pyproject.toml:
python = "^3.8"
distributed = "^2023.4.1"
For poetry update, resolving deps takes 0.7 s.
Then for poetry add ome-zarr, resolving deps takes >600 s (didn't wait longer)
Interestingly, starting with this in the pyproject.toml:
python = "^3.8"
For poetry update, resolving deps takes 0.1 s.
Then for poetry add ome-zarr, resolving deps takes 3.4 s.
This may be an issue with ome-zarr, but I'm not sure where to begin with resolving this. Also please let me know if this should be better suited for ome-zarr's github repo.
Edit: hm, starting with this in the pyproject.toml:
python = "^3.8"
numpy = "^1.24.3"
For poetry update, resolving deps takes 0.4 s.
Then for poetry add ome-zarr, resolving deps takes 3.1 s.
Then for poetry update, resolving deps takes 3.2 s.
It seems like the specific combination of the ome-zarr and distributed packages.