Skip to content

Commit bd52f39

Browse files
tiny edit
1 parent af5ad3c commit bd52f39

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -49,9 +49,9 @@ This could be specified with the `storage` keyword in the opt-in string dtype
4949
Since its introduction, the `StringDtype` has always been opt-in, and has used
5050
the experimental `pd.NA` sentinel for missing values (which was also [introduced
5151
in pandas 1.0](https://pandas.pydata.org/docs/whatsnew/v1.0.0.html#experimental-na-scalar-to-denote-missing-values)).
52-
However, up to this date, pandas has not yet taken the step to use `pd.NA` by
53-
default for any dtype, and thus the `StringDtype` deviates in missing value behaviour compared
54-
to the default data types.
52+
However, up to this date, pandas has not yet taken the step to use `pd.NA` for
53+
for any default dtype, and thus the `StringDtype` deviates in missing value
54+
behaviour compared to the default data types.
5555

5656
In 2023, [PDEP-10](https://pandas.pydata.org/pdeps/0010-required-pyarrow-dependency.html)
5757
proposed to start using a PyArrow-backed string dtype by default in pandas 3.0
@@ -370,6 +370,6 @@ The 2.3.0 release would then have all future string functionality available
370370

371371
For pandas 3.0, this `future.infer_string` flag becomes enabled by default.
372372

373-
## PDEP-XX History
373+
## PDEP-14 History
374374

375375
- 3 May 2024: Initial version

0 commit comments

Comments
 (0)