#28340: USE_THOUSAND_SEPARATOR=True causes primary key to include commas
-------------------------------------+-------------------------------------
Reporter: Zach Borboa | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Template system | Version: master
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Zach Borboa):
Can this behavior be documented with a note?
{{{
diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt
index 70402b1fc4..c5d83c38a8 100644
--- a/docs/ref/settings.txt
+++ b/docs/ref/settings.txt
@@ -2669,6 +2669,12 @@ format, it will have higher precedence and will
be applied instead.
See also :setting:`DECIMAL_SEPARATOR`, :setting:`NUMBER_GROUPING` and
:setting:`THOUSAND_SEPARATOR`.
+.. note::
+
+ Using ``{{ object.pk }}`` and ``{{ object.id }}`` may include
+ :setting:`THOUSAND_SEPARATOR`. Consider using {{
object.pk|unlocalize }}
+ instead.
+
.. setting:: USE_TZ
``USE_TZ``
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28340#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.4c4bc93ee116e2aef2510c24b54a375b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
