4 ms·
This is what not having sane BDFL does to organization. Only proper response is private email from sane BDFL similar to Linus email of "WE DON'T BREAK USERSPAC
by stackskipton 2y ago
This is what not having sane BDFL does to organization.
Only proper response is private email from sane BDFL similar to Linus email of "WE DON'T BREAK USERSPACE"
- Chris2048 2y agoThis is just a proposal though, having a (sane) BDFL needn't change anything.
- stackskipton 2y agoSane BDFL would have already stepped in with "Absolutely not" and PEP closed with "Will not implement" EDIT: Add on, Private Email to Pablo going "Dude, why are you purposing stuff that will break code spectacularly? I think we need to talk about your approach to language design."
- int_19h 2y agoThe community (including many of the maintainers) has spoken, and the PEP has been withdrawn, so apparently you don't need a BDFL for this.
- gklitz 2y agoThey are literally trying to depreciate a feature that regularly breaks user space because it’s unintentionally misused. I don’t think I’ve ever come across a use case where people actually intended to write a bare except. Anyone who ever does this are actually thinking that it’s effectively the same as “except Exception” which it isn’t, but that’s more obvious to most users.