It depends on the kind of groups/organizations you write code in. In some, I think such strong statements are necessary. You can mitigate the dangers of pickl

It depends on the kind of groups/organizations you write code in. In some, I think such strong statements are necessary. You can mitigate the dangers of pickle by educating junior devs or people new to python, by having a strong culture of code reviews with experienced reviewers, by having a style guide that explicitly prohibits pickle except in exceptional cases. ... Or you can just not use it in the first place and make it trivial for newcomers to your codebase to use safer serialization methods.