hashable patch interacts badly with --allow-newer
The os-string flag being default: False interacts badly with --allow-newer. Any builds with --allow-newer that pull in hashable will end up using the new filepath but without os-string, and so failing with the very error that this patch was meant to solve. Pinging @RyanGlScott as the author of that patch.