My suspicion is that this behavior/code is left over from when the code was handling strings in python2, where strings were always null terminated and so the equal-bytes test would always pass.  I don't think this is appropriate for bytes objects, so I think the compare logic should be fixed.  But I don't deal with the C code much, so I'd like an opinion from a core dev who does.