diff options
| author | Mike Edmunds <medmunds@gmail.com> | 2026-04-17 10:16:37 -0700 |
|---|---|---|
| committer | nessita <124304+nessita@users.noreply.github.com> | 2026-04-24 12:22:34 -0300 |
| commit | 29eac2648cbc8f4000a391bf6424bc32979b0149 (patch) | |
| tree | 0634bb488f90ba9732c97f38f078392e22c66c03 /docs/ref/exceptions.txt | |
| parent | d24160ab4855f6971aa1f437720adca6330048a2 (diff) | |
Replaced references in docs to accepted PEPs with specific Python docs links.
Where the docs used `:pep:` links for established Python language
features, replaced them with direct references to the Python docs
(usually glossary terms).
Diffstat (limited to 'docs/ref/exceptions.txt')
| -rw-r--r-- | docs/ref/exceptions.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/ref/exceptions.txt b/docs/ref/exceptions.txt index 93c6ec4203..4ffff03457 100644 --- a/docs/ref/exceptions.txt +++ b/docs/ref/exceptions.txt @@ -285,9 +285,9 @@ The Django wrappers for database exceptions behave exactly the same as the underlying database exceptions. See :pep:`249`, the Python Database API Specification v2.0, for further information. -As per :pep:`3134`, a ``__cause__`` attribute is set with the original -(underlying) database exception, allowing access to any additional -information provided. +A :attr:`~BaseException.__cause__` attribute is set with the original +(underlying) database exception, allowing access to any additional information +provided. .. exception:: models.ProtectedError |