BUG: NDFrame.__setattr__ calls object.__setattribute__ on the same name, which can cause unexpected behavior

[dhodcz2]

• closes BUG: NDFrame.__setattr__ calls object.__setattribute__ on the same name, which can cause unexpected behavior (rewrote #56773) #56793
• Tests added and passed if fixing a bug or adding a new feature
• All code checks passed.
• Added type annotations to new arguments/methods/functions.
• Added an entry in the latest doc/source/whatsnew/vX.X.X.rst file if fixing a bug or adding a new feature.

[rhshadrach]

As mentioned in the issue, the use case for subclassing pandas objects where a given attribute may be doing computation when accessed makes sense to avoid. I also like less try-excepts here. That said - this also appears to me it might make the code more fragile. An update to __getattribute__ not mirrored here could break things.

But overall still positive here. cc @phofl

[github-actions]

This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this.

[mroeschke]

Thanks for the PR but it has appears to gone stale. Additionally, this probably needs more discussion on the issue regarding the fix so closing until that discussion has resolved