Skip to content

DOC: some small edits to 3.0 release notes #63379

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mroeschke merged 1 commit into from
Dec 16, 2025
+11 −10
Merged

DOC: some small edits to 3.0 release notes #63379

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions doc/source/whatsnew/v3.0.0.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,8 +80,8 @@ and how to adapt your code to the new default.

.. _whatsnew_300.enhancements.copy_on_write:

Copy-on-Write
^^^^^^^^^^^^^
Consistent copy/view behaviour with Copy-on-Write
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

The new "copy-on-write" behaviour in pandas 3.0 brings changes in behavior in
how pandas operates with respect to copies and views. A summary of the changes:
Expand All @@ -101,9 +101,10 @@ copy or a view depended on the exact operation performed, which was often
confusing).

Because every single indexing step now behaves as a copy, this also means that
"chained assignment" (updating a DataFrame with multiple setitem steps) will
stop working. Because this now consistently never works, the
``SettingWithCopyWarning`` is removed.
**"chained assignment"** (updating a DataFrame with multiple setitem steps)
**will stop working**. Because this now consistently never works, the
``SettingWithCopyWarning`` is removed, and defensive ``.copy()`` calls to
silence the warning are no longer needed.

The new behavioral semantics are explained in more detail in the
:ref:`user guide about Copy-on-Write <copy_on_write>`.
Expand Down
10 changes: 5 additions & 5 deletions web/pandas/community/blog/pandas-3.0-release-candidate.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,18 +14,18 @@ release candidate now](#call-to-action-test-the-release-candidate).

pandas 3.0 introduces several major enhancements:

- **Dedicated string data type by default**: String columns are now inferred as
- **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
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
- **New `pd.col` syntax**: initial support for `pd.col()` as a simplified syntax
for creating callables in `DataFrame.assign`

Together with a lot of other improvements and bug fixes. You can find the
complete list of changes in our
Further, pandas 3.0 includes 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
Expand Down