Merge branch 'main' into update-docs-data-table-representation

Author: gnkl

.github/workflows/broken-linkcheck.yml

@@ -6,7 +6,7 @@ on:
 
 jobs:
   cleanup:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     if: github.repository_owner == 'pandas-dev'
     permissions:
       actions: write

.github/workflows/cache-cleanup-daily.yml

@@ -6,7 +6,8 @@ on:
 
 jobs:
   cleanup:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
+    if: github.repository_owner == 'pandas-dev'
     steps:
       - name: Clean Cache
         run: |

.github/workflows/cache-cleanup.yml

@@ -9,15 +9,6 @@ permissions:
   pull-requests: write
 
 jobs:
-  issue_assign:
-    runs-on: ubuntu-24.04
-    if: (!github.event.issue.pull_request) && github.event.comment.body == 'take'
-    concurrency:
-      group: ${{ github.actor }}-issue-assign
-    steps:
-      - run: |
-          echo "Assigning issue ${{ github.event.issue.number }} to ${{ github.event.comment.user.login }}"
-          curl -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" -d '{"assignees": ["${{ github.event.comment.user.login }}"]}' https://api.github.com/repos/${{ github.repository }}/issues/${{ github.event.issue.number }}/assignees
   preview_docs:
     runs-on: ubuntu-24.04
     if: github.event.issue.pull_request && github.event.comment.body == '/preview'
@@ -28,64 +19,3 @@ jobs:
         with:
           previewer-server: "https://pandas.pydata.org/preview"
           artifact-job: "Doc Build and Upload"
-  asv_run:
-    runs-on: ubuntu-24.04
-    # TODO: Support more benchmarking options later, against different branches, against self, etc
-    if: github.event.issue.pull_request && startsWith(github.event.comment.body, '@github-actions benchmark')
-    defaults:
-      run:
-        shell: bash -el {0}
-    env:
-      ENV_FILE: environment.yml
-      COMMENT: ${{github.event.comment.body}}
-
-    concurrency:
-      # Set concurrency to prevent abuse(full runs are ~5.5 hours !!!)
-      # each user can only run one concurrent benchmark bot at a time
-      # We don't cancel in progress jobs, but if you want to benchmark multiple PRs, you're gonna have
-      # to wait
-      group: ${{ github.actor }}-asv
-      cancel-in-progress: false
-
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v5
-        with:
-          fetch-depth: 0
-
-        # Although asv sets up its own env, deps are still needed
-        # during discovery process
-      - name: Set up Conda
-        uses: ./.github/actions/setup-conda
-
-      - name: Run benchmarks
-        id: bench
-        continue-on-error: true # asv will exit code 1 for regressions
-        run: |
-          # extracting the regex, see https://stackoverflow.com/a/36798723
-          REGEX=$(echo "$COMMENT" | sed -n "s/^.*-b\s*\(\S*\).*$/\1/p")
-          cd asv_bench
-          asv check -E existing
-          git remote add upstream https://github.com/pandas-dev/pandas.git
-          git fetch upstream
-          asv machine --yes
-          asv continuous -f 1.1 -b $REGEX upstream/main HEAD
-          echo 'BENCH_OUTPUT<<EOF' >> $GITHUB_ENV
-          asv compare -f 1.1 upstream/main HEAD >> $GITHUB_ENV
-          echo 'EOF' >> $GITHUB_ENV
-          echo "REGEX=$REGEX" >> $GITHUB_ENV
-
-      - uses: actions/github-script@v8
-        env:
-          BENCH_OUTPUT: ${{env.BENCH_OUTPUT}}
-          REGEX: ${{env.REGEX}}
-        with:
-          script: |
-            const ENV_VARS = process.env
-            const run_url = `https://github.com/${context.repo.owner}/${context.repo.repo}/actions/runs/${context.runId}`
-            github.rest.issues.createComment({
-              issue_number: context.issue.number,
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              body: '\nBenchmarks completed. View runner logs here.' + run_url + '\nRegex used: '+ 'regex ' + ENV_VARS["REGEX"] + '\n' + ENV_VARS["BENCH_OUTPUT"]
-            })

