Merge remote-tracking branch 'upstream/main' into groupby-generic-doc-SeriesGroupby

Making branch be up to date

Author: acrossler

.devcontainer.json

@@ -65,14 +65,12 @@ pandas/_version.py export-subst
 asv_bench export-ignore
 ci export-ignore
 doc export-ignore
-gitpod export-ignore
 MANIFEST.in export-ignore
 scripts/** export-ignore
 typings export-ignore
 web export-ignore
 CITATION.cff export-ignore
 codecov.yml export-ignore
-Dockerfile export-ignore
 environment.yml export-ignore
 setup.py export-ignore
 

.gitattributes

@@ -3,3 +3,4 @@
 - [ ] All [code checks passed](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit).
 - [ ] Added [type annotations](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#type-hints) to new arguments/methods/functions.
 - [ ] Added an entry in the latest `doc/source/whatsnew/vX.X.X.rst` file if fixing a bug or adding a new feature.
+- [ ] If I used AI to develop this pull request, I prompted it to follow `AGENTS.md`.

.github/PULL_REQUEST_TEMPLATE.md

@@ -131,33 +131,6 @@ jobs:
         asv machine --yes
         asv run --quick --dry-run --durations=30 --python=same --show-stderr
 
-  build_docker_dev_environment:
-    name: Build Docker Dev Environment
-    runs-on: ubuntu-24.04
-    defaults:
-      run:
-        shell: bash -el {0}
-
-    concurrency:
-      # https://github.community/t/concurrecy-not-work-for-push/183068/7
-      group: ${{ github.event_name == 'push' && github.run_number || github.ref }}-build_docker_dev_environment
-      cancel-in-progress: true
-
-    steps:
-      - name: Clean up dangling images
-        run: docker image prune -f
-
-      - name: Checkout
-        uses: actions/checkout@v5
-        with:
-          fetch-depth: 0
-
-      - name: Build image
-        run: docker build --pull --no-cache --tag pandas-dev-env .
-
-      - name: Show environment
-        run: docker run --rm pandas-dev-env python -c "import pandas as pd; print(pd.show_versions())"
-
   requirements-dev-text-installable:
     name: Test install requirements-dev.txt
     runs-on: ubuntu-24.04

.github/workflows/code-checks.yml

@@ -39,6 +39,7 @@ jobs:
     if: >-
       (github.event_name == 'schedule') ||
       github.event_name == 'workflow_dispatch' ||
+      github.event_name == 'release' ||
       (github.event_name == 'pull_request' &&
       contains(github.event.pull_request.labels.*.name, 'Build')) ||
       (github.event_name == 'push' && startsWith(github.ref, 'refs/tags/v') && ( ! endsWith(github.ref, 'dev0')))
@@ -84,6 +85,7 @@ jobs:
     if: >-
       (github.event_name == 'schedule') ||
       github.event_name == 'workflow_dispatch' ||
+      github.event_name == 'release' ||
       (github.event_name == 'pull_request' &&
       contains(github.event.pull_request.labels.*.name, 'Build')) ||
       (github.event_name == 'push' && startsWith(github.ref, 'refs/tags/v') && ( ! endsWith(github.ref, 'dev0')))

.github/workflows/wheels.yml

@@ -0,0 +1,48 @@
+# pandas Agent Instructions
+
+## Project Overview
+`pandas` is an open source, BSD-licensed library providing high-performance, easy-to-use data structures and data analysis tools for the Python programming language.
+
+## Purpose
+- Assist contributors by suggesting code changes, tests, and documentation edits for the pandas repository while preserving stability and compatibility.
+
+## Persona & Tone
+- Concise, neutral, code-focused. Prioritize correctness, readability, and tests.
+
+## Project Guidelines
+- Be sure to follow all guidelines for contributing to the codebase specified at https://pandas.pydata.org/docs/development/contributing_codebase.html
+- These guidelines are also available in the following local files, which should be loaded into context and adhered to
+    - doc/source/development/contributing_codebase.rst
+    - doc/source/development/contributing_docstring.rst
+    - doc/source/development/contributing_documentation.rst
+    - doc/source/development/contributing.rst
+
+## Decision heuristics
+- Favor small, backward-compatible changes with tests.
+- If a change would be breaking, propose it behind a deprecation path and document the rationale.
+- Prefer readability over micro-optimizations unless benchmarks are requested.
+- Add tests for behavioral changes; update docs only after code change is final.
+
+## Type hints guidance (summary)
+- Prefer PEP 484 style and types in pandas._typing when appropriate.
+- Avoid unnecessary use of typing.cast; prefer refactors that convey types to type-checkers.
+- Use builtin generics (list, dict) when possible.
+
+## Docstring guidance (summary)
+- Follow NumPy / numpydoc conventions used across the repo: short summary, extended summary, Parameters, Returns/Yields, See Also, Notes, Examples.
+- Ensure examples are deterministic, import numpy/pandas as documented, and pass doctest rules used by docs validation.
+- Preserve formatting rules: triple double-quotes, no blank line before/after docstring, parameter formatting ("name : type, default ..."), types and examples conventions.
+
+## Pull Requests (summary)
+- Pull request titles should be descriptive and include one of the following prefixes:
+    - ENH: Enhancement, new functionality
+    - BUG: Bug fix
+    - DOC: Additions/updates to documentation
+    - TST: Additions/updates to tests
+    - BLD: Updates to the build process/scripts
+    - PERF: Performance improvement
+    - TYP: Type annotations
+    - CLN: Code cleanup
+- Pull request descriptions should follow the template, and **succinctly** describe the change being made. Usually a few sentences is sufficient.
+- Pull requests which are resolving an existing Github Issue should include a link to the issue in the PR Description.
+- Do not add summaries or additional comments to individual commit messages. The single PR description is sufficient.

.gitpod.yml

@@ -828,7 +828,6 @@ def setup(app) -> None:
             "https://github.com/pandas-dev/pandas/blob/v0.20.2/pandas/core/generic.py#L568",
             "https://github.com/pandas-dev/pandas/blob/v0.20.2/pandas/core/frame.py#L1495",
             "https://github.com/pandas-dev/pandas/issues/174151",
-            "https://gitpod.io/#https://github.com/USERNAME/pandas",
             "https://manishamde.github.io/blog/2013/03/07/pandas-and-python-top-10/",
             "https://matplotlib.org/api/axes_api.html#matplotlib.axes.Axes.table",
             "https://nipunbatra.github.io/blog/visualisation/2013/05/01/aggregation-timeseries.html",

AGENTS.md

@@ -16,13 +16,11 @@ locally before pushing your changes. It's recommended to also install the :ref:`
     :maxdepth: 2
     :hidden:
 
-    contributing_gitpod.rst
 
 Step 1: install a C compiler
 ----------------------------
 
-How to do this will depend on your platform. If you choose to use ``Docker`` or ``GitPod``
-in the next step, then you can skip this step.
+How to do this will depend on your platform.
 
 **Windows**
 
@@ -163,51 +161,6 @@ should already exist.
    # Install the build dependencies
    python -m pip install -r requirements-dev.txt
 
-Option 3: using Docker
-~~~~~~~~~~~~~~~~~~~~~~
-
-pandas provides a ``DockerFile`` in the root directory to build a Docker image
-with a full pandas development environment.
-
-**Docker Commands**
-
-Build the Docker image::
-
-    # Build the image
-    docker build -t pandas-dev .
-
-Run Container::
-
-    # Run a container and bind your local repo to the container
-    # This command assumes you are running from your local repo
-    # but if not alter ${PWD} to match your local repo path
-    docker run -it --rm -v ${PWD}:/home/pandas pandas-dev
-
-*Even easier, you can integrate Docker with the following IDEs:*
-
-**Visual Studio Code**
-
-You can use the DockerFile to launch a remote session with Visual Studio Code,
-a popular free IDE, using the ``.devcontainer.json`` file.
-See https://code.visualstudio.com/docs/remote/containers for details.
-
-**PyCharm (Professional)**
-
-Enable Docker support and use the Services tool window to build and manage images as well as
-run and interact with containers.
-See https://www.jetbrains.com/help/pycharm/docker.html for details.
-
-Option 4: using Gitpod
-~~~~~~~~~~~~~~~~~~~~~~
-
-Gitpod is an open-source platform that automatically creates the correct development
-environment right in your browser, reducing the need to install local development
-environments and deal with incompatible dependencies.
-
-If you are a Windows user, unfamiliar with using the command line or building pandas
-for the first time, it is often faster to build with Gitpod. Here are the in-depth instructions
-for :ref:`building pandas with GitPod <contributing-gitpod>`.
-
 Step 3: build and install pandas
 --------------------------------