I've successfully built and tested 5.2.0 (ussuri) and 5.8.0 (yoga) versions of python3-openstackclient _without_ the `pyperclip==1.5.27` dependency, and run a full battery of openstack CLI tests, with and without $DISPLAY being set (ssh -Y <host> vs. not), and all worked perfectly without incident.
Since the clipboard is managed by the terminal of choice (iTerm/Terminal/Termius on macOS, PuTTY on Windows, xterm/rxvt/term on Linux), there is no reason for the _remote_ CLI tools to contain any clipboard sharing capabilities, such as those provided by `pyperclip`. Removing this Python dependency is a no-op to the function of the openstack client tools.
This is an easy, 1-line PR. I'll see if I can push this upstream and encourage our internal repackaging of the same to mitigate this issue on Ubuntu.
I've successfully built and tested 5.2.0 (ussuri) and 5.8.0 (yoga) versions of python3- openstackclient _without_ the `pyperclip==1.5.27` dependency, and run a full battery of openstack CLI tests, with and without $DISPLAY being set (ssh -Y <host> vs. not), and all worked perfectly without incident.
Since the clipboard is managed by the terminal of choice (iTerm/ Terminal/ Termius on macOS, PuTTY on Windows, xterm/rxvt/term on Linux), there is no reason for the _remote_ CLI tools to contain any clipboard sharing capabilities, such as those provided by `pyperclip`. Removing this Python dependency is a no-op to the function of the openstack client tools.
This is an easy, 1-line PR. I'll see if I can push this upstream and encourage our internal repackaging of the same to mitigate this issue on Ubuntu.