Creating virtual environment at: .venv
  x No solution found when resolving dependencies for split (markers: python_full_version == '3.10.*'):
  `-> Because only the following versions of zarr are available:
          zarr<=3.0.0
          zarr==3.0.1
          zarr==3.0.2
          zarr==3.0.3
          zarr==3.0.4
          zarr==3.0.5
          zarr==3.0.6
          zarr==3.0.7
          zarr==3.0.8
          zarr==3.0.9
          zarr==3.0.10
          zarr==3.1.0
          zarr==3.1.1
          zarr==3.1.2
          zarr==3.1.3
      and zarr>=3.0.0,<=3.0.2 was yanked (reason: zarr.load() deletes data. See https://github.com/zarr-developers/zarr-python/issues/3061 for more information), we
      can conclude that zarr>=3.0.0,<=3.0.2 cannot be used.
      And because zarr==3.0.3 was yanked (reason: broke a certain indexing incantation with our last release. see #2849. This can lead to data corruption) and
      zarr>=3.0.4,<=3.0.7 was yanked (reason: zarr.load() deletes data. See https://github.com/zarr-developers/zarr-python/issues/3061 for more information), we can
      conclude that zarr>=3.0.4,<=3.0.7 cannot be used. (1)

      Because the requested Python version (>=3.10) does not satisfy Python>=3.11 and zarr>=3.0.8 depends on Python>=3.11, we can conclude that zarr>=3.0.8 cannot
      be used.
      And because we know from (1) that zarr>=3.0.4,<=3.0.7 cannot be used, we can conclude that zarr>=3.0.0 cannot be used.
      And because your project depends on zarr>=3 and your project requires isofit[dev], we can conclude that your project's requirements are unsatisfiable.

      hint: The `requires-python` value (>=3.10) includes Python versions that are not supported by your dependencies (e.g., zarr>=3.0.8 only supports >=3.11).
      Consider using a more restrictive `requires-python` value (like >=3.11).
  help: If you want to add the package regardless of the failed resolution, provide the `--frozen` flag to skip locking and syncing.