Re: [Django] #30480: Discrepancy in `DateTime` field value If the django orm union() is used with the empty array in the filter.

[Django]

#30480: Discrepancy in `DateTime` field value If the django orm union() is used
with the empty array in the filter.
-+-
 Reporter:  Shashank Parekh  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * status:  new => closed
 * version:  2.1 => master
 * resolution:   => worksforme
 * severity:  Release blocker => Normal


Comment:

 Thanks for the report, however it contains a lot of gaps, e.g. `detail`
 model is not correct, ordering is not allowed in subqueries of compound
 statements (IMO it's not important) etc. Moreover it works for me in all
 described cases and with Django 2.1, 2.2 and on master. I tried to
 reproduce this issue with the following model
 {{{ #!python
 class Detail(models.Model):
   id = models.CharField(max_length=127, primary_key=True)
   date_field = models.DateTimeField(null=True)
   guid = models.CharField(null=True, max_length=127)
   mobile = models.CharField(null=True, max_length=127)

 >>> p = Detail.objects.filter(guid__in=[])
 >>> q = Detail.objects.filter(mobile__in=['8970405058'])
 >>> v = (p.union(q)).order_by('-date_field')
 >>> v[0].date_field
 datetime.datetime(2019, 5, 16, 19, 19, 7, 426452, tzinfo=)
 }}}

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.7a4ad8cf15728c6ab42bbb30f0074271%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30482: prefetch_related_objects evaluates queryset when checking for invalid prefetch ordering.

[Django]

#30482: prefetch_related_objects evaluates queryset when checking for invalid
prefetch ordering.
-+-
 Reporter:  Iain P. Watts|Owner:  Iain P.
 |  Watts
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"59ffafa1d2f466fa7aacbe74fe2787b2004b7871" 59ffafa1]:
 {{{
 #!CommitTicketReference repository=""
 revision="59ffafa1d2f466fa7aacbe74fe2787b2004b7871"
 Fixed #30482 -- Prevented unnecessary evaluation of lookup.queryset in
 prefetch_related_objects().
 }}}

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.b73dd4f8cfb8b3cafe01bc58dc9dba04%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30486: Custom aggregate function example needs updating for Django 2.2's `allow_distinct`

[Django]

#30486: Custom aggregate function example needs updating for Django 2.2's
`allow_distinct`
-+-
 Reporter:  Carlton Gibson   |Owner:
 |  Vyacheslav V.V.
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  2.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Vyacheslav V.V.):

 * needs_better_patch:  1 => 0


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.07004f50d0884bd8b24b0dcc23ff58ba%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30486: Custom aggregate function example needs updating for Django 2.2's `allow_distinct`

[Django]

#30486: Custom aggregate function example needs updating for Django 2.2's
`allow_distinct`
-+-
 Reporter:  Carlton Gibson   |Owner:
 |  Vyacheslav V.V.
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  2.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Vyacheslav V.V.):

 I have created [https://github.com/django/django/pull/11376 PR]

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.10c3181e1698aabe9ebc0fc2a0fd8915%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30486: Custom aggregate function example needs updating for Django 2.2's `allow_distinct`

[Django]

#30486: Custom aggregate function example needs updating for Django 2.2's
`allow_distinct`
+---
 Reporter:  Carlton Gibson  |Owner:  VVyacheslav
 Type:  Bug |   Status:  assigned
Component:  Documentation   |  Version:  2.2
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+---
Changes (by VVyacheslav):

 * status:  new => assigned
 * owner:  nobody => VVyacheslav


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.b33bc367dc861ec0946a0c8f1fa284f8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30475: Use of i18n_patterns and a buggy 404 template trigger internal server error without a backtrace

[Django]

#30475: Use of i18n_patterns and a buggy 404 template trigger internal server 
error
without a backtrace
-+--
 Reporter:  Erik Stein   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (URLs)  |  Version:  2.2
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Carlton Gibson):

 * status:  new => closed
 * resolution:   => needsinfo


Comment:

 Replying to [ticket:30475 Erik Stein]:
 > [draft bug report, I'll try to provide more details later or on request]

 Hi Erik.

 Happy to look at this but, as Claude says, could you provide a sample
 project the reproduces the issue?

 What **exactly** is the issue? An error in the 404 template? That i18n
 patterns swallows that? (Is it in fact dependent on i18n patterns?) And so
 on.

 Thanks.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.8637f5a45754c45081f4367dca2839f4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30481: Document that force_text() allows lone surrogates. (was: force_text() allows lone surrogates)

[Django]

#30481: Document that force_text() allows lone surrogates.
--+
 Reporter:  Adam Hooper   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  2.2
 Severity:  Normal|   Resolution:
 Keywords:  force_text unicode| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.9cc1ba426bded75e2d64991777d80cf0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30481: force_text() allows lone surrogates

[Django]

#30481: force_text() allows lone surrogates
--+
 Reporter:  Adam Hooper   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  2.2
 Severity:  Normal|   Resolution:
 Keywords:  force_text unicode| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Carlton Gibson):

 * component:  Utilities => Documentation
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 Replying to [comment:2 Adam Hooper]:

 > I'd be happy to compose a few sentences to clarify this in the docs.
 Where does this documentation belong?

 Hey Adam. Since you're happy to compose the patch, let's Accept this to
 see what you come up with. (I'm a bit _meh_ to be honest: this looks like
 more trouble that it's worth to explain but...)

 The place for it would be the
 
[https://docs.djangoproject.com/en/2.2/ref/utils/#django.utils.encoding.force_text
 `force_text()` docs].

 Thanks!

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.46e66ebdf4ca701534b5fca97ec518f1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30486: Custom aggregate function example needs updating for Django 2.2's `allow_distinct`

[Django]

#30486: Custom aggregate function example needs updating for Django 2.2's
`allow_distinct`
+
 Reporter:  Carlton Gibson  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Documentation   |  Version:  2.2
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+
Changes (by Carlton Gibson):

 * needs_better_patch:  0 => 1


-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.e1fdefb9700516ebec1807b0aa2fd214%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #30486: Custom aggregate function example needs updating for Django 2.2's `allow_distinct`

[Django]

#30486: Custom aggregate function example needs updating for Django 2.2's
`allow_distinct`
--+
   Reporter:  Carlton Gibson  |  Owner:  nobody
   Type:  Bug | Status:  new
  Component:  Documentation   |Version:  2.2
   Severity:  Normal  |   Keywords:
   Triage Stage:  Accepted|  Has patch:  1
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
 #28658 added the `Aggregate.allow_distinct` attribute. The example of the
 custom `Count` needs updating to use this.

 [https://github.com/django/django/pull/11373 PR] already begun.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/056.c374e3d9c950046a35739ac1a8fa8ff2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30484: Using RawSQL with CheckConstraint

[Django]

#30484: Using RawSQL with CheckConstraint
-+-
 Reporter:  David Sanders|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 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
-+-
Changes (by Simon Charette):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 It looks like this could be expressed as
 `Q(total__isnull=RawSQL('(total_last_updated IS NULL)')` but I haven't
 tested it.

 When #25367 lands it should even work without `RawSQL`:
 `Q(total__isnull=Q(total_last_updated__isnull=True))`.

 In the mean time if the above doesn't work I'd suggest you register
 [https://docs.djangoproject.com/en/2.2/howto/custom-lookups/ a custom
 Lookup] to express this filtering.

 {{{#!python
 from django.db.models.fields import Field
 from django.db.models import Lookup

 class IsNullEq(Lookup):
 lookup_name = 'isnulleq'

 def as_sql(self, compiler, connection):
 lhs, lhs_params = self.process_lhs(compiler, connection)
 rhs, rhs_params = self.process_rhs(compiler, connection)
 params = lhs_params + rhs_params
 return '(%s IS NULL) = (%s IS NULL)' % (lhs, rhs), params

 Field.register_lookup(IsNullEq)
 }}}

 And use it for your constraint's condition
 `Q(total__isnulleq=F('total_last_updated'))`.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.7de97acf8ce492c910a05c9028ccc74e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30483: Switch test requirements from psycopg2-binary package to pscyopg2

[Django]

#30483: Switch test requirements from psycopg2-binary package to pscyopg2
--+
 Reporter:  Jon Dufresne  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Testing framework |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Carlton Gibson ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"8076ae68c1842aec26cbab51dc8ab609fb135eb0" 8076ae68]:
 {{{
 #!CommitTicketReference repository=""
 revision="8076ae68c1842aec26cbab51dc8ab609fb135eb0"
 Fixed #30483 -- Switched test requirement to psycopg2 package.
 }}}

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.ccf47a348f29827a68fe1dd25e21bcdd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30481: force_text() allows lone surrogates

[Django]

#30481: force_text() allows lone surrogates
+--
 Reporter:  Adam Hooper |Owner:  nobody
 Type:  Uncategorized   |   Status:  new
Component:  Utilities   |  Version:  2.2
 Severity:  Normal  |   Resolution:
 Keywords:  force_text unicode  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Adam Hooper):

 That's fair; then perhaps there should be some documentation to that
 effect?

 Where I'm coming from: Postgres gave me an error when I tried to INSERT a
 string that was passed to my handler via JSON. It turns out Python's
 `json.loads()` can produce lone surrogates (because JSON can contain them
 -- https://bugs.python.org/issue17906); but Postgres TEXT (or JSON or
 JSONB) fields only store well-formed Unicode text. "I mustn't be the only
 person with this problem," I figured. I found `force_text()`. It looks
 like exactly the utility I need -- especially since it's littered all over
 the `django.db` package.

 Then I needed to learn that it wasn't.

 I ended up writing my own utility to replace surrogates. For anyone
 reading:

 {{{
 import re
 Surrogates = re.compile(r'[\ud800-\udfff]')
 def force_valid_text(text):
 return Surrogates.sub('\ufffd', text)
 }}}

 (I had to add `\u` to the regex, too, because Postgres doesn't allow
 that, either. But I feel that's a Postgres-specific issue, whereas the
 utility of `force_text()` is more general.)

 In the end, I wrote my own `force_text()` utility. It would have saved me
 some effort if the documentation had told me that `force_text()` wasn't
 what I want when preparing arbitrary input text for a database text field.

 I'd be happy to compose a few sentences to clarify this in the docs. Where
 does this documentation belong? I was startled when I learned Django can
 allow invalid-text `str` as input in perfectly ordinary usage; but it
 turns out it ''must'' because JSON allows them.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.3a6c78c7b75dffdb1483747562459bbd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #30485: Unexpected behavior for django.utils.http.urlencode

[Django]

#30485: Unexpected behavior for django.utils.http.urlencode
+
   Reporter:  jlubcke   |  Owner:  nobody
   Type:  Bug   | Status:  new
  Component:  Core (Other)  |Version:  2.2
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 The function django.utils.http.urlencode has been changed to give
 unexpected result for tuple values (and other iterable objects) in the
 case when no iterations is expected:
 {{{
 >>> django.utils.http.urlencode(dict(a=('a','b')), doseq=False)
 'a=%5B%27a%27%2C+%27b%27%5D'
 }}}

 One would expect the same as the standard library version (Note the first
 and last characters has been replaced by square brackets):
 {{{
 >>> urllib.parse.urlencode(dict(a=('a', 'b')), doseq=False)
 'a=%28%27a%27%2C+%27b%27%29'
 }}}

 If the value is a list, the result if what one would expect:
 {{{
 >>> django.utils.http.urlencode(dict(a=['a','b']), doseq=False)
 'a=%5B%27a%27%2C+%27b%27%5D'
 >>> urllib.parse.urlencode(dict(a=['a', 'b']), doseq=False)
 'a=%5B%27a%27%2C+%27b%27%5D'
 }}}

 Note: This is a problem when one has objects that has a `__str__` method
 defined, returning the value one would want to be in the urlencode result,
 but the object by coincidence is also iterable.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/050.7b7bcab19d7c2c19c4bcfc81c75b5515%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30484: Using RawSQL with CheckConstraint (was: Feature request: Using RawSQL with CheckConstraint)

[Django]

#30484: Using RawSQL with CheckConstraint
-+-
 Reporter:  David Sanders|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.78e3464c3191f4da142d09bbd00615ac%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30481: force_text() allows lone surrogates

[Django]

#30481: force_text() allows lone surrogates
+--
 Reporter:  Adam Hooper |Owner:  nobody
 Type:  Uncategorized   |   Status:  new
Component:  Utilities   |  Version:  2.2
 Severity:  Normal  |   Resolution:
 Keywords:  force_text unicode  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by Claude Paroz):

 I don't think that fixing unvalid unicode input is in the contract of
 `force_str`/`force_text`.

-- 
Ticket URL: 
Django 
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.9841593831507f0a06f7f5de4bb55c4d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.