Comment 8 for bug 1475640

> My personal take is that the current behavior, specifically doing partial download is less than desirable.

Let me ask this question, since we're not doing anything with the data (in the instance the user doesn't tell us where to put the data), why is not downloading all 30GB of data for no particularly good reason desirable? No, really, why would a user want to wait for that to download in its entirety before being able to do what they actually wanted?

Here's the thing, we can add a flag that says --no-really-I-want-the-raw-bytes-printed-to-my-terminal, but I'm very much against reverting this because the "partial download" issue only affects the shell and doesn't affect users of the Python API.

I can see how this makes it harder for people to make an end-run around swift not being exposed to the user, but it doesn't make it *that* much harder.