You can try this in a terminal:
```
python -c "from unittest.mock import MagicMock; open(MagicMock(), 'w'); print(0)"
```
But why didn't the tests fail under pytest?
pytest wraps, substitutes or otherwise messes with `sys.stdout` enough that fd 1 being dead doesn't cause prints to fail.
The best part? The method that calls `shutil.copy` is called `_safe_copy`, but it doesn't check whether the values it receives are strings or `Path`s. So it happily passes a `MagicMock` along as the copy destination.
So yeah, test your tests, and if you call something safe make it at least careful.
Tests started failing when run with unittest, had been running fine with pytest for a while.
Tests error out with `OSError: [Errno 9] Bad file descriptor`.
Turns out if you `shutil.copy` something onto a `MagicMock`, you kill `sys.stdout`:
```
from unittest.mock import MagicMock
import shutil
m = MagicMock()
m.__fspath__.__index__() # → 1
shutil.copy(filename, m)
[errors omitted]
print(1) # → OSError: [Errno 9] Bad file descriptor
```
Much head scratching!
Python Path is great. Until it isn't.
Don't try this at home.
remotePath = Path("data", "stuff")
pbexec("ssh", HOST, "rm", "-rf", remotePath / "/*")
The result is disastrous, as it it is:
ssh homeserver rm -rf /*
Not run as root, the server's installed software was not accessible, but it proceeded to my home directory before I could stop it and made a mess of it. Luckily nothing terminally lost.
It should have been remotePath / "*" or, even saner, just remotePath.
danzin
Klay
Harald
wowiamreallyamazed🍉️
incommunicado
Mathias ❄️🐺🐶 
Jon Udell