.github/workflows/comment-commands.yml

@@ -182,7 +182,7 @@ jobs:
     strategy:
       matrix:
         # Note: Don't use macOS latest since macos 14 appears to be arm64 only
-        os: [macos-13, macos-14, windows-latest]
+        os: [macos-13, macos-14, windows-2025]
         env_file: [actions-311.yaml, actions-312.yaml, actions-313.yaml]
       fail-fast: false
     runs-on: ${{ matrix.os }}
@@ -322,7 +322,7 @@ jobs:
       fail-fast: false
       matrix:
         # Separate out macOS 13 and 14, since macOS 14 is arm64 only
-        os: [ubuntu-24.04, macOS-13, macOS-14, windows-latest]
+        os: [ubuntu-24.04, macOS-13, macOS-14, windows-2025]
 
     timeout-minutes: 90
 

.github/workflows/unit-tests.yml

@@ -229,7 +229,7 @@ jobs:
       - build_sdist
       - build_wheels
 
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
 
     environment:
       name: pypi
@@ -243,6 +243,8 @@ jobs:
         with:
           path: dist          # everything lands in ./dist/**
 
+      # TODO: This step can be probably be achieved by actions/download-artifact@v5
+      # by specifying merge-multiple: true, and a glob pattern
       - name: Collect files
         run: |
           mkdir -p upload

.github/workflows/wheels.yml

@@ -36,16 +36,14 @@ and `good first issue
 <https://github.com/pandas-dev/pandas/issues?q=is%3Aopen+sort%3Aupdated-desc+label%3A%22good+first+issue%22+no%3Aassignee>`_
 are typically good for newer contributors.
 
-Once you've found an interesting issue, it's a good idea to assign the issue to yourself,
-so nobody else duplicates the work on it. On the Github issue, a comment with the exact
-text ``take`` to automatically assign you the issue
-(this will take seconds and may require refreshing the page to see it).
+Once you've found an interesting issue, leave a comment with your intention
+to start working on it. If somebody else has
+already commented on issue but they have shown a lack of activity in the issue
+or a pull request in the past 2-3 weeks, you may take it over.
 
 If for whatever reason you are not able to continue working with the issue, please
-unassign it, so other people know it's available again. You can check the list of
-assigned issues, since people may not be working in them anymore. If you want to work on one
-that is assigned, feel free to kindly ask the current assignee if you can take it
-(please allow at least a week of inactivity before considering work in the issue discontinued).
+leave a comment on an issue, so other people know it's available again. You can check the list of
+assigned issues, since people may not be working in them anymore.
 
 We have several :ref:`contributor community <community>` communication channels, which you are
 welcome to join, and ask questions as you figure things out. Among them are regular meetings for

doc/source/development/contributing.rst

@@ -948,6 +948,7 @@ Datetimelike
 - Bug in :class:`Timestamp` constructor failing to raise when given a ``np.datetime64`` object with non-standard unit (:issue:`25611`)
 - Bug in :func:`date_range` where the last valid timestamp would sometimes not be produced (:issue:`56134`)
 - Bug in :func:`date_range` where using a negative frequency value would not include all points between the start and end values (:issue:`56147`)
+- Bug in :func:`to_datetime` where passing an ``lxml.etree._ElementUnicodeResult`` together with ``format`` raised  ``TypeError``. Now subclasses of ``str`` are handled. (:issue:`60933`)
 - Bug in :func:`tseries.api.guess_datetime_format` would fail to infer time format when "%Y" == "%H%M" (:issue:`57452`)
 - Bug in :func:`tseries.frequencies.to_offset` would fail to parse frequency strings starting with "LWOM" (:issue:`59218`)
 - Bug in :meth:`DataFrame.fillna` raising an ``AssertionError`` instead of ``OutOfBoundsDatetime`` when filling a ``datetime64[ns]`` column with an out-of-bounds timestamp. Now correctly raises ``OutOfBoundsDatetime``. (:issue:`61208`)
