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:  assigned
Component:  Utilities|  Version:  master
 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 felixxm):

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

Re: [Django] #31470: Overflow not respected when using `` tag in `` in the admin site.

[Django]

#31470: Overflow not respected when using `` tag in `` in the 
admin
site.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, fieldset, | Triage Stage:  Accepted
  pre, overflow  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by felixxm):

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


Comment:

 Thanks, I reproduced this issue.

-- 
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.50feaaef6d6cc18d6148e4bf39cec959%40djangoproject.com.

Re: [Django] #31398: multiple_database.tests.AuthTestCase doesn't flush the default database if transactions aren't supported.

[Django]

#31398: multiple_database.tests.AuthTestCase doesn't flush the default database 
if
transactions aren't supported.
-+-
 Reporter:  Tim Graham   |Owner:  Hassaan
 |  Ali Wattoo
 Type:  Bug  |   Status:  assigned
Component:  Core (Other) |  Version:  master
 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 Simon Charette):

 Hassaan, you could try running the suite with MySQL's MyISAM to reproduce
 locally.

-- 
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.1cf25a4d45db07d34cccd40a91ea21c7%40djangoproject.com.

Re: [Django] #31398: multiple_database.tests.AuthTestCase doesn't flush the default database if transactions aren't supported.

[Django]

#31398: multiple_database.tests.AuthTestCase doesn't flush the default database 
if
transactions aren't supported.
-+-
 Reporter:  Tim Graham   |Owner:  Hassaan
 |  Ali Wattoo
 Type:  Bug  |   Status:  assigned
Component:  Core (Other) |  Version:  master
 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):

 This issue only affects databases that don't support transactions. I used
 [https://github.com/googleapis/python-spanner-django Cloud Spanner].

-- 
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.3392b1508528d5c392e954c7fc15dd61%40djangoproject.com.

Re: [Django] #31398: multiple_database.tests.AuthTestCase doesn't flush the default database if transactions aren't supported.

[Django]

#31398: multiple_database.tests.AuthTestCase doesn't flush the default database 
if
transactions aren't supported.
-+-
 Reporter:  Tim Graham   |Owner:  Hassaan
 |  Ali Wattoo
 Type:  Bug  |   Status:  assigned
Component:  Core (Other) |  Version:  master
 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 Hassaan Ali Wattoo):

 I'm having trouble duplicating this issue. Running the multiple_database
 test suite for the latest code on master results in no failures.

 {{{
 #!div style="font-size: 80%"
   {{{#!python
 .
 --
 Ran 77 tests in 0.366s
   }}}
 }}}

 Could you give us more information about how you reproduced this issue?
 (version of Django, operating system, steps to reproduce the issue)?
 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.7c69273a4f6c2f2e1d4ec3b4686489ef%40djangoproject.com.

Re: [Django] #31358: Increase default password salt size in BasePasswordHasher.

[Django]

#31358: Increase default password salt size in BasePasswordHasher.
--+
 Reporter:  Jon Moroney   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  Version:  master
 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 Jon Moroney):

 > Ok, next step would be to use those new `decode` methods in the existing
 cases where manual decoding happens (to reduce the duplication added by
 this method).

 I've updated the PR with what I think you mean by this for the pbkdf2
 hasher. Let me know if that's what you're thinking and I'll do the rest,
 else let me know what I misunderstood :)

 > Then the next step would be to look into where and how we can implement
 the update of the salt. Preferably without adding it to the `must_update`
 individually. We could add a `salt_length` attribute and then adjust based
 on that (which could be None for the unsalted variants).

 I think this can be handled in the BasePasswordHasher unless a hasher
 implements its own `must_update` logic and in that case it must be on a
 case by case basis. As for the salt length do you propose adding a
 `salt_length` field to the return from `decode`? I think it may just be
 easier to use `len(salt)` and handle the case where salt is `None`.

