API Changes / Segregation

wesm / pandas2

Design documents and code for the pandas 2.0 effort.

https://pandas-dev.github.io/pandas2/

306 stars 41 forks source link

API Changes / Segregation #66

Open jreback opened 7 years ago

jreback commented 7 years ago

This will serve as a master issue to record API changes / testing that needs segregation in pandas.

Copy-on-write can help here:

[ ] view propagation: https://github.com/pandas-dev/pandas/issues/14953

wesm commented 7 years ago

As a matter of process, the way this should probably work is:

Segregate unit tests subject to breakage in upstream pandas-dev/pandas
Rebase pandas2 on upstream branch.
Write new unit tests that port those "bad" tests to new tests that reflect the changed behavior

what do you think?

jreback commented 7 years ago

yep, should have the test runner exclude them for pandas2 (and add separate tests that only) apply to pandas 2.

so prob need something like

pandas/tests # existing tests
pandas/tests_changing_in_pandas2
pandas/tests_pandas2

with the sub-structure the same as

pandas/tests

but the changing/pandas2 can live on pandas2 repo

jorisvandenbossche commented 7 years ago

From the dev meeting: idea is instead of physically segregating the tests is to leave them at the same place but mark them as "may fail on pandas 2.0"