This was a bug in torchvision, it’s fixed with this PR 24.
We’re working on pushing a new release soon that will include this fix (among many others!). To get the fix locally today, you can install torchvision master from source 9.