Please see the PR

Every non-empty str will be checked twice at present.

This redundant exists since Python 3.4 or earlier.

Unlikely to get changed in Py3.4/5 anymore, since this is not even a bug fix. I wouldn't even fight for backporting, although 3.7 seems ok for it.

I agree that this code duplication is worth removing. I don't consider hashing the empty string important enough for leaving it in, especially because the net performance effect can at most be zero, if not negative, for the normal case of non-empty strings.

New changeset a1d14253066f7dd60cfb465c6511fa565f312b42 by Serhiy Storchaka (animalize) in branch 'master':
bpo-35636: Remove redundant check in unicode_hash(). (GH-11402)
https://github.com/python/cpython/commit/a1d14253066f7dd60cfb465c6511fa565f312b42

Thanks for review.

Don't know why bytes and str generates the same hash value for ASCII sequence.
>>> hash('abc') == hash(b'abc')
True

This may brings some hash collisions, does it affect performance slightly?

> why bytes and str generates the same hash value for ASCII sequence

Probably mostly for historical Py2 reasons. These days, both are somewhat unlikely to appear in the same dict. But still, I'd advise against changing the hash function without a very good reason. You never know how much code relies on it in one way or another.

> I'd advise against changing the hash function without a very good reason. You never know how much code relies on it in one way or another.

ok, maybe this can be changed in Python 4.0

> maybe this can be changed in Python 4.0

Well, if you find a *very* good reason for changing it, as I said. Py4 won't be special in that regard, I suppose.

One scene is caching regular expresses, b'[a-z]', '[a-z]' may exist in the same dict. Any way, it's trivial on the whole.

For historical reasons. In Python 2, str and unicode consisting of ASCII characters can be equal. Equal values should have the same hash. In Python 3, bytes and str are always different. This can cause subtle bugs in the code ported from Python 2. Options -b and -bb were added to help to catch such bugs. For increasing a chance of catching such bugs, hashes of bytes and str consisting of ASCII characters with same codes, should be equal.