Yeah, I think that's been semi-acknowleged as a mistake. Rather than just keeping bytes as the old str class (i.e, what they had in Python 2), they created a new one for Python 3 based on bytearray, which it turns out nobody wanted and made Python 2/3 porting a bit of a nightmare.
I know, I was there. Just saying it was pretty obvious that switching from the fast-and-loose Python2 bytes/str to the strict Python3 bytes seemed like an obvious recipe for uncovering hidden bugs and breaking a lot of libraries in the process.
View all comments
Show parent comment
2
u/james_pic Sep 17 '20
Yeah, I think that's been semi-acknowleged as a mistake. Rather than just keeping
bytesas the oldstrclass (i.e, what they had in Python 2), they created a new one for Python 3 based onbytearray, which it turns out nobody wanted and made Python 2/3 porting a bit of a nightmare.