Re: [Django] #33514: Fallback to a more generic language variant for Select2 translations.

[Django]

#33514: Fallback to a more generic language variant for Select2 translations.
-+-
 Reporter:  David Glenck |Owner:  Mohamed
 Type:   |  Nabil Rady
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:  select2  | 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 Mariusz Felisiak):

 * 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/068.1c1980169537aaa96b29ac308b70749b%40djangoproject.com.

Re: [Django] #33520: "has_add_permission" for Django Admin error

[Django]

#33520: "has_add_permission" for Django Admin error
-+-
 Reporter:  John Raphael Medina  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  3.2
 Severity:  Normal   |   Resolution:  invalid
 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 Mariusz Felisiak):

 * resolution:  wontfix => 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/070.b21730fd3780e5c293bb38ffb575f137%40djangoproject.com.

Re: [Django] #33520: "has_add_permission" for Django Admin error

[Django]

#33520: "has_add_permission" for Django Admin error
-+-
 Reporter:  John Raphael Medina  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  3.2
 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 John Raphael Medina):

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


-- 
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/070.febde712c752519e332c0e6698206969%40djangoproject.com.

[Django] #33520: "has_add_permission" for Django Admin error

[Django]

#33520: "has_add_permission" for Django Admin error
-+
   Reporter:  joraphmedina   |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.admin  |Version:  3.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  |
-+
 Potential bug found in:
 
https://github.com/django/django/blob/stable/3.2.x/django/contrib/admin/options.py

 Kindly see error here (currently testing on our local):

 Request Method: GET
 Request URL:http://localhost:8000/admin/users/user/13/change/
 Django Version: 3.2.12
 Exception Type: TypeError
 Exception Value:
 has_add_permission() takes 2 positional arguments but 3 were given
 Exception Location: /usr/local/lib/python3.8/site-
 packages/django/contrib/admin/options.py, line 605, in
 get_inline_instances
 Python Executable:  /usr/local/bin/python
 Python Version: 3.8.12

-- 
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/055.0031b2fc8724a873caaa7eca3d26d688%40djangoproject.com.

Re: [Django] #33514: Fallback to a more generic language variant for Select2 translations.

[Django]

#33514: Fallback to a more generic language variant for Select2 translations.
-+-
 Reporter:  David Glenck |Owner:  Mohamed
 Type:   |  Nabil Rady
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:  select2  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mohamed Nabil Rady):

 * cc: Mohamed Nabil Rady (added)
 * owner:  nobody => Mohamed Nabil Rady
 * has_patch:  0 => 1
 * status:  new => assigned


Comment:

 https://github.com/django/django/pull/15438

-- 
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.9de4cdc053048a63d2e42392b8883192%40djangoproject.com.

Re: [Django] #33379: Add minimum database version checks

[Django]

#33379: Add minimum database version checks
-+-
 Reporter:  Tim Graham   |Owner:  Hasan
 |  Ramezani
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 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 Tim Graham):

 * 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.600c9f5460b0878312bfbd9aaf06e99a%40djangoproject.com.

Re: [Django] #28358: LazyObject defines attribute that don't exist on wrapped object

[Django]

#28358: LazyObject defines attribute that don't exist on wrapped object
-+-
 Reporter:  Andrey Fedoseev  |Owner:  Theofilos
 |  Alexiou
 Type:  Bug  |   Status:  closed
Component:  Utilities|  Version:  1.11
 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
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"b2ed0d78f2dff9986ef15b9098c1b6d9ce720a99" b2ed0d78]:
 {{{
 #!CommitTicketReference repository=""
 revision="b2ed0d78f2dff9986ef15b9098c1b6d9ce720a99"
 Refs #28358 -- Fixed infinite recursion in LazyObject.__getattribute__().

 Regression in 97d7990abde3fe4b525ae83958fd0b52d6a1d13f.

 Co-authored-by: Mariusz Felisiak 
 Co-authored-by: Theo Alexiou 
 }}}

-- 
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/072.f12f2db654a1e6ac37a8f5cd83c18c4d%40djangoproject.com.

