ptrblck:

I would see this default as sticking to the “Zen of Python” - “Explicit is better than implicit”.


It seems to be falling short of this goal anyway.  If the idea was to avoid obscure performance problems caused by a distant change, torch should have thrown an exception in case async transfer is not possible.  Or at least printed a warning.