In Python 3, if pypdfChr() is provided an input that is either a bytes or str object it will throw a TypeError.
And in Python 2, if pypdfChr() is provided an int or unicode object it will quietly return the same object type (int or unicode).
This is a problem because code that interacts with a bytes string in a loop, or accesses a bytes string by index, the individual character will be a str in Python 2 but an int in Python 3. And if the string type is not 100% known (that is, perhaps it's unicode in Python 2 or str in Python 3), then the same loop or index-based access may be passed into pypdfChr(), causing a crash or an incorrect type to be returned.
In Python 3, if
pypdfChr()is provided an input that is either abytesorstrobject it will throw a TypeError.And in Python 2, if
pypdfChr()is provided anintorunicodeobject it will quietly return the same object type (intorunicode).This is a problem because code that interacts with a
bytesstring in a loop, or accesses abytesstring by index, the individual character will be astrin Python 2 but anintin Python 3. And if the string type is not 100% known (that is, perhaps it'sunicodein Python 2 orstrin Python 3), then the same loop or index-based access may be passed intopypdfChr(), causing a crash or an incorrect type to be returned.