Re: [Django] #33519: Recursive {% include %} crashes silently. (was: include X in X leads to silent crash)

[Django]

#33519: Recursive {% include %} crashes silently.
-+-
 Reporter:  Brambor  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  3.2
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  template include | Triage Stage:
  crash  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * status:  new => closed
 * resolution:   => wontfix
 * type:  Uncategorized => Bug
 * component:  Core (Management commands) => Template system


Comment:

 Thanks for the report. On Django 4.0 it crashes with `RecursionError:
 maximum recursion depth exceeded` and on Django 3.2 it crashes with:
 {{{
 Fatal Python error: Cannot recover from stack overflow.
 Python runtime state: initialized

 Current thread 0x7f8e7a566700 (most recent call first):
 
 }}}
 It seems to have been accidentally improved in
 854e9b066850b9b4eb1171966e996322b2c16d27. Unfortunately, Django 3.2 is in
 extended support and doesn't receive bugfixes anymore (except security
 issues and data loss bugs).

-- 
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.92e3fc1aaf535b88603c1088e9de71d7%40djangoproject.com.

[Django] #33519: include X in X leads to silent crash

[Django]

#33519: include X in X leads to silent crash
-+-
   Reporter:  Brambor|  Owner:  nobody
   Type: | Status:  new
  Uncategorized  |
  Component:  Core   |Version:  3.2
  (Management commands)  |   Keywords:  template include
   Severity:  Normal |  crash
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 index.html
 {{{
 {% load static %}

 {% include "index.html" %}
 }}}

 view:
 {{{
 def index(request, **kwargs):
 template = loader.get_template('index.html')

 return HttpResponse(template.render({}, request))
 }}}

 `url(r'^index$', index)` is in urlpatterns in urls.py

 When running the server with
 `python manage.py runserver`
 and accessing `http://localhost:8000/index`
 The server just stops, not printing anything

 cmd line looks like this:
 {{{
 >>>python manage.py runserver
 Watching for file changes with StatReloader
 Performing system checks...

 System check identified no issues (0 silenced).
 February 17, 2022 - 11:33:10
 Django version 3.2.12, using settings 'settings'
 Starting development server at http://127.0.0.1:8000/
 Quit the server with CTRL-BREAK.

 >>>
 }}}

 I also tried `python manage.py runserver -v 3`, which too didn't print
 anything.

 If I have seen a simple "Ran out of memory" Exception or something, it
 would occur to me that I did include X in X. Without that error message, I
 wondered, whether the issue is that something is called `index` and that
 word is reserved somewhere.

-- 
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/050.a70b5180974df489952e65779e13c2d1%40djangoproject.com.

Re: [Django] #33518: Add alias RemovedAfterNextVersionWarning for deprecations after next version

[Django]

#33518: Add alias RemovedAfterNextVersionWarning for deprecations after next
version
-+-
 Reporter:  Shai Berger  |Owner:
 Type:   |  Saidblanchette
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  dev
 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
-+-

Comment (by Mariusz Felisiak):

 > So now we go with  the name `RemovedAfterNextVersionWarning` ?.

 Yes.

-- 
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/063.6303123e2ba3e4f80fc795ff6a4da898%40djangoproject.com.

Re: [Django] #33518: Add alias RemovedAfterNextVersionWarning for deprecations after next version

[Django]

#33518: Add alias RemovedAfterNextVersionWarning for deprecations after next
version
-+-
 Reporter:  Shai Berger  |Owner:
 Type:   |  Saidblanchette
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Other) |  Version:  dev
 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
-+-

Comment (by Saidblanchette):

 Replying to [comment:5 Mariusz Felisiak]:
 > Replying to [comment:4 Shai Berger]:
 > > Replying to [comment:2 Mariusz Felisiak]:
 > > > I'm not sure about the name. What do you think about
 `RemovedInVersionAfterNextWarning`?
 > >
 > > I started with `RemovedInNextNextVersionWarning` and changed it when I
 realized that is incorrect for x.0 versions (the pending-deprecation
 warning is not about the x.2 version, but about the (x+1).0 version). As
 far as my English goes, that also disqualifies
 `RemovedInVersionAfterNextWarning`.
 >
 > Right 

 So now we go with  the name `RemovedAfterNextVersionWarning` ?.
 
 Thank you  Shai Berger .