-- 
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.320ad761c8fb3bc40095ac8b116b7302%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:  assigned
Component:  Utilities|  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 Mariusz Felisiak ):

 In [changeset:"71c4fb7beb8e3293243140e4bd74e53989196440" 71c4fb7b]:
 {{{
 #!CommitTicketReference repository=""
 revision="71c4fb7beb8e3293243140e4bd74e53989196440"
 Refs #27468 -- Changed default Signer algorithm to SHA-256.
 }}}

-- 
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.22b0d54c1b8b7c5c54b8345e2363b469%40djangoproject.com.

Re: [Django] #31470: Overflow not respected when using `` tag in `` in the admin site.

[Django]

#31470: Overflow not respected when using `` tag in `` in the 
admin
site.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:  Uncategorized|   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, fieldset, | Triage Stage:
  pre, overflow  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by Nick Pope):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/12725 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/065.4154649bde9397bc747c1ddc7cdc0019%40djangoproject.com.

Re: [Django] #31470: Overflow not respected when using `` tag in `` in the admin site.

[Django]

#31470: Overflow not respected when using `` tag in `` in the 
admin
site.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:  Uncategorized|   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, fieldset, | Triage Stage:
  pre, overflow  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by Nick Pope):

 * Attachment "with-fix.png" 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.d9f938400c3f717c9c0c5d14c90bf2b2%40djangoproject.com.

Re: [Django] #31470: Overflow not respected when using `` tag in `` in the admin site.

[Django]

#31470: Overflow not respected when using `` tag in `` in the 
admin
site.
-+-
 Reporter:  Nick Pope|Owner:  Nick Pope
 Type:  Uncategorized|   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  admin, fieldset, | Triage Stage:
  pre, overflow  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by Nick Pope):

 * Attachment "without-fix.png" 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.a30c50a2f2e44b0bb2e8dea515efe8b0%40djangoproject.com.

[Django] #31470: Overflow not respected when using `` tag in `` in the admin site.

[Django]

#31470: Overflow not respected when using `` tag in `` in the 
admin
site.
-+-
   Reporter:  Nick Pope  |  Owner:  Nick Pope
   Type: | Status:  assigned
  Uncategorized  |
  Component: |Version:  master
  contrib.admin  |   Keywords:  admin, fieldset,
   Severity:  Normal |  pre, overflow
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  1  |
-+-
 When using the `` tag to render a read-only block of code/markup with
 syntax highlighting in a ``, overflow is not respected and the
 `` forces the `` to be wider.

 This can be resolved by setting `min-width: 0` on `fieldset` in CSS.

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

Re: [Django] #31441: TabluarInline will not auto unhide/expand when classes = ['collapse'] and there is error during the saving process in django admin

[Django]

#31441: TabluarInline will not auto unhide/expand when classes = ['collapse'] 
and
there is error during the saving process in django admin
-+-
 Reporter:  Jian |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  3.0
 Severity:  Normal   |   Resolution:
 Keywords:  admin.TabularInline  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Hasan Ramezani):

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

[Django] #31469: Custom lookup ignored inside built-in aggregation

[Django]

#31469: Custom lookup ignored inside built-in aggregation
-+-
   Reporter:  Oliver |  Owner:  nobody
  Ford   |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  3.0
  layer (models, ORM)|   Keywords:  custom
   Severity:  Normal |  lookup,aggregation
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 With a '[[https://docs.djangoproject.com/en/3.0/howto/custom-
 lookups/|custom lookup]]' such as:
 {{{
 @JSONField.register_lookup
 class JsonbArrayLength(models.Transform):
 output_field = models.IntegerField()
 lookup_name = "arraylen"
 function = "JSONB_ARRAY_LENGTH"
 }}}

 Using it as `qs.annotate(num_items=models.Sum("jsonfield__arraylen"))`
 results in the query fragment:
 {{{
 SELECT SUM("model"."jsonfield") AS "num_items"
 }}}

 i.e. the `arraylen` lookup is ignored/not done.
 `qs.values("jsonfield__arraylen")` works as expected.

 Modifying it to `models.Sum(JsonbArrayLength("jsonfield"))` gives the
 desired result.

