Followup: I discovered/realized that, even though I was using cygwin's python, the windows python (Anaconda in my case) was still in my cygwin path, because the cygwin path has the windows path elements in it. You can see that if you run this, and see two pythons:
which -a python
I discovered this when I ran pip and ipython in cygwin, and they "worked," i.e. something ran, but not right.I put this at the end of my .bashrc to remove windows python from cygwin's path:
export PATH=$(echo $PATH |sed -e "s/:[^:]*Anaconda[^:]*:/:/g" |sed -e "s/:[^:]*Anaconda[^:]*:/:/g")
There were two anaconda directories in the path, and /g should have taken care of both, but my RE-fu is apparently lacking, so brute force.Cygwin has pitfalls.
I suspect one of two things, although it could be something else. You might be using the windows installation of python, rather than the cygwin installation. In most cases that works fine, but cygwin's python is compiled to expect a cygwin/unix-like environment, and windows python is compiled to expect windows. Sometimes weirdness ensues, and it's better to use cygwin's python in cygwin.
My other suspicion is that the installation of youtube-dl didn't happen correctly. Notice above that I used pip, which is offered in the installation instructions. If you've installed pip that's usually your best/first option. Their first instructions involve downloading the gz (as you did). I did that with wget in python, then noticed the installation is an extraction and a chmod; I'm usually more comfortable trying pip in that circmstance.
I've placed my email in my profile if you want to chat about this. I'll leave it there until I remember to remove it.
Edit: you can run the python shell, and it will summarize python's construction:
From a windows cmd.exe shell: