The pandas team has released pandas 3.0.0, a major update that changes core behaviors around string handling, memory semantics, and datetime resolution, while removing a substantial amount of deprecated functionality. The release introduces several changes to core behaviors in the library’s API.
In pandas 3.0, string data is now stored using a dedicated str dtype instead of the previous object dtype from NumPy. This change aims to provide a consistent method for handling string data. The new string dtype only accepts string values and allows for missing values, simplifying the management of missing data. Code that checks for the object dtype or handles missing values in the old way may need to be updated to align with these new standards.
Another change is the formal adoption of Copy-on-Write semantics. Indexing and subsetting operations now behave as if they return copies from the user’s perspective, eliminating longstanding ambiguity between views and copies. As a result, chained assignment no longer works, SettingWithCopyWarning has been removed, and defensive .copy() calls are no longer necessary to silence warnings. Internally, pandas may still use views for performance, but the API guarantees predictable copy-like behavior.
The release also introduces early support for a new expression syntax using pd.col(), allowing column-based transformations to be written declaratively instead of via lambda functions. For example, df.assign(c = pd.col("a") + pd.col("b")) replaces the need for inline callables. The feature is expected to expand in future versions.
Datetime handling has changed as well. Instead of defaulting to nanosecond precision, pandas now infers the most appropriate resolution when parsing input. This may affect code that assumes nanosecond-level integers when converting datetime values.
Under the hood, pandas 3.0 adds support for the Arrow PyCapsule interface, enabling zero-copy data exchange with Arrow-compatible systems. The release also raises the minimum requirement to Python 3.11 and NumPy 1.26.0, and shifts to the standard library’s zoneinfo as the default timezone backend.
The update has prompted discussion in the community about pandas’ direction and competition from alternatives such as Polars. In one thread, a commenter wrote:
Pandas has made a lot of poor design choices lately to be a more flexible “pythonic” library at the expense of the core data science user base. I would recommend polars instead.
Another added:
Unfortunately, it still doesn’t help with the awful API and the inferior performance in comparison with polars. It is nice that pandas keeps evolving, but the industry has already embraced polars, and I don’t think that whoever started to use polars would ever look back.
A pandas core developer responded:
I’m not sure that the industry really moved away. I think pandas is still huge compared to Polars. But I fully agree that pandas API and performance are very far from Polars, even with those changes.
Pandas 3.0.0 is available on PyPI and conda, accompanied by a migration guide outlining breaking changes and recommended upgrade steps.
