PEP 675: Mark malicious code example with red sidebar#3574
Uh oh!
There was an error while loading. Please reload this page.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.




Fixespython/docs-community#22.
As suggested by @encukou in python/docs-community#22, the dangerous "naive" SQL code could do with a red marker.
Regarding accessibility, similar to #3567, we're not relying on colour to convey meaning, it's also there in the text. ✅
Are there any examples in this PEP that could benefit from a red or green (or even yellow) sidebar? Perhaps the "written safely" one immediately after could be green?
Also remove the redundant headers.
📚 Documentation preview 📚: https://pep-previews--3574.org.readthedocs.build/