-- 
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/049.a3a8301d2b3a87cf3552d8b9dfd8336c%40djangoproject.com.

Re: [Django] #31468: Move migration name suggestion from AutoDetector to operation classes

[Django]

#31468: Move migration name suggestion from AutoDetector to operation classes
-+-
 Reporter:  Adam (Chainz)|Owner:  nobody
  Johnson|
 Type:  New feature  |   Status:  assigned
Component:  Migrations   |  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 Adam (Chainz) Johnson):

 * stage:  Unreviewed => Accepted


Comment:

 Marking as impicitly accepted by previous GitHub 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/068.c8e778b1d9acb8d53096f16fa6db701a%40djangoproject.com.

Re: [Django] #31441: TabluarInline will not auto unhide/expand when classes = ['collapse'] and there is error during the saving process in django admin

[Django]

#31441: TabluarInline will not auto unhide/expand when classes = ['collapse'] 
and
there is error during the saving process in django admin
-+-
 Reporter:  Jian |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  3.0
 Severity:  Normal   |   Resolution:
 Keywords:  admin.TabularInline  | 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.e87dfe70e247e0a2577c92f6b7504678%40djangoproject.com.

Re: [Django] #31468: Move migration name suggestion from AutoDetector to operation classes

[Django]

#31468: Move migration name suggestion from AutoDetector to operation classes
-+-
 Reporter:  Adam (Chainz)|Owner:  nobody
  Johnson|
 Type:  New feature  |   Status:  assigned
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Adam (Chainz) Johnson):

 [PR](https://github.com/django/django/pull/12131)

 (I started this one just to add two methods and at Simon's suggestion, it
 grew.)

-- 
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.936df33a6c27cd45a4c2ca1ba79594df%40djangoproject.com.

[Django] #31468: Move migration name suggestion from AutoDetector to operation classes

[Django]

#31468: Move migration name suggestion from AutoDetector to operation classes
-+-
   Reporter:  Adam   |  Owner:  nobody
  (Chainz) Johnson   |
   Type:  New| Status:  assigned
  feature|
  Component: |Version:  master
  Migrations |
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Currently migration automatic names are generated in one method in the
 autodetector. This does not support all operation types, and has no way of
 being extended for custom operation types. This logic should be moved to
 the individual operations classes.

-- 
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/053.855bd25f00cd822f8e4e8aa6726c8473%40djangoproject.com.

Re: [Django] #31459: URL path parameter regex too lenient.

[Django]

#31459: URL path parameter regex too lenient.
-+-
 Reporter:  Adam (Chainz)|Owner:  Adam
  Johnson|  (Chainz) Johnson
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (URLs)  |  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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"4bb33bb07450ea9b623877417c28e6489246f51c" 4bb33bb0]:
 {{{
 #!CommitTicketReference repository=""
 revision="4bb33bb07450ea9b623877417c28e6489246f51c"
 Fixed #31459 -- Fixed handling invalid indentifiers in URL path
 conversion.

 This patch adjusted existing tests that used invalid identifiers.
 }}}

-- 
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.8fefdd362cb8758f8b6e3d7d6085667d%40djangoproject.com.

Re: [Django] #31450: Querying on ArrayField(PointField) returns string instead of list

[Django]

#31450: Querying on ArrayField(PointField) returns string instead of list
-+-
 Reporter:  Nitin Sangwan|Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  contrib.postgres |  Version:  3.0
 Severity:  Normal   |   Resolution:
 Keywords:  ArrayField,  | Triage Stage:  Accepted
  PointField |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report. Reproduced at
 578c03b276e435bcd3ce9eb17b81e85135c2d3f3 with the attached test case.

-- 
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.97da00868e01272e0bf1f85647dae9bd%40djangoproject.com.

Re: [Django] #31450: Querying on ArrayField(PointField) returns string instead of list

