Core Python developer suspended for three months

Governance and Process

• Some see the suspension as a normal application of a clear governance mechanism to repeated CoC violations, not a “crisis.”
• Others argue the steering/council structure is repressive, selectively enforces the CoC, and uses power to neutralize critics, likening it to corporate or political hierarchies.
• Proposed bylaw changes to make it easier to remove lifetime members are viewed by critics as power grabs that reduce community voting and resemble “secret police” rather than open governance.
• A few commenters note that openly criticizing leadership in public is a classic way to get sidelined in any power structure.

Nature of the Conduct and Evidence

• The official list of reasons (posting volume, references to SNL skits, jokes about sensitive topics, discussion of “reverse racism/sexism,” etc.) is widely debated.
• Several readers who skimmed the underlying threads say the developer’s posts looked thoughtful but persistent, and that he misread the room and became adversarial.
• Others perceive deliberate mischaracterization: e.g., the SNL bullet is alleged to stretch a mild remark into “endorsing a slur.”
• Many complain that the council’s list has no direct links or quotes, making it impossible to judge context and inviting suspicion.

CoC, Inclusivity, and Free Expression

• One camp defends CoCs as necessary to avoid “useful assholes” dominating and to maintain a welcoming, legally safer, professional environment.
• Another camp sees modern CoCs as broad, political tools enabling “purity spirals,” grievance farming, and disproportionate targeting of eccentric, neurodivergent, or dissenting contributors.
• There is specific criticism of a steering member’s statement that if an enforcement action harms someone’s career, it is entirely their fault, with commenters calling this a “just world” assumption that denies possible process errors.

Impact on Python and Open Source

• Some potential or past contributors say this kind of drama has already led them to abandon Python-related work or leave Python governance spaces.
• Others argue for “vote with your feet” via forking, while several point out that successful forks are hard given Python’s ecosystem, corporate backing, and C API inertia.
• A recurring theme is that open source is “being professional in public”; several worry that the public, ambiguous punishment itself is reputationally damaging to both the individual and the project.