Skip to content

bpo-45677: Reword first section of sqlite3 docs #29326

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
willingc merged 14 commits into from
Nov 15, 2021
Merged

bpo-45677: Reword first section of sqlite3 docs #29326

Changes from 1 commit
Commits
Show all changes
14 commits
Select commit Hold shift + click to select a range
af15b22
bpo-45677: Avoid addressing the reader as 'you' in sqlite3 docs
Oct 29, 2021
c1e758d
Adjust wording
Oct 29, 2021
204052c
Adjust wording again
Oct 29, 2021
02d2a53
Typo
Oct 29, 2021
15008ee
Update Doc/library/sqlite3.rst
Oct 31, 2021
4d53130
Address review: adjust wording
Oct 31, 2021
f5ce4af
Update Doc/library/sqlite3.rst
Oct 31, 2021
e9c3e97
Update Lib/sqlite3/__init__.py
Oct 31, 2021
86efc85
Update Doc/library/sqlite3.rst
Oct 31, 2021
6923fee
Update Doc/library/sqlite3.rst
Oct 31, 2021
c794d16
Update Lib/sqlite3/__init__.py
Oct 31, 2021
f405915
Update Doc/library/sqlite3.rst
Oct 31, 2021
d451f9d
Apply Alex' suggestion, and apply 80 char limit to PR
Oct 31, 2021
9bd8121
Minor adjustment
Oct 31, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update Doc/library/sqlite3.rst 
Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com>
  • Loading branch information
@AlexWaygood
Erlend Egeberg Aasland and AlexWaygood authored Oct 31, 2021
commit f4059152b40a2c3da2b2011d23bcf0a045e80aa2
6 changes: 3 additions & 3 deletions Doc/library/sqlite3.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,9 +73,9 @@ This example uses the iterator form::

.. _sqlite3-placeholders:

SQL operations will usually need to use values from Python variables. It is poor
practice to assemble queries using Python's string operations, because they are
vulnerable to SQL injection attacks (see the `xkcd webcomic
SQL operations usually need to use values from Python variables. However,
beware of using Python's string operations to assemble queries, as they
are vulnerable to SQL injection attacks (see the `xkcd webcomic
<https://xkcd.com/327/>`_ for a humorous example of what can go wrong)::

# Never do this -- insecure!
Expand Down