8000 PDEP-15: Reject PDEP-10 by lithomas1 · Pull Request #58623 · pandas-dev/pandas · GitHub
[go: up one dir, main page]

Skip to content

PDEP-15: Reject PDEP-10 #58623

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.

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

Closed
wants to merge 12 commits into from
Prev Previous commit
Next Next commit
Apply suggestions from code review
Co-authored-by: Irv Lustig <irv@princeton.com>
  • Loading branch information
lithomas1 and Dr-Irv authored May 21, 2024
commit 6e4efe5a5eff823d32a1d2d7104d594019966d3f
8000
4 changes: 2 additions & 2 deletions web/pandas/pdeps/0015-do-not-require-pyarrow.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,13 +29,13 @@ pyodide, a WASM distribution of pandas), both of which pyarrow does not provide
While both of these reasons are mentioned in the drawbacks section of this PDEP, at the time of the writing
of the PDEP, we underestimated the impact this would have on users, and also downstream developers.

2) Many of the benefits presented in this PDEP can be materialized even with payrrow as an optional dependency.
2) Many of the benefits presented in PDEP-10 can be materialized even with payrrow as an optional dependency.

For example, as detailed in PDEP-14, it is possible to create a new string data type with the same semantics
as our current default object string data type, but that allows users to experience faster performance and memory savings
compared to the object strings (if pyarrow is installed).

While we've decided to not move forward with requiring pyarrow in pandas 3.0, the rejection of this PDEP
While we've decided to not move forward with requiring pyarrow in pandas 3.0, the rejection of PDEP-10
does not mean that we are abandoning pyarrow support and integration in pandas. We, as the core team, still believe
that adopting support for pyarrow arrays and data types in more of pandas will lead to greater interoperability with the
ecosystem and better performance for users. Furthermore, a lot of the drawbacks, such as the large installation size of pyarrow
Expand Down
0