Pyperclip does not work on Windows XP 32-bit about pyperclip

[seasalt]

Thanks . It should help. I noticed last night when was asked to restart my
comp
On Nov 19, 2015 5:26 PM, "Al Sweigart" [email protected] wrote:

Pyperclip doesn't work on WIndows XP 32-bit (and possibly 64-bit too).
When installing, the following output is received:

C:\Python34\Scripts>pip install pyperclip
Collecting pyperclip
Using cached pyperclip-1.5.24.zip
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "", line 20, in
File "C:\DOCUME1\admin\LOCALS1\Temp\pip-build-ncweabkc\pyperclip\setup.p
y", line 8, in
version=import('pyperclip').version,
File "C:\DOCUME1\admin\LOCALS1\Temp\pip-build-ncweabkc\pyperclip\pypercl
ip__init__.py", line 103, in
copy, paste = determine_clipboard()
File "C:\DOCUME1\admin\LOCALS1\Temp\pip-build-ncweabkc\pyperclip\pypercl
ip__init__.py", line 53, in determine_clipboard
return init_windows_clipboard()
File "C:\DOCUME1\admin\LOCALS1\Temp\pip-build-ncweabkc\pyperclip\pypercl
ip\windows.py", line 75, in init_windows_clipboard
wcscpy_s = ctypes.cdll.msvcrt.wcscpy_s
File "C:\Python34\lib\ctypes__init__.py", line 364, in getattr
func = self.getitem(name)
File "C:\Python34\lib\ctypes__init__.py", line 369, in getitem
func = self._FuncPtr((name_or_ordinal, self))
AttributeError: function 'wcscpy_s' not found

----------------------------------------

Command "python setup.py egg_info" failed with error code 1 in C:\DOCUME1\admin
\LOCALS1\Temp\pip-build-ncweabkc\pyperclip

When I try to modify the code to use ctypes.cdll.msvcrt.wcscpy instead of
ctypes.cdll.msvcrt.wcscpy_s, this quick fix just results in this error:

import pyperclip
pyperclip.copy('howdy')
Traceback (most recent call last):
File "", line 1, in
File "C:\Python34\pyperclip\windows.py", line 142, in copy_windows
if wcscpy_s(c_wchar_p(locked_handle), count, c_wchar_p(text)):
OSError: exception: access violation reading 0x00000006

This is probably an issue that wcscpy_s doesn't exist in the old
msvcrt.dll. I was able to replicate this in a VM. I'm not sure if this can
be fixed by updating the dll, but we should come up with a better solution
than that.

—
Reply to this email directly or view it on GitHub
#51.

[mhils]

Just my 5 cents: Windows XP is EOL, so IMHO there's really no reason to fix that.

[drakulavich]

I'm not sure, but may be runtime libraries will help?
https://www.microsoft.com/en-us/download/details.aspx?id=30679

[mhils]

Nonwithstanding my opinion on Windows XP support: IMO the best way to fix that is using memcpy, which we ultimately need to use anyway if we want to support other formats than text.

Edit: The suggestion below is certainly better.

[hynekcer]

The easiest and recommended way to copy memory is ctypes.memmove. It is independent on the platform and libraries.
(It is similarly insecure as memcpy, but in the context of preceding lines it is safe: The same size is copied that had been allocated.)