Repository navigation
Python 3.13 support not present for spatialdata >= 0.3.0 from conda #1054
Description
Activity
Thanks for reporting, should get fixed when the new conda-forge distribution is out: conda-forge/spatialdata-feedstock#30
If you need 3.13 also for older spatialdata versions please make a patch (see an example here conda-forge/spatialdata-feedstock#17).
error libmamba Could not solve for environment specs The following packages are incompatible ├─ python 3.13.12* is requested and can be installed; └─ spatialdata 0.7.2* is not installable because it requires └─ python >=3.11,<3.13 , which conflicts with any installable versions previously reported. critical libmamba Could not solve for environment specsare you sure @LucaMarconato ?
True, there is still the 3.13 constraint here https://github.com/conda-forge/spatialdata-feedstock/pull/32/changes#diff-f3725a55bf339595bf865fec73bda8ac99f283b0810c205442021f29c06eea9aL40.
@LucaMarconato can I kindly lobby for you to fix this? In my humble opinion, installation issues are always of highest priority and should always be solved immediately. They hinder adoption and are a main cause of frustration. I'd love to update my best practice book environments.
Being worked on in https://github.com/conda-forge/spatialdata-feedstock/pulls?q=sort%3Aupdated-desc+is%3Apr+state%3Aopen+. This will affect only the latest released version. If you need python3.13 in a older version please open a PR directly with a patch (see an example here conda-forge/spatialdata-feedstock#17).
Closed by conda-forge/spatialdata-feedstock#35
Reacted by Lukas Heumos and Shashank KatiyarReacted by Ajayrama Kumaraswamy
Minimal working example
$ conda create -n temp python=3.13$ conda activate temp$ conda install conda-forge::spatialdata==0.3.0Output
Describe the bug
The latest spatialdata-feedstock at conda-forge still seems to have the python<3.13 constraint (https://github.com/conda-forge/spatialdata-feedstock/blob/51e4845ff4698ecdf75bc882f899beb1058e75f5/recipe/meta.yaml#L23), even though the discussion at #964 states that spatialdata should support it now. Just curious if this is intentional or not. A side-effect of this is that installing latest squidpy (v1.7.0) in python3.13 environment using conda is difficult because squidpy1.7.0 requires spatialdata>=0.6.0, which requires python<3.13.
Additional context
This is the link to the commit in the spatialdata-feedstock that added the constraint of python<3.13: conda-forge/spatialdata-feedstock@1cbe783.
Thanks a lot!