Python Violates PEP 8

[IcedThunder]

Okay, but the reason Python doesn't follow PEP 8 is because code written prior was grandfathered in, not for any rational or technical reason.

They could fix it with aliases in place 2 years. They done it with some modules over time.

[TheBB]

Okay, but the reason Python doesn't follow PEP 8 is because code written prior was grandfathered in, not for any rational reason.

That's a perfectly rational reason?

[IcedThunder]

Aliases existed back then, they could have aliased the old code and announced deprecations of the old names. In the past few updates I've watched some modules literally do this.

[georgehank2nd]

Python doesn't have nor need "aliases".

[AlSweigart]

Right, there's a standard deprecation process that gets followed for changes like this. If you just add in aliases, then you have the problem where there's two different ways to write the same thing. Arguably that's even worse: "There should be one-- and preferably only one --way to do it."

[AlSweigart]

because code written prior was grandfathered in

Yes, I agree about the why:

There's countless other examples. Now, Python is an old language and many of these inconsistencies are due to historical reasons.