(prepep) Preventing future issues with warnings as errors

[sirosen (Stephen Rosen)]

@mikeshardmind

Something that was proposed in that thread that sort of slipped by in much of the frustration was the potential for a core developer endorsed lint configuration that was tailored for things that are known common footguns, and a way to easily ship this with the interpreter, but as a seperate tool the interpreter runs (Even if it runs it by default to help those who don’t know to know to turn it on), not as part of the interpreter core itself.

For whatever it’s worth, I noticed this and it reminded me of this thread.
My opinions haven’t changed much since last year, but I didn’t feel that there wasn’t any signal that CPython devs wanted to add something.

I’m not game to start a new project right now but if nobody else acts first, I don’t mind starting to prove it out on PyPI.

---

I support the ideas in the OP here. They don’t seem that controversial and they leave room for features to be flagged as warning-worthy without breaking anyone for using those behaviors.

Of course, some teams will treat all such warnings as errors and forbid such usages. That is their prerogative and it shouldn’t impact the overall community judgement that some things are dangerous if used improperly but useful when used correctly.