-- 
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/063.519f04845542af0dee6ae0a0a776bced%40djangoproject.com.

Re: [Django] #27468: Move utils.crypto.salted_hmac() from SHA1 toward SHA256

[Django]

#27468: Move utils.crypto.salted_hmac() from SHA1 toward SHA256
-+-
 Reporter:  Tim Graham   |Owner:  Claude
 Type:   |  Paroz
  Cleanup/optimization   |   Status:  closed
Component:  Utilities|  Version:  dev
 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
-+-

Comment (by GitHub ):

 In [changeset:"a94ae4cb11b2b6a6fffb26f5a2dfd0c665e2070d" a94ae4cb]:
 {{{
 #!CommitTicketReference repository=""
 revision="a94ae4cb11b2b6a6fffb26f5a2dfd0c665e2070d"
 Refs #27468 -- Updated django.core.signing docstring.

 Follow up to 71c4fb7beb8e3293243140e4bd74e53989196440.
 }}}

-- 
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.558c59d3381e3a554abd68a5f23dec5f%40djangoproject.com.

Re: [Django] #33517: Extracting seconds also returns fractional seconds on PostgreSQL. (was: Implied behavior of `__second` extractor inside of `F()` expressions does not match documented behavior for

[Django]

#33517: Extracting seconds also returns fractional seconds on PostgreSQL.
-+-
 Reporter:  Joey Lange   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * component:  Documentation => Database layer (models, ORM)
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report! We should have consistent behavior on all backends.
 What do you think about adding `DATE_TRUNC()` in this case? For example:
 {{{#!diff
 diff --git a/django/db/backends/postgresql/operations.py
 b/django/db/backends/postgresql/operations.py
 index 399c1b24e7..fd90b95fb8 100644
 --- a/django/db/backends/postgresql/operations.py
 +++ b/django/db/backends/postgresql/operations.py
 @@ -36,6 +36,8 @@ class DatabaseOperations(BaseDatabaseOperations):
  return "EXTRACT('isodow' FROM %s)" % field_name
  elif lookup_type == 'iso_year':
  return "EXTRACT('isoyear' FROM %s)" % field_name
 +elif lookup_type == 'second':
 +return f"EXTRACT('second' FROM DATE_TRUNC('second',
 {field_name}))"
  else:
  return "EXTRACT('%s' FROM %s)" % (lookup_type, field_name)


 }}}

-- 
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/069.858fcfd60c1dc379bd27ee321642d604%40djangoproject.com.

Re: [Django] #33496: Auto database mirroring.

[Django]

#33496: Auto database mirroring.
-+-
 Reporter:  M Hadi Azarabad  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  multi-database / | Triage Stage:
  mirror database|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Steven Mapes):

 Following on from Mariusz's reply with the Postgres reference on HA, load
 balancing and replication here's [https://dev.mysql.com/doc/refman/8.0/en
 /replication-solutions.html MySQL's replication solutions]  and
 [https://downloads.mysql.com/docs/mysql-proxy-en.pdf MySQL Proxy] which
 can be used as  load balancer to distribute requests and perform automatic
 failover, here's a [https://www.digitalocean.com/community/tutorials/how-
 to-use-proxysql-as-a-load-balancer-for-mysql-on-ubuntu-16-04 Digital Ocean
 install guide] for the latter.

 If you are using MariaDB then here's the [https://mariadb.com/kb/en
 /standard-replication/ replication docs] to get you started.

 If you are looking at Multi-Master using either then look into
 [https://galeracluster.com/ Galera Cluster] but these will be better
 solutions than writing twice from code

-- 
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.6f23ceeade4cdc9f5b2df2892dc88a19%40djangoproject.com.