Copy on write using weakrefs (part 2)

[nickeubank]

Continuation of #11500

[nickeubank]

@shoyer @jreback Ballpark timeline on refactor? Like, >1.5 years?

If so, I think I'll set this aside.Trying to modify the DataFrame constructor just opened a huge can of worms I think it'd take a long time to work through.

Till the refactor, any interest in making SettingWithCopyWarning into an exception?

[wesm]

I'd like to get it done in under a year; in combing through the codebase I've been making lists of things to do. It's a large effort but luckily we have a huge test suite to protect us and help keep the train on the rails. Will keep you posted

[nickeubank]

@wesm Great. Then will def set aside. :)

[jreback]

@nickeubank thanks for all the effort / commentary tests. I think these will be useful in the refactor.

[nickeubank]

@jreback thanks for the guidance! If nothing else, I now know a lot more about how references work in Python! :)

[TomAugspurger]

@nickeubank If you want to apply that knowledge for some internet karma, this came up yesterday ;)

[nickeubank]

@TomAugspurger on it, thanks Tom.

[pkch]

Is there an open issue for this? I found a bunch of issues related to this, but didn't see any open ones.

[jreback]

there are refeneced issues

[shoyer]

See wesm/pandas2#10