Merge branch 'main' into autofilter-feature

Author: antznette1

.github/PULL_REQUEST_TEMPLATE.md

@@ -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`.

AGENTS.md

@@ -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.

doc/source/user_guide/duplicates.rst

@@ -109,8 +109,6 @@ with the same label.
 Disallowing Duplicate Labels
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 1.2.0
-
 As noted above, handling duplicates is an important feature when reading in raw
 data. That said, you may want to avoid introducing duplicates as part of a data
 processing pipeline (from methods like :meth:`pandas.concat`,

doc/source/user_guide/groupby.rst

@@ -1264,8 +1264,6 @@ with
 Numba accelerated routines
 --------------------------
 
-.. versionadded:: 1.1
-
 If `Numba <https://numba.pydata.org/>`__ is installed as an optional dependency, the ``transform`` and
 ``aggregate`` methods support ``engine='numba'`` and ``engine_kwargs`` arguments.
 See :ref:`enhancing performance with Numba <enhancingperf.numba>` for general usage of the arguments

doc/source/user_guide/io.rst

@@ -156,13 +156,9 @@ dtype : Type name or dict of column -> type, default ``None``
   Data type for data or columns. E.g. ``{'a': np.float64, 'b': np.int32, 'c': 'Int64'}``
   Use ``str`` or ``object`` together with suitable ``na_values`` settings to preserve
   and not interpret dtype. If converters are specified, they will be applied INSTEAD
-  of dtype conversion.
-
-  .. versionadded:: 1.5.0
-
-     Support for defaultdict was added. Specify a defaultdict as input where
-     the default determines the dtype of the columns which are not explicitly
-     listed.
+  of dtype conversion. Specify a defaultdict as input where
+  the default determines the dtype of the columns which are not explicitly
+  listed.
 
 dtype_backend : {"numpy_nullable", "pyarrow"}, defaults to NumPy backed DataFrames
   Which dtype_backend to use, e.g. whether a DataFrame should have NumPy
@@ -177,12 +173,8 @@ dtype_backend : {"numpy_nullable", "pyarrow"}, defaults to NumPy backed DataFram
 engine : {``'c'``, ``'python'``, ``'pyarrow'``}
   Parser engine to use. The C and pyarrow engines are faster, while the python engine
   is currently more feature-complete. Multithreading is currently only supported by
-  the pyarrow engine.
-
-  .. versionadded:: 1.4.0
-
-     The "pyarrow" engine was added as an *experimental* engine, and some features
-     are unsupported, or may not work correctly, with this engine.
+  the pyarrow engine. Some features of the "pyarrow" engine
+  are unsupported or may not work correctly.
 converters : dict, default ``None``
   Dict of functions for converting values in certain columns. Keys can either be
   integers or column labels.
@@ -355,8 +347,6 @@ on_bad_lines : {{'error', 'warn', 'skip'}}, default 'error'
     - 'warn', print a warning when a bad line is encountered and skip that line.
     - 'skip', skip bad lines without raising or warning when they are encountered.
 
-    .. versionadded:: 1.3.0
-
 .. _io.dtypes:
 
 Specifying column data types
@@ -935,8 +925,6 @@ DD/MM/YYYY instead. For convenience, a ``dayfirst`` keyword is provided:
 Writing CSVs to binary file objects
 +++++++++++++++++++++++++++++++++++
 
-.. versionadded:: 1.2.0
-
 ``df.to_csv(..., mode="wb")`` allows writing a CSV to a file object
 opened binary mode. In most cases, it is not necessary to specify
 ``mode`` as pandas will auto-detect whether the file object is
@@ -1122,8 +1110,6 @@ You can elect to skip bad lines:
     data = "a,b,c\n1,2,3\n4,5,6,7\n8,9,10"
     pd.read_csv(StringIO(data), on_bad_lines="skip")
 
-.. versionadded:: 1.4.0
-
 Or pass a callable function to handle the bad line if ``engine="python"``.
 The bad line will be a list of strings that was split by the ``sep``:
 
@@ -1547,8 +1533,6 @@ functions - the following example shows reading a CSV file:
 
    df = pd.read_csv("https://download.bls.gov/pub/time.series/cu/cu.item", sep="\t")
 
-.. versionadded:: 1.3.0
-
 A custom header can be sent alongside HTTP(s) requests by passing a dictionary
 of header key value mappings to the ``storage_options`` keyword argument as shown below:
 
