BUG: Most recent conda-forge package limited to python 3.9?

[schorlton-bugseq]

Pandas version checks

• I have checked that this issue has not already been reported.

• I have confirmed this bug exists on the latest version of pandas.

• I have confirmed this bug exists on the main branch of pandas.

Reproducible Example

docker run --rm -it mambaorg/micromamba
micromamba install pandas -c conda-forge -c defaults

Issue Description

Sorry if this issue is in the wrong place! It seems there were previously conda-forge packages for linux-64 up to python v3.13 but the latest package only has v3.9:

https://anaconda.org/conda-forge/pandas/files

What this means is that installing pandas via the example above chooses to install python 3.9 unless the user selects a newer version of python, which is probably suboptimal?

Thanks for your consideration!

Expected Behavior

Conda-forge packages for all supported versions of python released at the same time?

Installed Versions

>>> pd.show_versions()                                                                                                                                        [11/1762]
                                         
INSTALLED VERSIONS          
------------------          
commit                : 0691c5cf90477d3503834d983f69350f250a6ff7
python                : 3.9.21
python-bits           : 64  
OS                    : Linux
OS-release            : 6.1.119-129.201.amzn2023.x86_64
Version               : #1 SMP PREEMPT_DYNAMIC Tue Dec  3 21:07:35 UTC 2024
machine               : x86_64
processor             :     
byteorder             : little
LC_ALL                : C.UTF-8
LANG                  : C.UTF-8
LOCALE                : en_US.UTF-8

pandas                : 2.2.3
numpy                 : 2.0.2
pytz                  : 2024.1
dateutil              : 2.9.0.post0
pip                   : 25.0
Cython                : None
sphinx                : None
IPython               : None
adbc-driver-postgresql: None
adbc-driver-sqlite    : None
bs4                   : None
blosc                 : None
bottleneck            : None
dataframe-api-compat  : None
fastparquet           : None
fsspec                : None
html5lib              : None
hypothesis            : None
gcsfs                 : None
jinja2                : None
lxml.etree            : None
matplotlib            : None
numba                 : None
numexpr               : None
odfpy                 : None
openpyxl              : None
pandas_gbq            : None
psycopg2              : None
pymysql               : None
pyarrow               : None
pyreadstat            : None
pytest                : None
python-calamine       : None
pyxlsb                : None
s3fs                  : None
scipy                 : None

[rhshadrach]

Not sure what would have caused these files to get updated since we didn't release anything. @lithomas1 - would you know?

[rhshadrach]

It looks like this occurs when the build recipe is updated. It's not clear to me that pandas has control over this.

[lithomas1]

Ah sorry looks like jobs failed on a PR I merged in after the 2.2.3 release.

I'll retrigger things.

[schorlton-bugseq]

Thanks for the really quick response!

[lithomas1]

Ah sorry looks like jobs failed on a PR I merged in after the 2.2.3 release.

I'll retrigger things.

Looks like quite a few tests are failing so something must have broke in the gap between releases.

Since 2.3 is coming out soon (I'm not sure of the exact date, but the last few PRs seem to be getting merged around now), I don't think there's going to be another 2.2.x release that's going to be able to fix the issues, sorry!

[schorlton-bugseq]

No prob for this specific patch version and thanks again for investigating and retriggering a build. Is there a way to ensure this doesn't happen going forward, i.e. ensuring that all conda packages successfully build before only some get published?

[rhshadrach]

Ah sorry looks like jobs failed on a PR I merged in after the 2.2.3 release.

@lithomas1 - the new files on conda-forge were uploaded just over 2 weeks ago, is this something that was done recently? If not, I don't understand why the files are being added now.

[lithomas1]

Ah sorry looks like jobs failed on a PR I merged in after the 2.2.3 release.

@lithomas1 - the new files on conda-forge were uploaded just over 2 weeks ago, is this something that was done recently? If not, I don't understand why the files are being added now.

Pins were added to the conda-forge pandas via this PR
conda-forge/pandas-feedstock#212

The reason things failed is mainly human error on my part.
That PR was green, but we hadn't re-run CI in a while, so it ended up red since something changed in the meantime.

[rhshadrach]

Thanks! Everything makes sense now, and agreed we can wait on a fix with 2.3.