On Aug 26, 2021, at 12:05, Brett Cannon
I wouldn't be opposed to that personally. I think a lot of people just think PEP 8 is a doc for the community when it is actually for Python itself and it happens to be very convenient for others to use. Although we obviously understand that people do use it in situations outside of the stdlib, so I don't think saying, "if you're going to use this in a way we didn't mean it to, here's some advice”.
It might be helpful to acknowledge that PEP 8 *in practice* often serves as the base style guide for code outside the stdlib. IME it rarely serves as *the* style guide though, since there usually are explicit deviations to adhere to organization or personal taste. I’ve also found some tools that maybe take PEP 8 a little too far, like it’s the law, or have different interpretations of the PEP 8 recommendations. The other thing to keep in mind is that, at least historically, we’ve rejected changes to PEP 8 to keep some deliberate ambiguity in the recommendations. PEP 8 can’t and shouldn’t be so detailed as to not give Python programmers some leeway to determine what’s right for them, their teams, or their projects. Cheers, -Barry