[Django]

#31450: Querying on ArrayField(PointField) returns string instead of list
-+-
 Reporter:  Nitin Sangwan|Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  contrib.postgres |  Version:  3.0
 Severity:  Normal   |   Resolution:
 Keywords:  ArrayField,  | Triage Stage:
  PointField |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * Attachment "postgis_tests.zip" added.

 Reproduce test case for #31450

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

Re: [Django] #31459: URL path parameter regex too lenient.

[Django]

#31459: URL path parameter regex too lenient.
-+-
 Reporter:  Adam (Chainz)|Owner:  Adam
  Johnson|  (Chainz) Johnson
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Core (URLs)  |  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 felixxm):

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

Re: [Django] #31223: Add __class_getitem__ to support runtime type parameters for some classes

[Django]

#31223: Add __class_getitem__ to support runtime type parameters for some 
classes
-+-
 Reporter:  Sobolev Nikita   |Owner:  Sobolev
 |  Nikita
 Type:  New feature  |   Status:  closed
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  types, mypy, | Triage Stage:  Ready for
  django-stubs   |  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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"578c03b276e435bcd3ce9eb17b81e85135c2d3f3" 578c03b]:
 {{{
 #!CommitTicketReference repository=""
 revision="578c03b276e435bcd3ce9eb17b81e85135c2d3f3"
 Fixed #31223 -- Added __class_getitem__() to Manager and QuerySet.
 }}}

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

Re: [Django] #31223: Add __class_getitem__ to support runtime type parameters for some classes

[Django]

#31223: Add __class_getitem__ to support runtime type parameters for some 
classes
-+-
 Reporter:  Sobolev Nikita   |Owner:  Sobolev
 |  Nikita
 Type:  New feature  |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  types, mypy, | Triage Stage:  Ready for
  django-stubs   |  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/066.2abdeaafcbb237610888f9a3bf446770%40djangoproject.com.

Re: [Django] #31459: URL path parameter regex too lenient.

[Django]

#31459: URL path parameter regex too lenient.
-+-
 Reporter:  Adam (Chainz)|Owner:  Adam
  Johnson|  (Chainz) Johnson
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Core (URLs)  |  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 felixxm):

 * type:  Bug => Cleanup/optimization


-- 
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.3d1811c2b31f88c348854d9c1238a1d7%40djangoproject.com.

Re: [Django] #27060: Take indexes into account in inspectdb command

[Django]

#27060: Take indexes into account in inspectdb command
-+-
 Reporter:  Akshesh Doshi|Owner:  Drew
 |  Winstel
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  db-indexes   | Triage Stage:  Accepted
  inspectdb  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * owner:  Pavel White => Drew Winstel


Comment:

 [https://github.com/django/django/pull/12712 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/062.85a521a8553136410af4222d994c43f1%40djangoproject.com.

Re: [Django] #31223: Add __class_getitem__ to support runtime type parameters for some classes

[Django]

#31223: Add __class_getitem__ to support runtime type parameters for some 
classes
-+-
 Reporter:  Sobolev Nikita   |Owner:  Sobolev
 |  Nikita
 Type:  New feature  |   Status:  assigned
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  types, mypy, | Triage Stage:  Accepted
  django-stubs   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by felixxm):

 * owner:  nobody => Sobolev Nikita
 * 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/066.f99a10b88f5cc2d8f190ab2c82136dc0%40djangoproject.com.

Re: [Django] #31268: Update Algerian Arabic (ar_DZ) locale formats.

[Django]

#31268: Update Algerian Arabic (ar_DZ) locale formats.
-+-
 Reporter:  infosrabah   |Owner:
 Type:   |  infosrabah
  Cleanup/optimization   |   Status:  closed
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  Date, Time,  | Triage Stage:  Accepted
  Datetime, ar, Algeria, DZ  |
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:"25afe59d342ac0fb77f523b8da42aa166c6e1503" 25afe59]:
 {{{
 #!CommitTicketReference repository=""
 revision="25afe59d342ac0fb77f523b8da42aa166c6e1503"
 Fixed #31268 -- Updated Algerian Arabic (ar_DZ) locale formats.
 }}}