@@ -971,7 +972,6 @@ Datetimelike
 - Bug in constructing arrays with :class:`ArrowDtype` with ``timestamp`` type incorrectly allowing ``Decimal("NaN")`` (:issue:`61773`)
 - Bug in constructing arrays with a timezone-aware :class:`ArrowDtype` from timezone-naive datetime objects incorrectly treating those as UTC times instead of wall times like :class:`DatetimeTZDtype` (:issue:`61775`)
 - Bug in setting scalar values with mismatched resolution into arrays with non-nanosecond ``datetime64``, ``timedelta64`` or :class:`DatetimeTZDtype` incorrectly truncating those scalars (:issue:`56410`)
-- Bug in :func:`to_datetime` where passing an ``lxml.etree._ElementUnicodeResult`` together with ``format`` raised  ``TypeError``. Now subclasses of ``str`` are handled. (:issue:`60933`)
 
 
 Timedelta

doc/source/whatsnew/v3.0.0.rst

@@ -295,29 +295,28 @@ def test_empty_with_nrows_chunksize(all_parsers, iterator):
     tm.assert_frame_equal(result, expected)
 
 
-def test_read_csv_memory_growth_chunksize(all_parsers):
+def test_read_csv_memory_growth_chunksize(temp_file, all_parsers):
     # see gh-24805
     #
     # Let's just make sure that we don't crash
     # as we iteratively process all chunks.
     parser = all_parsers
 
-    with tm.ensure_clean() as path:
-        with open(path, "w", encoding="utf-8") as f:
-            for i in range(1000):
-                f.write(str(i) + "\n")
-
-        if parser.engine == "pyarrow":
-            msg = "The 'chunksize' option is not supported with the 'pyarrow' engine"
-            with pytest.raises(ValueError, match=msg):
-                with parser.read_csv(path, chunksize=20) as result:
-                    for _ in result:
-                        pass
-            return
-
-        with parser.read_csv(path, chunksize=20) as result:
-            for _ in result:
-                pass
+    with open(temp_file, "w", encoding="utf-8") as f:
+        for i in range(1000):
+            f.write(str(i) + "\n")
+
+    if parser.engine == "pyarrow":
+        msg = "The 'chunksize' option is not supported with the 'pyarrow' engine"
+        with pytest.raises(ValueError, match=msg):
+            with parser.read_csv(temp_file, chunksize=20) as result:
+                for _ in result:
+                    pass
+        return
+
+    with parser.read_csv(temp_file, chunksize=20) as result:
+        for _ in result:
+            pass
 
 
 def test_chunksize_with_usecols_second_block_shorter(all_parsers):

pandas/tests/io/parser/common/test_chunksize.py

@@ -142,19 +142,18 @@ def test_iterator_skipfooter_errors(all_parsers, kwargs):
             pass
 
 
-def test_iteration_open_handle(all_parsers):
+def test_iteration_open_handle(temp_file, all_parsers):
     parser = all_parsers
     kwargs = {"header": None}
 
-    with tm.ensure_clean() as path:
-        with open(path, "w", encoding="utf-8") as f:
-            f.write("AAA\nBBB\nCCC\nDDD\nEEE\nFFF\nGGG")
+    with open(temp_file, "w", encoding="utf-8") as f:
+        f.write("AAA\nBBB\nCCC\nDDD\nEEE\nFFF\nGGG")
 
-        with open(path, encoding="utf-8") as f:
-            for line in f:
-                if "CCC" in line:
-                    break
+    with open(temp_file, encoding="utf-8") as f:
+        for line in f:
+            if "CCC" in line:
+                break
 
-            result = parser.read_csv(f, **kwargs)
-            expected = DataFrame({0: ["DDD", "EEE", "FFF", "GGG"]})
-            tm.assert_frame_equal(result, expected)
+        result = parser.read_csv(f, **kwargs)
+        expected = DataFrame({0: ["DDD", "EEE", "FFF", "GGG"]})
+        tm.assert_frame_equal(result, expected)