Skip to content

Commit c44bfb5

Browse files
rephrase main points in proposal
1 parent 1c4c2d9 commit c44bfb5

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

web/pandas/pdeps/0014-string-dtype.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -96,14 +96,15 @@ is intended to become the default in pandas 3.0).
9696

9797
To be able to move forward with a string data type in pandas 3.0, this PDEP proposes:
9898

99-
1. For pandas 3.0, a `"str"` string dtype is enabled by default, which will use PyArrow
100-
if installed, and otherwise falls back to an in-house functionally-equivalent
101-
(but slower) version.
99+
1. For pandas 3.0, a `"str"` string dtype is enabled by default, i.e. this
100+
string dtype will be used as the default dtype for text data when creating
101+
pandas objects (e.g. inference in constructors, I/O functions).
102102
2. This default string dtype will follow the same behaviour for missing values
103103
as other default data types, and use `NaN` as the missing value sentinel.
104-
3. The version that is not backed by PyArrow can reuse (with minor code
105-
additions) the existing numpy object-dtype backed StringArray for its
106-
implementation.
104+
3. The string dtype will use PyArrow if installed, and otherwise falls back to
105+
an in-house functionally-equivalent (but slower) version. This fallback can
106+
reuse (with minor code additions) the existing numpy object-dtype backed
107+
StringArray for its implementation.
107108
4. Installation guidelines are updated to clearly encourage users to install
108109
pyarrow for the default user experience.
109110

0 commit comments

Comments
 (0)