Re: [Django] #33481: Clarify remove_stale_contenttypes data loss warning

[Django]

#33481: Clarify remove_stale_contenttypes data loss warning
-+-
 Reporter:  Johannes Maron   |Owner:  Syed
 Type:   |  Waheed
  Cleanup/optimization   |   Status:  assigned
Component:   |  Version:  dev
  contrib.contenttypes   |
 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
-+-

Comment (by Mariusz Felisiak):

 Replying to [comment:6 Syed Waheed]:
 > link to my fork - https://github.com/Waheedsys/django
 > link to my commit -
 https://github.com/django/django/compare/main...Waheedsys:django:main
 > I would like to have a review of the changes

 Please send a patch via GitHub PR (check out
 [https://docs.djangoproject.com/en/5.0/internals/contributing/writing-code
 /working-with-git/#publishing-work docs] for more details).

-- 
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/0107018ce2ca682c-92634db1-f68f-4ae1-8c6e-9860c9bd19ce-00%40eu-central-1.amazonses.com.

Re: [Django] #33481: Clarify remove_stale_contenttypes data loss warning

[Django]

#33481: Clarify remove_stale_contenttypes data loss warning
-+-
 Reporter:  Johannes Maron   |Owner:  Syed
 Type:   |  Waheed
  Cleanup/optimization   |   Status:  assigned
Component:   |  Version:  dev
  contrib.contenttypes   |
 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
-+-

Comment (by Syed Waheed):

 link to my fork - https://github.com/Waheedsys/django
 link to my commit -
 https://github.com/django/django/compare/main...Waheedsys:django:main
 I would like to have a review of the changes

-- 
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/0107018ce2c7832e-3c0783d7-58b5-42a7-89ca-637c8b173288-00%40eu-central-1.amazonses.com.

Re: [Django] #35091: Allow use of ipaddress standard library module with django.contrib.gis.geoip2

[Django]

#35091: Allow use of ipaddress standard library module with
django.contrib.gis.geoip2
---+-
 Reporter:  Nick Pope  |Owner:  Nick Pope
 Type:  New feature|   Status:  closed
Component:  GIS|  Version:  dev
 Severity:  Normal |   Resolution:  fixed
 Keywords:  geoip2, ipaddress  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"cc56c22a24ef717cc3111e92ca146136fa518d55" cc56c22a]:
 {{{
 #!CommitTicketReference repository=""
 revision="cc56c22a24ef717cc3111e92ca146136fa518d55"
 Fixed #35091 -- Allowed GeoIP2 querying using IPv4Address/IPv6Address.
 }}}

-- 
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/0107018ce2c7124e-3fc8bafb-ff7a-49f7-bd1d-3ecf4213ecad-00%40eu-central-1.amazonses.com.

Re: [Django] #16752: Multi-db without a 'default' database

[Django]

#16752: Multi-db without a 'default' database
-+-
 Reporter:  Jeremy Dunck |Owner:  Ryan
 |  Cheley
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.3
  (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
-+-

Comment (by Tim Graham):

 Option one, although the database shouldn't be treated as the default.
 Instead the developer must route each query as explained in the ticket
 description. Comment 2 describe the issue and the potential roadblocks
 fairly well. I think it will be difficult. Trying to solve #13528 could be
 a first step.

-- 
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/0107018ce11ddfcd-c86ea952-e0ce-4f6c-8d92-68181c4c7909-00%40eu-central-1.amazonses.com.

Re: [Django] #16752: Multi-db without a 'default' database

[Django]

#16752: Multi-db without a 'default' database
-+-
 Reporter:  Jeremy Dunck |Owner:  Ryan
 |  Cheley
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.3
  (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
-+-

Comment (by Ryan Cheley):

 I've been poking around on this ticket and I'm not sure if the intention
 here is to allow a user to specify the name of the default database, that
 is allow this code to work (where `core` is ANY name other than `default`)

 {{{
 DATABASES = {
 'core': {
 'ENGINE': 'django.db.backends.sqlite3',
 'NAME': BASE_DIR / 'db.sqlite3',
 }
 }
 }}}

 OR

 allow the `DATABASES` setting to have an empty dictionary, that is

 {{{
 DATABASES = {}
 }}}

 and if it is set to empty, it assumes what is currently in the
 `settings.py` file by default, that is

 {{{
 DATABASES = {
 'default': {
 'ENGINE': 'django.db.backends.sqlite3',
 'NAME': BASE_DIR / 'db.sqlite3',
 }
 }
 }}}

 I think it's the first, but before I get too much further I wanted to add
 this comment.

-- 
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/0107018ce087f3c9-0bb1e525-72f1-4abd-9b55-20f21e3ecc6e-00%40eu-central-1.amazonses.com.

Re: [Django] #23557: Prevent silent extension of explicit GROUP BY when using order_by

[Django]

#23557: Prevent silent extension of explicit GROUP BY when using order_by
-+-
 Reporter:  Brian May|Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.7
  (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 Ryan Cheley):

 * owner:  Ryan Cheley => (none)
 * status:  assigned => new


-- 
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/0107018ce044d953-c777fa86-f3ed-4467-8bb2-e7ca46ce02b6-00%40eu-central-1.amazonses.com.

Re: [Django] #23557: Prevent silent extension of explicit GROUP BY when using order_by

[Django]

#23557: Prevent silent extension of explicit GROUP BY when using order_by
-+-
 Reporter:  Brian May|Owner:  Ryan
 |  Cheley
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.7
  (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 Ryan Cheley):

 * owner:  nobody => Ryan Cheley
 * 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/0107018ce044270b-bfe3d2cb-50e9-485a-ae71-a8b94ab7fc35-00%40eu-central-1.amazonses.com.

Re: [Django] #14831: Django Template Style Guide

[Django]

#14831: Django Template Style Guide
-+-
 Reporter:  Simon Meers  |Owner:  Ryan
 |  Cheley
 Type:  New feature  |   Status:  assigned
Component:  Documentation|  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  template, style, | Triage Stage:  Accepted
  format |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Ryan Cheley):

 After reviewing the html files this is what I've found:

 False positives from the script above

 * `./contrib/admindocs/templates/admin_doc/bookmarklets.html` has inline
 javascript on line 22 which is the source of:

 ||= Count =||= Symbol =||
 || 2 || {al ||
 || 1 || {if ||
 || 1 || {re ||
 || 1 || {vi ||
 || 1 || {x= ||

 * `./contrib/admindocs/templates/admin_doc/template_filter_index.html`
 line 23 which is triggering the {"|. This seems to fall outside of the
 requirements for this ticket
 * `./contrib/admindocs/templates/admin_doc/template_tag_index.html` line
 23 which is triggering the {"|. This seems to fall outside of the
 requirements for this ticket
 * `./forms/jinja2/django/forms/widgets/multiwidget.html` line ` has `{%-`.
 Per the [https://jinja.palletsprojects.com/en/3.1.x/templates/#whitespace-
 control jinja2 docs] this is in place for whitespace control

 Files where the standard isn't being followed

 * `./views/templates/technical_500.html` on line 157 has
 `{{server_time|date:"r"}}`

 Based on these findings it seems that the docs that are currently written
 are being enforced.

 Next steps:

 - review `extends` and `load` tag placement
 - placement of HTML in `block`
 - indentation practices for code inside of `block`

-- 
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/0107018ce03efbba-420cae61-d9cf-4b12-b47c-3118680a0a57-00%40eu-central-1.amazonses.com.

Re: [Django] #35091: Allow use of ipaddress standard library module with django.contrib.gis.geoip2 (was: Support use of ipaddress standard library module with django.contrib.gis.geoip2)

[Django]

#35091: Allow use of ipaddress standard library module with
django.contrib.gis.geoip2
---+-
 Reporter:  Nick Pope  |Owner:  Nick Pope
 Type:  New feature|   Status:  assigned
Component:  GIS|  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords:  geoip2, ipaddress  | 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):

 * stage:  Unreviewed => Accepted


-- 
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/0107018ce01e2f63-fac831db-e6f9-459f-ab27-61d204d83652-00%40eu-central-1.amazonses.com.

Re: [Django] #35092: Expose additional data in responses from geoip2 queries.

[Django]

#35092: Expose additional data in responses from geoip2 queries.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  geoip2   | 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):

 * stage:  Unreviewed => Accepted


-- 
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/0107018ce00045e4-50e14967-e541-4fae-8d00-19e82578b02c-00%40eu-central-1.amazonses.com.

Re: [Django] #14831: Django Template Style Guide

[Django]

#14831: Django Template Style Guide
-+-
 Reporter:  Simon Meers  |Owner:  Ryan
 |  Cheley
 Type:  New feature  |   Status:  assigned
Component:  Documentation|  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:  template, style, | Triage Stage:  Accepted
  format |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Ryan Cheley):

 I ran the following bash command (which is returning some false positives,
 for example `{al` is finding an inline javascrpt alert) to get a sense of
 what is current in the `django/django` directory

 {{{
 find django/django -type f -name "*.html" -exec grep -E
 "(\{\{[^}]*\}\})|(\{%[^%]*%\})" {} + | grep -o -E "\{.." | sort | uniq -c
 }}}

 This gives the following usages

 {{

 ||= Count =||= Symbol =||
 ||724 || {{ ||
 || 2 || {"| ||
 || 2 || {al ||
 || 1 || {if ||
 || 1 || {re ||
 || 1 || {vi ||
 || 1 || {x= ||
 || 1 || {{s ||

 {%

 ||= Count =||= Symbol =||
 || 2121 || {% ||
 || 1 || {%- ||

 For the items that don't conform to `{{` or `{%` I'll look more deeply at
 the occurrences and provide more context for them, but on initial review
 it seems that the preference / standard seems to be `{{` or `{%` followed
 by a space

-- 
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/0107018cdfca14dd-d1eca040-15fb-43dc-b1ad-6d7ea9607462-00%40eu-central-1.amazonses.com.

Re: [Django] #35092: Expose additional data in responses from geoip2 queries.

[Django]

#35092: Expose additional data in responses from geoip2 queries.
-+--
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  geoip2   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Nick Pope):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/17706 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/0107018cdfc9fafb-9f9ae574-e56b-4258-b773-156ff47fafd9-00%40eu-central-1.amazonses.com.

[Django] #35092: Expose additional data in responses from geoip2 queries.

[Django]

#35092: Expose additional data in responses from geoip2 queries.
---+---
   Reporter:  Nick Pope|  Owner:  Nick Pope
   Type:  New feature  | Status:  assigned
  Component:  GIS  |Version:  dev
   Severity:  Normal   |   Keywords:  geoip2
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+---
 I'd like to expose some of the data missing in the responses returned for
 both country and city queries.

 For country responses, we should return `continent_code`,
 `continent_name`, and `is_in_european_union`'''^1^'''.

 For city responses, we should return `accuracy_radius` and `region_name`.
 We should also rename `region` to `region_code` and `dma_code`'''^2^''' to
 `metro_code`. ''(In my initial patch I've kept the old names around for
 backward compatibility, but perhaps we should deprecate those keys?)''

 
 '''^1^''' ''This was already added for city responses in #30447.''
 '''^2^''' ''IIRC this is an old name for `metro_code` that was used in the
 old v1 of the GeoIP library...''

-- 
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/0107018cdfc3024f-f6df99ed-1155-47cc-9639-12dac39c5f4b-00%40eu-central-1.amazonses.com.

Re: [Django] #35091: Support use of ipaddress standard library module with django.contrib.gis.geoip2

[Django]

#35091: Support use of ipaddress standard library module with
django.contrib.gis.geoip2
---+--
 Reporter:  Nick Pope  |Owner:  Nick Pope
 Type:  New feature|   Status:  assigned
Component:  GIS|  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords:  geoip2, ipaddress  | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Nick Pope):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/17705 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/0107018cdfae3e05-67012b09-44b5-463d-9bb9-7c9ce5dbc792-00%40eu-central-1.amazonses.com.

[Django] #35091: Support use of ipaddress standard library module with django.contrib.gis.geoip2

[Django]

#35091: Support use of ipaddress standard library module with
django.contrib.gis.geoip2
---+---
   Reporter:  Nick Pope|  Owner:  Nick Pope
   Type:  New feature  | Status:  assigned
  Component:  GIS  |Version:  dev
   Severity:  Normal   |   Keywords:  geoip2, ipaddress
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+---
 It currently isn't possible to pass an `ipaddress.IPv4Address` or
 `ipaddress.IPv6Address` when querying using `django.contrib.gis.geoip2`.

 I propose to make it possible to pass in these types without the need to
 coerce them to strings.

-- 
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/0107018cdfacfc57-9cbf5543-02f8-4d7c-9a7a-ba10bd49adfe-00%40eu-central-1.amazonses.com.

Re: [Django] #16752: Multi-db without a 'default' database

[Django]

#16752: Multi-db without a 'default' database
-+-
 Reporter:  Jeremy Dunck |Owner:  Ryan
 |  Cheley
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.3
  (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
-+-

Comment (by Ryan Cheley):

 Replying to [comment:6 Natalia Bidart]:

 Sounds good. I'll get to working on this 😀

 > Hey Ryan, while I agree that the docs have changed/improved, I think
 this ticket is about doing the cleanup to actually remove the need to
 declare a `default` database (which should also avoid the need to define a
 `default` key, even if empty, in the `DATABASES` dict).
 >
 > So from my understanding, this ticket is still valid and needs
 addressing.

-- 
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/0107018cdf716eec-46ba5992-978a-4e4a-8005-d884cbc5ba96-00%40eu-central-1.amazonses.com.

Re: [Django] #35088: Add support for ST_Collect on MySQL 8.0.24+.

[Django]

#35088: Add support for ST_Collect on MySQL 8.0.24+.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:  New feature  |   Status:  closed
Component:  GIS  |  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  st_collect,  | Triage Stage:  Accepted
  collect, aggregate, mysql, gis |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by GitHub ):

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


Comment:

 In [changeset:"53fc6ac64976a7693d2272050a03b71e56b16578" 53fc6ac]:
 {{{
 #!CommitTicketReference repository=""
 revision="53fc6ac64976a7693d2272050a03b71e56b16578"
 Fixed #35088 -- Added support for Collect on MySQL 8.0.24+.
 }}}

-- 
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/0107018cdf1a281c-f4728441-256c-45a1-b56e-f5bfa62d46f4-00%40eu-central-1.amazonses.com.

Re: [Django] #35090: Enforce uniqueness on custom path converters

[Django]

#35090: Enforce uniqueness on custom path converters
-+-
 Reporter:  Adam Johnson |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (URLs)  |  Version:  dev
 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
-+-
Changes (by Mariusz Felisiak):

 * type:  Bug => Cleanup/optimization


Comment:

 As for it's a cleanup not a bug. If someone registers converters with the
 same name as builtin converters, they will get what they deserve. What if
 they do it on purpose?

-- 
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/0107018cded10b64-f7ba5cb3-b04b-4f67-a1ff-d8d1eab7cb3e-00%40eu-central-1.amazonses.com.

Re: [Django] #35090: Enforce uniqueness on custom path converters

[Django]

#35090: Enforce uniqueness on custom path converters
--+--
 Reporter:  Adam Johnson  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (URLs)   |  Version:  dev
 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
--+--

Comment (by Salvo Polizzi):

 I've submitted a PR for this bug:
 https://github.com/django/django/pull/17703

-- 
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/0107018cde50d236-d08807ea-1850-4c4b-9c67-5bdf600ccedc-00%40eu-central-1.amazonses.com.