DEPR: to_clipboard, read_clipboard

[jbrockmendel]

• closes DEPR: to_clipboard #52129 (Replace xxxx with the GitHub issue number)
• 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.

[WillAyd]

Why do we want to deprecate these? I personally find them useful every now and again - are these a maintenance burden?

[jbrockmendel]

My main complaint is that we effectively aren't (and AFAICT can't) test it on the CI. If I'm wrong about it being rarely used then i wont mind keeping it around.

[WillAyd]

I would prefer to keep these. Sure not the main reason for using pandas, but they are nice for quick transfers of data across applications

[MarkRotchell]

I use this functionality all the time. Often will define something like the below at the top of a notebook for sending arbitraty array-likes to the clipboard as I'm modelling. Clearly, not something needed (much?) in production code, but when doing ad-hoc throw-away work/analysis, it's incredibly useful.

def clippy(data):
    pd.DataFrame(data).to_clipboard()

[jbrockmendel]

I don't care about this deprecation enough to argue about it, but my thought is that the def clippy(data) use case would be better served by

def clippy(data):
    content = pd.DataFrame(data).to_csv()
    something_that_lives_outside_of_pandas.to_clipboard(content)

[mroeschke]

My attempt to test clipboard in the CI in #56084

[phofl]

Merged the test pr, so closing here