-- 
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.2b10ba2764d446567e5e60d6cd53aeea%40djangoproject.com.

Re: [Django] #31466: A potential improvement in the Django template filter `escapejs`

[Django]

#31466: A potential improvement in the Django template filter `escapejs`
-+--
 Reporter:  Phithon  |Owner:  Phithon
 Type:  New feature  |   Status:  closed
Component:  Template system  |  Version:  3.0
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  escapejs | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by Phithon):

 Hi, thanks for your reply.

 In my option, the document and former ticket are talking about "HTML or
 JavaScript template literals", but the current context is "JavaScript
 string", seems like a bit different.

 Anyway, this ticket can help people who have bad programming practices
 although it was closed.

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

Re: [Django] #31451: Settings are cleaned insufficiently.

[Django]

#31451: Settings are cleaned insufficiently.
-+-
 Reporter:  Markus Holtermann|Owner:  Ichlasul
 Type:   |  Affan
  Cleanup/optimization   |   Status:  closed
Component:  Error reporting  |  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 Mariusz Felisiak ):

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


Comment:

 In [changeset:"3e7c39f710ec1895611fa1b337423742eebd0da1" 3e7c39f7]:
 {{{
 #!CommitTicketReference repository=""
 revision="3e7c39f710ec1895611fa1b337423742eebd0da1"
 Fixed #31451 -- Made settings cleansing work with list and tuple settings.
 }}}

-- 
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.0829693199712e61fac6a613ac288d55%40djangoproject.com.

Re: [Django] #31034: Add a navigation sidebar to the admin

[Django]

#31034: Add a navigation sidebar to the admin
---+---
 Reporter:  Tom Carrick|Owner:  Tom Carrick
 Type:  New feature|   Status:  assigned
Component:  contrib.admin  |  Version:  master
 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:  1
---+---
Changes (by Carlton Gibson):

 * needs_better_patch:  0 => 1


Comment:

 I posted to the mailing list thread to see if we can find a Design/UX/CSS
 expert to input on the PR.

 If not, I think we should proceed. It's a improvement, and we can iterate
 on it over time.

 There's one CSS issue that we should resolve (at least) commented on the
 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/065.de91b8e699e9f0927569928b2e0241ee%40djangoproject.com.

Re: [Django] #31451: Settings are cleaned insufficiently.

[Django]

#31451: Settings are cleaned insufficiently.
-+-
 Reporter:  Markus Holtermann|Owner:  Ichlasul
 Type:   |  Affan
  Cleanup/optimization   |   Status:  assigned
Component:  Error reporting  |  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 felixxm):

 * 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/065.dd399e92e667e8ff59a6d3250a15ce29%40djangoproject.com.

Re: [Django] #31462: Allow overridding widget in formfield_for_manytomany().

[Django]

#31462: Allow overridding widget in formfield_for_manytomany().
-+-
 Reporter:  007  |Owner:  007
 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:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"d51c50d836c5cf8db5566da17963f871be554615" d51c50d8]:
 {{{
 #!CommitTicketReference repository=""
 revision="d51c50d836c5cf8db5566da17963f871be554615"
 Fixed #31462 -- Allowed overriding autocomplete/raw_id_fields/filter
 widgets for ManyToManyFields with formfield_overrides.
 }}}

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

Re: [Django] #31462: Allow overridding widget in formfield_for_manytomany().

[Django]

#31462: Allow overridding widget in formfield_for_manytomany().
-+-
 Reporter:  007  |Owner:  007
 Type:   |   Status:  assigned
  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:  1|UI/UX:  0
-+-
Changes (by felixxm):

 * 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/064.2b9f5f500f58d649854e6ac5ca1d8ea3%40djangoproject.com.