You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GCPy 1.6.0 is now available on conda-forge. However, the conda-forge builds use Python versions 3.10, 3.11. and 3.12 but not the most recent Python 3.13 version. Using Python 3.13 causes the environment build to fail due to an error in the esmpy/xesmf packages.
I am just posting this here as a placeholder so that we don't forget to address this in the future.
yantosca
changed the title
GCPy does not build on conda-forge with python==3.13
geoschem-gcpy checks do not pass on conda-forge with python==3.13
Mar 4, 2025
yantosca
changed the title
geoschem-gcpy checks do not pass on conda-forge with python==3.13
GCPy does not build with the current environment.yml with python 3.13 or later
Mar 4, 2025
Your name
Bob Yantosca
Your affiliation
Harvard + GCST
What happened? What did you expect to happen?
GCPy 1.6.0 is now available on conda-forge. However, the conda-forge builds use Python versions 3.10, 3.11. and 3.12 but not the most recent Python 3.13 version. Using Python 3.13 causes the environment build to fail due to an error in the esmpy/xesmf packages.
I am just posting this here as a placeholder so that we don't forget to address this in the future.
What are the steps to reproduce the bug?
I opened the PR conda-forge/geoschem-gcpy-feedstock#19 to fix several outdated Python packages. However the build does not work with Python 3.13.
To reproduce the bug, remove the comment characters in these lines:
https://github.com/conda-forge/geoschem-gcpy-feedstock/blob/ba03cce009dfa91afd457ab6b71f8aefe3d3833b/.azure-pipelines/azure-pipelines-linux.yml#L27-L30
https://github.com/conda-forge/geoschem-gcpy-feedstock/blob/ba03cce009dfa91afd457ab6b71f8aefe3d3833b/.azure-pipelines/azure-pipelines-osx.yml#L23-L25
and run the GitHub action.
You can also produce this error by changing
python==3.12.0
topython==3.13.0
in theenvironment.yml
file. Then build a new mamba environment with:$ mamba env create -n gcpy_env_py313 --file=environment.yml`
which will fail due to package inconsistencies.
Please attach any relevant configuration and log files.
What GCPy version were you using?
1.6.0
What environment were you running GCPy on?
Other (please explain below)
What python environment were you using?
conda-forge
Will you be addressing this bug yourself?
Yes
Additional information
No response
The text was updated successfully, but these errors were encountered: