Re: [Django] #31039: Support __contained_by lookup for AutoFields and BigAutoFields.

[Django]

#31039: Support __contained_by lookup for AutoFields and BigAutoFields.
-+-
 Reporter:  Bolay Michael|Owner:  Hasan
 |  Ramezani
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Hasan Ramezani):

 * owner:  nobody => Hasan Ramezani
 * status:  new => assigned


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.bb6b6f0d2851729d7bf774cc9184297e%40djangoproject.com.

Re: [Django] #24991: Range types not properly converted to SQL in QuerySet.query.__str__()

[Django]

#24991: Range types not properly converted to SQL in QuerySet.query.__str__()
-+-
 Reporter:  Villiers Strauss |Owner:  Dmitry
 |  Dygalo
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  1.8
 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 Claude Paroz):

 * needs_better_patch:  1 => 0


Comment:

 I tried to fix errors in [https://github.com/django/django/pull/12156 that
 PR]. I'm not very proud of those regex testing, but well, it works...

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.f8673fd73a668814d1cdeeb9134a72c0%40djangoproject.com.

Re: [Django] #30255: docutils reports an error rendering view docstring when the first line is not empty

[Django]

#30255: docutils reports an error rendering view docstring when the first line 
is
not empty
-+-
 Reporter:  Manlio Perillo   |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  assigned
Component:  contrib.admindocs|  Version:  3.0
 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 Baptiste Mispelon):

 * has_patch:  0 => 1
 * version:  2.1 => 3.0


Comment:

 After a bit of trial and error, I finally managed to reproduce the issue
 on current master with an up-to-date version of `docutils`.

 The trick was to use a docstring like this: `"firstline\n\nsecond
 line"` and not the one mentioned in the original report.

 I took Simon's suggestion from comment 2 and removed `trim_docstring` in
 favor of `inspect.cleandoc` and it fixes the issue.

 [https://github.com/django/django/pull/12155 PR here]

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.13e03c216219d9def269a1a8d41c46e3%40djangoproject.com.

Re: [Django] #29262: Custom Left Outer Join in Queries

[Django]

#29262: Custom Left Outer Join in Queries
-+-
 Reporter:  Sassan Haradji   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM Join | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by frnhr):

 * cc: frnhr (added)


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.e233d1dc3b99a41fb4f3abbed27d2faf%40djangoproject.com.

Re: [Django] #28404: Django admin empty_value/empty_value_display doesn't check for empty strings

[Django]

#28404: Django admin empty_value/empty_value_display doesn't check for empty
strings
-+-
 Reporter:  Mark Koh |Owner:  Nazarov
 |  Georgiy
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  empty value display  | Triage Stage:  Accepted
  admin charfield|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Sardorbek Imomaliev):

 * cc: Sardorbek Imomaliev (added)


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.0c08dc30b45c9ab65f91399acea0d018%40djangoproject.com.

Re: [Django] #29892: Multiple Selenium test failures in Firefox

[Django]

#29892: Multiple Selenium test failures in Firefox
-+-
 Reporter:  Tom Forbes   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * stage:  Accepted => Ready for checkin


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.fffca84617a365b27ad3a0c46e3b7c3c%40djangoproject.com.

Re: [Django] #23919: Cleanups for when we drop Python 2 compatibility

[Django]

#23919: Cleanups for when we drop Python 2 compatibility
--+
 Reporter:  Tim Graham|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Carlton Gibson ):

 In [changeset:"86a0231e0a087d4b909f76223cc55d5bbb673930" 86a0231e]:
 {{{
 #!CommitTicketReference repository=""
 revision="86a0231e0a087d4b909f76223cc55d5bbb673930"
 Refs #23919 -- Replaced super(...) with super() in metaclasses.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.8c246390dd3697aefd418aaafca3bbb5%40djangoproject.com.

Re: [Django] #29892: Multiple Selenium test failures in Firefox

[Django]

#29892: Multiple Selenium test failures in Firefox
---+
 Reporter:  Tom Forbes |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 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 Carlton Gibson):

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


Comment:

 Ooops. I should have updated the commit message on
 875e3ff4fd883e11008ca9dfcf02b8314c57c0a6 to be `Refs`.
 [https://github.com/django/django/pull/12152 PR12152] is still incoming.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.329158f4f9f51de6463c41ddae8ecc09%40djangoproject.com.

Re: [Django] #31028: Use JavaScript classList API

[Django]

#31028: Use JavaScript classList API
-+-
 Reporter:  Jon Dufresne |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
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:"46a0edc3ba6c40d685b9d128c5f6d8723f9659ca" 46a0edc3]:
 {{{
 #!CommitTicketReference repository=""
 revision="46a0edc3ba6c40d685b9d128c5f6d8723f9659ca"
 Fixed #31028 -- Used classList API to check, add and remove DOM classes.

 Thanks to Claude Paroz for review.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.40f56eed0616122de0bed391f4854073%40djangoproject.com.

Re: [Django] #31042: Rewrite AdminSeleniumTestCase.get_css_value() without jQuery.

[Django]

#31042: Rewrite AdminSeleniumTestCase.get_css_value() without jQuery.
-+-
 Reporter:  Jon Dufresne |Owner:  Jon
 Type:   |  Dufresne
  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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"c8bd37a8606a89b6e09854ab5f3bbaa98e849408" c8bd37a8]:
 {{{
 #!CommitTicketReference repository=""
 revision="c8bd37a8606a89b6e09854ab5f3bbaa98e849408"
 Fixed #31042 -- Removed AdminSeleniumTestCase.get_css_value() in favor of
 Selenium .is_displayed().

 All instances of AdminSeleniumTestCase.get_css_value() were used to
 inspect the display property.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.c4f669fba714d91882344f866742d9dd%40djangoproject.com.

Re: [Django] #31028: Use JavaScript classList API

[Django]

#31028: Use JavaScript classList API
-+-
 Reporter:  Jon Dufresne |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Claude Paroz):

 * stage:  Accepted => Ready for checkin


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.08023dc4a802223ca3b98f317ac6a296%40djangoproject.com.

Re: [Django] #29262: Custom Left Outer Join in Queries

[Django]

#29262: Custom Left Outer Join in Queries
-+-
 Reporter:  Sassan Haradji   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM Join | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ivan Zaikin):

 * cc: Ivan Zaikin (added)


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.28d0de7f720cf170c3f9c11c2116ca89%40djangoproject.com.

Re: [Django] #29262: Custom Left Outer Join in Queries

[Django]

#29262: Custom Left Outer Join in Queries
-+-
 Reporter:  Sassan Haradji   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM Join | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Alexandr Artemyev):

 I believe my case relates to this issue.

 I have a user model and a second model like this

 {{{
 class SecondModel(models.Model):
 date = models.DateField()
 from_member = models.ForeignKey(User, models.CASCADE, '+',)
 to_member = models.ForeignKey(User, models.CASCADE, '+')
 first_value = models.IntegerField(default=0)
 second_value = models.IntegerField(default=0)
 }}}


 I want to left join this subquery with the User model on `id=target`:
 {{{
 subquery = (
 SecondModel.objects.filter(
 Q(from_member=self.user) | Q(to_member=self.user),
 date__gte=start_date, date__lte=end_date,
 ).annotate(
 target=Case(When(Q(from_member=self.user),
 then=F('to_member_id')), default=F('from_member_id')),
 ).values('target').annotate(
 sum_first_value=Sum('first_value'),
 sum_second_value=Sum('second_value'),
 total=F('sum_first_value') + F('sum_second_value'),
 )
 )
 }}}


 I imagine it somehow like this:

 {{{
 qs = User.objects.annotate(subquery=subquery)
 }}}
 After that filter/exclude/order_by features should work.
 Also I should have access to fields like
 qs[0].subquery_first_value/qs[0].subquery_second_value

 Here is an example SQL query that I want to be generated:
 {{{
 SELECT "users".*, "subquery".*
 FROM "users"
 LEFT OUTER JOIN
   (SELECT CASE
   WHEN "second_model"."from_member_id" = 7 THEN
 "second_model"."to_member_id"
   ELSE "second_model"."from_member_id"
   END AS "target",
   SUM("second_model"."first_value") AS "sum_first_value",
   SUM("second_model"."second_value") AS "sum_second_value",
FROM "second_model"
WHERE ("second_model"."from_member_id" = 7
   OR "second_model"."to_member_id" = 7) -- also the condition for
 date on start and end
GROUP BY CASE
 WHEN "second_model"."from_member_id" = 7 THEN
 "second_model"."to_member_id"
 ELSE "second_model"."from_member_id"
 END) subquery ON ("users"."id" = subquery."target")
 WHERE "users"."id" = 502
 }}}

 I found a solution that resolves my problem:
 https://stackoverflow.com/a/42816689/5628843
 using CustomJoin helps me, but to access values i need to use extra, and
 this code doesn’t look very nice

 {{{
 join_to(Users, subquery, 'id', 'target', queryset, 'subquery').extra(
 select={
 field_name: f'COALESCE({field_name}, 0)'
 for field_name in (
 'sum_first_value',
 'sum_second_value',
 )
 }
 )
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.8df639bc920e71c8e134507f1c929e83%40djangoproject.com.

Re: [Django] #29262: Custom Left Outer Join in Queries

[Django]

#29262: Custom Left Outer Join in Queries
-+-
 Reporter:  Sassan Haradji   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM Join | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Alexandr Artemyev):

 * cc: Alexandr Artemyev (added)


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.c21e7a283cb57156fe84cf28f4d21cbd%40djangoproject.com.

Re: [Django] #31021: 0011_update_proxy_permissions crashes in multi database environment.

[Django]

#31021: 0011_update_proxy_permissions crashes in multi database environment.
-+
 Reporter:  haudoing |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  contrib.auth |  Version:  2.2
 Severity:  Release blocker  |   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 felixxm):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/12153 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.d32d48629919975fcf1cb8bba0e4d9cf%40djangoproject.com.

Re: [Django] #30974: Selenium asserts should be wait statements

[Django]

#30974: Selenium asserts should be wait statements
-+-
 Reporter:  Johannes Hoppe   |Owner:  Johannes
 |  Hoppe
 Type:  Bug  |   Status:  closed
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 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:  assigned => closed
 * resolution:   => duplicate


Comment:

 So let's call this a duplicate of #29892, where this is being addressed.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.358eb45cbe9d5adc5369e5c07e22d720%40djangoproject.com.

Re: [Django] #29892: Multiple Selenium test failures in Firefox

[Django]

#29892: Multiple Selenium test failures in Firefox
---+
 Reporter:  Tom Forbes |Owner:  nobody
 Type:  Bug|   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:"875e3ff4fd883e11008ca9dfcf02b8314c57c0a6" 875e3ff4]:
 {{{
 #!CommitTicketReference repository=""
 revision="875e3ff4fd883e11008ca9dfcf02b8314c57c0a6"
 Fixed #29892 -- Added .wait_page_loaded() in
 SeleniumTests.test_first_field_focus().
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.b812dfafe0b05d52154dfc05e6b4c7da%40djangoproject.com.

Re: [Django] #31037: Template truncatechars dots missing.

[Django]

#31037: Template truncatechars dots missing.
-+--
 Reporter:  老广 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  2.2
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  truncatechars| 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
 * resolution:   => invalid


Comment:

 Thanks for the report, however, translations are handled at
 
[https://docs.djangoproject.com/en/dev/internals/contributing/localizing/#translations.
 Transifex] and not in this tracker.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.922c7c30dd2376440a5a95c815b25e49%40djangoproject.com.

Re: [Django] #31037: Template truncatechars dots missing.

[Django]

#31037: Template truncatechars dots missing.
-+--
 Reporter:  老广 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  2.2
 Severity:  Normal   |   Resolution:
 Keywords:  truncatechars| Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by 老广):

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


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.5291cfbcab8be091b300129d3e842b33%40djangoproject.com.

Re: [Django] #31037: Template truncatechars dots missing.

[Django]

#31037: Template truncatechars dots missing.
-+--
 Reporter:  老广 |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  2.2
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  truncatechars| Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by 老广):

 Replying to [comment:1 felixxm]:
 > `truncatechars` now uses the real ellipsis character (…) instead of 3
 dots, this is a
 [https://docs.djangoproject.com/en/2.2/releases/2.2/#miscellaneous
 documented] and expected change.
 >
 > `{{ "Hello Django" | truncatechars:10 }}` returns `Hello Dja…` for me.

 I found the bug, It's because the Django locale zh-hans Lost the ellipsis


 > #, python-format
 > msgctxt "String to return when truncating text"
 > msgid "%(truncated_text)s…"
 > msgstr "%(truncated_text)s"


 
https://github.com/django/django/blob/stable/2.2.x/django/conf/locale/zh_Hans/LC_MESSAGES/django.po#L1048

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.97e964197f20fcd5f3bba56f66b6f993%40djangoproject.com.

Re: [Django] #29892: Multiple Selenium test failures in Firefox

[Django]

#29892: Multiple Selenium test failures in Firefox
---+
 Reporter:  Tom Forbes |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  master
 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
---+

Comment (by Carlton Gibson ):

 In [changeset:"f0ed38edf33947fad539d43b7b3fbabf82816518" f0ed38ed]:
 {{{
 #!CommitTicketReference repository=""
 revision="f0ed38edf33947fad539d43b7b3fbabf82816518"
 Refs #29892 -- Replaced Selenium .submit() shim with .click() on the
 submit button.

 There is no WebDriver submit primitive. The Selenium project implements
 it as a convenience only. The geckodriver developers recommend against
 using it. Replace it with a real primitive, click on the submit button.

 Fixes failing Seleninum test test_date_time_picker_shortcuts when using
 the Firefox Selenium driver.
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/061.881f877573cabf91d98ce3bd542ade54%40djangoproject.com.