From 54fa93f141d8ffa12c2b893617ba1385c1370cb9 Mon Sep 17 00:00:00 2001
From: Joris Van den Bossche <jorisvandenbossche@gmail.com>
Date: Fri, 12 Dec 2025 18:13:31 +0100
Subject: [PATCH 1/4] WEB: add pandas 3.0 release candidate announcement blog

---
 .../blog/pandas-3.0-release-candidate.md      | 114 ++++++++++++++++++
 1 file changed, 114 insertions(+)
 create mode 100644 web/pandas/community/blog/pandas-3.0-release-candidate.md

diff --git a/web/pandas/community/blog/pandas-3.0-release-candidate.md b/web/pandas/community/blog/pandas-3.0-release-candidate.md
new file mode 100644
index 0000000000000..e1d92ab2e3e11
--- /dev/null
+++ b/web/pandas/community/blog/pandas-3.0-release-candidate.md
@@ -0,0 +1,114 @@
+Title: pandas 3.0.0 release candidate ready for testing
+Date: 2025-12-12
+
+# pandas 3.0.0 release candidate ready for testing!
+
+We're excited to announce the release candidate for pandas 3.0. This major
+release brings significant improvements to pandas, but also features some
+potentially breaking changes.
+
+## Highlights of pandas 3.0
+
+pandas 3.0 introduces several major enhancements:
+
+- **Dedicated string data type by default**: String columns are now inferred as
+  the new `str` dtype instead of `object`, providing better performance and type
+  safety
+- **Consistent copy/view behaviour with Copy-on-Write (CoW)** (a.k.a. getting
+  rid of the SettingWithCopyWarning): More predictable and consistent behavior
+  for all operations, with improved performance through avoiding unnecessary
+  copies
+- **New `pd.col` syntax**: Initial support for `pd.col()` as a simplified syntax
+  for creating callables in `DataFrame.assign`
+- **Enhanced deprecation policy**: A new 3-stage deprecation process to give
+  downstream packages more time to adapt
+
+You can find the complete list of changes in our
+[release notes](https://pandas.pydata.org/docs/dev/whatsnew/v3.0.0.html).
+
+## Important changes requiring code updates
+
+As a major release, pandas 3.0 includes some breaking changes that may require
+updates to your code. The two most significant changes are:
+
+### 1. Dedicated string data type by default
+
+Starting with pandas 3.0, string columns are automatically inferred as `str`
+dtype instead of the numpy `object` (which can store any Python object).
+
+**Example of the change:**
+```python
+# Old behavior (pandas < 3.0)
+>>> ser = pd.Series(["a", "b"])
+>>> ser
+0    a
+1    b
+dtype: object  # <-- numpy object dtype
+
+# New behavior (pandas 3.0)
+>>> ser = pd.Series(["a", "b"])
+>>> ser.dtype
+>>> ser
+0    a
+1    b
+dtype: str  # <-- new string dtype
+```
+
+This change improves performance and type safety, but may require code updates.
+For more details, see the
+[String Data Type Migration Guide](https://pandas.pydata.org/docs/dev/user_guide/migration-3-strings.html).
+
+### 2. Consistent copy/view behaviour with Copy-on-Write (CoW)
+
+Copy-on-Write is now the default and only mode in pandas 3.0. This makes
+behavior more consistent and predictable, but requires updates to certain coding
+patterns:
+
+**What you need to update:**
+- **Chained assignment** will no longer work. You'll need to use `.loc` or
+  `.iloc` directly on the DataFrame instead
+- The `SettingWithCopyWarning` is removed (since chained assignment no longer works)
+- Any indexing operation now always behaves as if it were a copy, so
+  modifications won't affect the original DataFrame
+
+**Example of the change:**
+```python
+# Old behavior (pandas < 3.0) - chained assignment
+df[df['A'] > 0]['B'] = 1  # This might modify df (unpredictable)
+
+# New behavior (pandas 3.0) - must use .loc
+df.loc[df['A'] > 0, 'B'] = 1  # This is the correct way
+```
+
+[Copy-on-Write Migration Guide](https://pandas.pydata.org/pandas-docs/version/3.0.0/user_guide/copy_on_write.html)
+
+## Call to Action: Test the Release Candidate
+
+We need your help to ensure a smooth pandas 3.0 release!
+
+Especially if you have pandas code in production or maintain a library with
+pandas as a dependency, it is strongly recommended to run your test suites with
+the release candidate, and report any issue to our issue tracker before the
+official 3.0.0 release.
+
+1. **Install the release candidate** and test it with your codebase
+2. **Run your existing code** to identify any issues or needed updates
+3. **Report any problems** you encounter on our [GitHub repository](https://github.com/pandas-dev/pandas/issues)
+4. **Share your migration experiences** with the community
+
+The more testing we get now, the smoother the final pandas 3.0 release will be
+for everyone. Your feedback is crucial to making this a successful release!
+
+### Getting the Release Candidate
+
+You can install the pandas 3.0 release candidate from PyPI:
+
+```bash
+python -m pip install --upgrade pandas==3.0.0rc0
+```
+
+Or from conda-forge using conda/mamba:
+
+```bash
+conda install -c conda-forge/label/pandas_rc pandas==3.0.0rc0
+```

From 4fc155f89da9b8795eb3d3a2141dd47541b72b82 Mon Sep 17 00:00:00 2001
From: Joris Van den Bossche <jorisvandenbossche@gmail.com>
Date: Mon, 15 Dec 2025 23:09:40 +0100
Subject: [PATCH 2/4] some styling updates (smaller max-width, more margin
 around h1)

---
 web/pandas/_templates/layout.html | 4 +++-
 web/pandas/index.html             | 2 +-
 web/pandas/static/css/pandas.css  | 7 +++++++
 3 files changed, 11 insertions(+), 2 deletions(-)

diff --git a/web/pandas/_templates/layout.html b/web/pandas/_templates/layout.html
index c26b093b0c4ba..bf1918326f8b8 100644
--- a/web/pandas/_templates/layout.html
+++ b/web/pandas/_templates/layout.html
@@ -56,9 +56,11 @@
             </nav>
         </header>
         <main role="main">
-            <div class="container">
+            {% block body_container %}
+            <div class="container container-main">
                 {% block body %}{% endblock %}
             </div>
+            {% endblock %}
         </main>
         <footer class="container pt-4 pt-md-5 border-top">
             <ul class="list-inline social-buttons float-end">
diff --git a/web/pandas/index.html b/web/pandas/index.html
index c520a16b8160f..fdc27f11a9e95 100644
--- a/web/pandas/index.html
+++ b/web/pandas/index.html
@@ -1,5 +1,5 @@
 {% extends "layout.html" %}
-{% block body %}
+{% block body_container %}
     <div class="container">
         <div class="row">
             <div class="col-md-9">
diff --git a/web/pandas/static/css/pandas.css b/web/pandas/static/css/pandas.css
index ef354d8264da4..c081c0b82f06a 100644
--- a/web/pandas/static/css/pandas.css
+++ b/web/pandas/static/css/pandas.css
@@ -9,6 +9,7 @@ h1 {
     font-size: 2.4rem;
     font-weight: 700;
     color: #130654;
+    margin: 2.4rem 0 2.4rem;
 }
 h2 {
     font-size: 1.8rem;
@@ -136,6 +137,12 @@ h2:hover a.headerlink, h3:hover a.headerlink {
     transition: opacity 0.5s;
 }
 
+@media (min-width: 992px) {
+  .container-main {
+    max-width: 960px;
+  }
+}
+
 
 /** Copied from the pydata-sphinx-theme **/
  div.admonition, .admonition {

From dee123622c1c0fa6ae32f1f5cd90dc70bb26702c Mon Sep 17 00:00:00 2001
From: Joris Van den Bossche <jorisvandenbossche@gmail.com>
Date: Mon, 15 Dec 2025 23:09:49 +0100
Subject: [PATCH 3/4] content updates

---
 .../blog/pandas-3.0-release-candidate.md      | 57 +++++++++++--------
 1 file changed, 34 insertions(+), 23 deletions(-)

diff --git a/web/pandas/community/blog/pandas-3.0-release-candidate.md b/web/pandas/community/blog/pandas-3.0-release-candidate.md
index e1d92ab2e3e11..c6d97a63bb575 100644
--- a/web/pandas/community/blog/pandas-3.0-release-candidate.md
+++ b/web/pandas/community/blog/pandas-3.0-release-candidate.md
@@ -7,6 +7,9 @@ We're excited to announce the release candidate for pandas 3.0. This major
 release brings significant improvements to pandas, but also features some
 potentially breaking changes.
 
+To ensure a smooth pandas 3.0 release, we can use your help to [test the
+release candidate now](#call-to-action-test-the-release-candidate).
+
 ## Highlights of pandas 3.0
 
 pandas 3.0 introduces several major enhancements:
@@ -20,8 +23,6 @@ pandas 3.0 introduces several major enhancements:
   copies
 - **New `pd.col` syntax**: Initial support for `pd.col()` as a simplified syntax
   for creating callables in `DataFrame.assign`
-- **Enhanced deprecation policy**: A new 3-stage deprecation process to give
-  downstream packages more time to adapt
 
 You can find the complete list of changes in our
 [release notes](https://pandas.pydata.org/docs/dev/whatsnew/v3.0.0.html).
@@ -36,7 +37,7 @@ updates to your code. The two most significant changes are:
 Starting with pandas 3.0, string columns are automatically inferred as `str`
 dtype instead of the numpy `object` (which can store any Python object).
 
-**Example of the change:**
+**Example:**
 ```python
 # Old behavior (pandas < 3.0)
 >>> ser = pd.Series(["a", "b"])
@@ -54,35 +55,41 @@ dtype: object  # <-- numpy object dtype
 dtype: str  # <-- new string dtype
 ```
 
-This change improves performance and type safety, but may require code updates.
+This change improves performance and type safety, but may require code updates,
+especially for library code that currently looks for "object" dtype when
+expecting string data.
+
 For more details, see the
-[String Data Type Migration Guide](https://pandas.pydata.org/docs/dev/user_guide/migration-3-strings.html).
+[migration guide for the new string data type](https://pandas.pydata.org/docs/dev/user_guide/migration-3-strings.html).
 
 ### 2. Consistent copy/view behaviour with Copy-on-Write (CoW)
 
 Copy-on-Write is now the default and only mode in pandas 3.0. This makes
 behavior more consistent and predictable, but requires updates to certain coding
-patterns:
+patterns.
 
-**What you need to update:**
-- **Chained assignment** will no longer work. You'll need to use `.loc` or
-  `.iloc` directly on the DataFrame instead
-- The `SettingWithCopyWarning` is removed (since chained assignment no longer works)
-- Any indexing operation now always behaves as if it were a copy, so
-  modifications won't affect the original DataFrame
+The most impactfull change is that **chained assignment will no longer work**.
+As a result, the `SettingWithCopyWarning` is also removed (since there is no
+longer ambiguity whether it would work or not).
 
-**Example of the change:**
+**Example:**
 ```python
 # Old behavior (pandas < 3.0) - chained assignment
-df[df['A'] > 0]['B'] = 1  # This might modify df (unpredictable)
+df["foo"][df["bar"] > 5] =   # This might modify df (unpredictable)
 
-# New behavior (pandas 3.0) - must use .loc
-df.loc[df['A'] > 0, 'B'] = 1  # This is the correct way
+# New behavior (pandas 3.0) - must do the modification in one step (e.g. with .loc)
+df.loc[df["bar"] > 5, "foo"] = 100
 ```
 
-[Copy-on-Write Migration Guide](https://pandas.pydata.org/pandas-docs/version/3.0.0/user_guide/copy_on_write.html)
+In general, any result of an indexing operation or method now always behaves as
+if it were a copy, so modifications of the result won't affect the original
+DataFrame.
+
+For more details, see the
+[Copy-on-Write migration guide](https://pandas.pydata.org/docs/dev/user_guide/copy_on_write.html#migrating-to-copy-on-write).
+
 
-## Call to Action: Test the Release Candidate
+## Call to Action: test the Release Candidate
 
 We need your help to ensure a smooth pandas 3.0 release!
 
@@ -91,13 +98,17 @@ pandas as a dependency, it is strongly recommended to run your test suites with
 the release candidate, and report any issue to our issue tracker before the
 official 3.0.0 release.
 
-1. **Install the release candidate** and test it with your codebase
-2. **Run your existing code** to identify any issues or needed updates
-3. **Report any problems** you encounter on our [GitHub repository](https://github.com/pandas-dev/pandas/issues)
-4. **Share your migration experiences** with the community
+How can you best test the release candidate?
+
+1. **First update to the latest released pandas 2.3** (if you are not already
+   running that version) and test it with your codebase. It is recommended to
+   resolve any deprecation warning before upgrading to pandas 3.0.
+2. **Install the release candidate** and test it with your codebase
+3. **Run your existing code** to identify any issues or needed updates
+4. **Report any problems** you encounter on our [GitHub repository issue tracker](https://github.com/pandas-dev/pandas/issues)
 
 The more testing we get now, the smoother the final pandas 3.0 release will be
-for everyone. Your feedback is crucial to making this a successful release!
+for everyone. Your feedback is crucial for making this a successful release!
 
 ### Getting the Release Candidate
 

From 0b8a7725026717110e4ae1d11da1f22cdfa83147 Mon Sep 17 00:00:00 2001
From: Joris Van den Bossche <jorisvandenbossche@gmail.com>
Date: Tue, 16 Dec 2025 09:44:01 +0100
Subject: [PATCH 4/4] review updates

---
 .../blog/pandas-3.0-release-candidate.md        | 17 +++++++++++------
 1 file changed, 11 insertions(+), 6 deletions(-)

diff --git a/web/pandas/community/blog/pandas-3.0-release-candidate.md b/web/pandas/community/blog/pandas-3.0-release-candidate.md
index c6d97a63bb575..e1f107f9bcd2d 100644
--- a/web/pandas/community/blog/pandas-3.0-release-candidate.md
+++ b/web/pandas/community/blog/pandas-3.0-release-candidate.md
@@ -1,4 +1,4 @@
-Title: pandas 3.0.0 release candidate ready for testing
+Title: pandas 3.0.0 release candidate ready for testing!
 Date: 2025-12-12
 
 # pandas 3.0.0 release candidate ready for testing!
@@ -24,7 +24,8 @@ pandas 3.0 introduces several major enhancements:
 - **New `pd.col` syntax**: Initial support for `pd.col()` as a simplified syntax
   for creating callables in `DataFrame.assign`
 
-You can find the complete list of changes in our
+Together with a lot of other improvements and bug fixes. You can find the
+complete list of changes in our
 [release notes](https://pandas.pydata.org/docs/dev/whatsnew/v3.0.0.html).
 
 ## Important changes requiring code updates
@@ -70,7 +71,8 @@ patterns.
 
 The most impactfull change is that **chained assignment will no longer work**.
 As a result, the `SettingWithCopyWarning` is also removed (since there is no
-longer ambiguity whether it would work or not).
+longer ambiguity whether it would work or not), and defensive `.copy()` calls
+to silence the warning are no longer needed.
 
 **Example:**
 ```python
@@ -103,9 +105,12 @@ How can you best test the release candidate?
 1. **First update to the latest released pandas 2.3** (if you are not already
    running that version) and test it with your codebase. It is recommended to
    resolve any deprecation warning before upgrading to pandas 3.0.
-2. **Install the release candidate** and test it with your codebase
-3. **Run your existing code** to identify any issues or needed updates
-4. **Report any problems** you encounter on our [GitHub repository issue tracker](https://github.com/pandas-dev/pandas/issues)
+2. Optionally, you can already enable the new string dtype and Copy-on-Write
+   mode using pandas 2.3 (`pd.options.future.infer_string = True` and
+   `pd.options.mode.copy_on_write = True`).
+3. **Install the release candidate** (see below) and test it with your codebase
+4. **Run your existing code** to identify any issues or needed updates
+5. **Report any problems** you encounter on our [GitHub repository issue tracker](https://github.com/pandas-dev/pandas/issues)
 
 The more testing we get now, the smoother the final pandas 3.0 release will be
 for everyone. Your feedback is crucial for making this a successful release!