diff options
| author | Rida Zouga <96395950+ZougaRida@users.noreply.github.com> | 2025-11-30 08:29:43 +0100 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2025-11-30 08:30:30 +0100 |
| commit | 9cfdab2e8d1fbd973e23765a98a06d3f7146e871 (patch) | |
| tree | dec14d7c0109502252dbf7e35e5a2d522e2a1259 | |
| parent | d17e646fe5020eeeb3a0e0c5f5983f15a0342429 (diff) | |
[6.0.x] Added link to Python Pickle documentation in docs/topics/cache.txt.
Co-authored-by: Rida Zouga <ridazouga@gmail.com>
Backport of 3ea0195ca57790d7bd6921ecaa32312eabec78d0 from main
| -rw-r--r-- | docs/topics/cache.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt index 990ce8f25c..563ab3837f 100644 --- a/docs/topics/cache.txt +++ b/docs/topics/cache.txt @@ -863,8 +863,8 @@ For cases like this, Django exposes a low-level cache API. You can use this API to store objects in the cache with any level of granularity you like. You can cache any Python object that can be pickled safely: strings, dictionaries, lists of model objects, and so forth. (Most common Python objects can be -pickled; refer to the Python documentation for more information about -pickling.) +pickled; refer to the :mod:`Python documentation <pickle>` for more information +about pickling.) Accessing the cache ------------------- |