@@ -1600,8 +1584,6 @@ More sample configurations and documentation can be found at `S3Fs documentation
 If you do *not* have S3 credentials, you can still access public
 data by specifying an anonymous connection, such as
 
-.. versionadded:: 1.2.0
-
 .. code-block:: python
 
    pd.read_csv(
@@ -2535,8 +2517,6 @@ Links can be extracted from cells along with the text using ``extract_links="all
     df[("GitHub", None)]
     df[("GitHub", None)].str[1]
 
-.. versionadded:: 1.5.0
-
 .. _io.html:
 
 Writing to HTML files
@@ -2726,8 +2706,6 @@ parse HTML tables in the top-level pandas io function ``read_html``.
 LaTeX
 -----
 
-.. versionadded:: 1.3.0
-
 Currently there are no methods to read from LaTeX, only output methods.
 
 Writing to LaTeX files
@@ -2766,8 +2744,6 @@ XML
 Reading XML
 '''''''''''
 
-.. versionadded:: 1.3.0
-
 The top-level :func:`~pandas.io.xml.read_xml` function can accept an XML
 string/file/URL and will parse nodes and attributes into a pandas ``DataFrame``.
 
@@ -3093,8 +3069,6 @@ supports parsing such sizeable files using `lxml's iterparse`_ and `etree's iter
 which are memory-efficient methods to iterate through an XML tree and extract specific elements and attributes.
 without holding entire tree in memory.
 
-.. versionadded:: 1.5.0
-
 .. _`lxml's iterparse`: https://lxml.de/3.2/parsing.html#iterparse-and-iterwalk
 .. _`etree's iterparse`: https://docs.python.org/3/library/xml.etree.elementtree.html#xml.etree.ElementTree.iterparse
 
@@ -3133,8 +3107,6 @@ of reading in Wikipedia's very large (12 GB+) latest article data dump.
 Writing XML
 '''''''''''
 
-.. versionadded:: 1.3.0
-
 ``DataFrame`` objects have an instance method ``to_xml`` which renders the
 contents of the ``DataFrame`` as an XML document.
 

doc/source/user_guide/reshaping.rst

@@ -478,8 +478,6 @@ The values can be cast to a different type using the ``dtype`` argument.
 
     pd.get_dummies(df, dtype=np.float32).dtypes
 
-.. versionadded:: 1.5.0
-
 :func:`~pandas.from_dummies` converts the output of :func:`~pandas.get_dummies` back into
 a :class:`Series` of categorical values from indicator values.
 

doc/source/user_guide/timeseries.rst

@@ -1964,8 +1964,6 @@ Note the use of ``'start'`` for ``origin`` on the last example. In that case, ``
 Backward resample
 ~~~~~~~~~~~~~~~~~
 
-.. versionadded:: 1.3.0
-
 Instead of adjusting the beginning of bins, sometimes we need to fix the end of the bins to make a backward resample with a given ``freq``. The backward resample sets ``closed`` to ``'right'`` by default since the last value should be considered as the edge point for the last bin.
 
 We can set ``origin`` to ``'end'``. The value for a specific ``Timestamp`` index stands for the resample result from the current ``Timestamp`` minus ``freq`` to the current ``Timestamp`` with a right close.

doc/source/user_guide/visualization.rst

@@ -645,8 +645,6 @@ each point:
 
 If a categorical column is passed to ``c``, then a discrete colorbar will be produced:
 
-.. versionadded:: 1.3.0
-
 .. ipython:: python
 
    @savefig scatter_plot_categorical.png

doc/source/user_guide/window.rst

@@ -77,8 +77,6 @@ which will first group the data by the specified keys and then perform a windowi
     to compute the rolling sums to preserve accuracy as much as possible.
 
 
-.. versionadded:: 1.3.0
-
 Some windowing operations also support the ``method='table'`` option in the constructor which
 performs the windowing operation over an entire :class:`DataFrame` instead of a single column at a time.
 This can provide a useful performance benefit for a :class:`DataFrame` with many columns
@@ -100,8 +98,6 @@ be calculated with :meth:`~Rolling.apply` by specifying a separate column of wei
    df = pd.DataFrame([[1, 2, 0.6], [2, 3, 0.4], [3, 4, 0.2], [4, 5, 0.7]])
    df.rolling(2, method="table", min_periods=0).apply(weighted_mean, raw=True, engine="numba")  # noqa: E501
 
-.. versionadded:: 1.3
-
 Some windowing operations also support an ``online`` method after constructing a windowing object
 which returns a new object that supports passing in new :class:`DataFrame` or :class:`Series` objects
 to continue the windowing calculation with the new values (i.e. online calculations).
@@ -182,8 +178,6 @@ By default the labels are set to the right edge of the window, but a
 
 This can also be applied to datetime-like indices.
 
-.. versionadded:: 1.3.0
-
 .. ipython:: python
 
     df = pd.DataFrame(
@@ -365,8 +359,6 @@ The ``engine_kwargs`` argument is a dictionary of keyword arguments that will be
 These keyword arguments will be applied to *both* the passed function (if a standard Python function)
 and the apply for loop over each window.
 
-.. versionadded:: 1.3.0
-
 ``mean``, ``median``, ``max``, ``min``, and ``sum`` also support the ``engine`` and ``engine_kwargs`` arguments.
 
 .. _window.cov_corr:

doc/source/whatsnew/index.rst

@@ -24,6 +24,7 @@ Version 2.3
 .. toctree::
    :maxdepth: 2
 
+   v2.3.4
    v2.3.3
    v2.3.2
    v2.3.1