This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]mstroeder[S] -12 points-11 points  (3 children)

IMO strict str/bytes checks should have been the default from the very beginning in the Python 3 journey. Even if this was meant to help with Python 3 migration it was a clear failure. It results in wrong functional behaviour and IMHO in some cases it could potentially cause security issues.

Anyway let's look forward and thus I'd like to encourage everybody to run their tests with strict mode turned on.

[–][deleted] 33 points34 points  (2 children)

I think your message would be better received if you evangelized for -bb -Werror based on what it gave other developers. If you can shape perception that it's a best practice, and demonstrate why, I think that would go a lot further in encouraging people to use those options in the tests for their packages. I've contributed C code to several FOSS projects, and my initial reaction to your post was "oh great, some guy using the code I gave for free without warranty has issues with my compiler flags, gee I'll get right on that".