spatialdata 0.3.0

[jdblischak]

Checklist

• Used a personal fork of the feedstock to propose changes
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

---

Closes #12
Closes #14

Blocked by conda-forge/multiscale-spatial-image-feedstock#5

Local rerendering had no effect because recently done in #10. The python_min in the recipe overrides the python_min in .ci_support/.

Explanation of differences from the 0.3.0 pyproject.toml:

• Upper bound of ome-zarr is due to a conda-forge/setuptools-scm problem that needs to be fixed (Dynamic version broken in conda binary for ome-zarr 0.10.3 ome-zarr-feedstock#24)
• Upper bound of <2025 for dask-core is because the breaking change was introduced in 2025.1.0. There is no reason that I am aware of that spatialdata 0.3.0 shouldn't be compatible with the 2024.12 minor releases of dask

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[giovp]

@conda-forge-admin please rerender

[giovp]

@conda-forge-admin please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/14249722853. Examine the logs at this URL for more detail.}

[giovp]

@conda-forge-admin please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/14255354543. Examine the logs at this URL for more detail.}

[giovp]

alright, I made the call and reverted back to the original pindown of dask. This is finally ready to go!

[giovp]

@conda-forge-admin please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/14269638001. Examine the logs at this URL for more detail.}

[LucaMarconato]

@jdblischak could you please comment on --no-deps and --no-build-isolation?

I see that they are added here in spatialdata-feedstock and in these downstream repositories:

• spatialdata-io-feedstock
• spatialdata-plot-feedstock

but not in these downstream repositories:

• napari-spatialdata-feedstock
• squidpy-feedstock.

Also the parameters are not used in these upstream repositories:

• spatial-image-feedstock
• multiscale-spatial-image-feedstock
• xarray-dataclasses-feedstock

[LucaMarconato]

CC @giovp

[jdblischak]

By default, pip will install any missing dependencies. However, all dependencies should be specified in the recipe and installed by conda. Using the flag --no-deps is a best practice to ensure all the required dependencies are defined in the recipe. It should be added to any recipe that is missing it

[jdblischak]

By default, pip creates a separate build environment, installs the build requirements, and build the package in this separate environment. Thus this completely defeats the purpose of using the conda recipe to specify the build requirements. Any recipe missing --no-build-isolation should have the flag added. It ensures the package is built by the conda packages indicated in the recipe.

[jdblischak]

A good habit when creating a new recipe or updating an existing one is to use grayskull, eg:

grayskull pypi --strict-conda-forge spatialdata
grep script spatialdata/meta.yaml
##   script: {{ PYTHON }} -m pip install . -vv --no-deps --no-build-isolation

which is the officially recommended method to generate conda-forge recipes.

[LucaMarconato]

Thanks! I will add these parameters to the incoming conda releases.

[LucaMarconato]

I tag also the other devs that are listed as maintainers of the repos above @melonora @timtreis @thewtex

[jdblischak]

Quick follow-up to add some more nuance. While the official stance is to add --no-deps --no-build-isolation, there is some debate in the community (conda/grayskull#582, conda/grayskull#584). Essentially in most cases the flags are redundant because conda-build/rattler-build set env vars to accomplish this. However, they are required for recipes with multiple outputs and in the past when conda-build has failed to set the env vars.

Personally, I like including the flags even when they are redundant because they make it more transparent to readers of the recipe that these pip behaviors are being enforced.

[LucaMarconato]

Thank you for the extra details!