Re: [Django] #32539: Support accessing the current filtered queryset from within SimpleListFilter.lookups()

2023-02-02 Thread Django 
#32539: Support accessing the current filtered queryset from within
SimpleListFilter.lookups()
+---
 Reporter:  Simon Willison  |Owner:  Sarah Boyce
 Type:  New feature |   Status:  assigned
Component:  contrib.admin   |  Version:  3.1
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+---
Changes (by Mariusz Felisiak):

 * 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/010701861610c2a3-cf42cdd9-7b1d-4d2e-b21d-7a860b218aa2-00%40eu-central-1.amazonses.com.

Re: [Django] #34259: Management command subparsers don’t retain error formatting

2023-02-02 Thread Django 
#34259: Management command subparsers don’t retain error formatting
-+-
 Reporter:  Adam Johnson |Owner:  Adam
 |  Johnson
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  dev
  commands)  |
 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:"beaa5f31e1e97bbde83a609c4b143193899f79ff" beaa5f3]:
 {{{
 #!CommitTicketReference repository=""
 revision="beaa5f31e1e97bbde83a609c4b143193899f79ff"
 [4.2.x] Fixed #34259 -- Passed called_from_command_line to command
 subparsers.

 Backport of 017fa23d3b0aee9142f531c2a0002fc86c82a54c from main
 }}}

-- 
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/01070186160e4b18-12509392-c719-41e2-b362-98d70069838a-00%40eu-central-1.amazonses.com.

Re: [Django] #34259: Management command subparsers don’t retain error formatting

2023-02-02 Thread Django 
#34259: Management command subparsers don’t retain error formatting
-+-
 Reporter:  Adam Johnson |Owner:  Adam
 |  Johnson
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  dev
  commands)  |
 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:"017fa23d3b0aee9142f531c2a0002fc86c82a54c" 017fa23]:
 {{{
 #!CommitTicketReference repository=""
 revision="017fa23d3b0aee9142f531c2a0002fc86c82a54c"
 Fixed #34259 -- Passed called_from_command_line to command subparsers.
 }}}

-- 
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/01070186160e0491-9fd005cd-ea46-49e1-9ea6-1ef2ae9807c4-00%40eu-central-1.amazonses.com.

Re: [Django] #33638: Saving unique geography fields crashes in the admin on PostGIS.

2023-02-02 Thread Django 
#33638: Saving unique geography fields crashes in the admin on PostGIS.
--+---
 Reporter:  Sebastian Clarke  |Owner:  Jacob Walls
 Type:  Bug   |   Status:  assigned
Component:  GIS   |  Version:  3.2
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+---
Changes (by Mariusz Felisiak):

 * 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/0107018615ef32b1-d58b7b0c-5c44-471f-9ec0-da8cdebfdc62-00%40eu-central-1.amazonses.com.

Re: [Django] #34259: Management command subparsers don’t retain error formatting

2023-02-02 Thread Django 
#34259: Management command subparsers don’t retain error formatting
-+-
 Reporter:  Adam Johnson |Owner:  Adam
 |  Johnson
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  dev
  commands)  |
 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 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/0107018615dce4e8-576aaa47-df67-4c34--cce003eef8d0-00%40eu-central-1.amazonses.com.

Re: [Django] #34308: Create Serializers for models (was: Feature request: Create Serializers for models)

2023-02-02 Thread Django 
#34308: Create Serializers for models
-+-
 Reporter:  Hemed Tov|Owner:  Hemed Tov
 Type:  New feature  |   Status:  closed
Component:  Core |  Version:  dev
  (Serialization)|
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  Serializer, Model| 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):

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


Comment:

 Hi, thanks for the proposition, however I'm not sure what kind of
 serialization you expect from `ModelSerializer` if it's similar to what
 `django-rest-framework` does then it's a duplicate of #32362. I will treat
 this report as a request for a new management command. I don't see this as
 something Django needs to provide and `ModelSerializer` is not a part of
 Django.

-- 
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/0107018615b9621b-c954ea2b-9c97-4a5f-8ee0-ce916ec0c0a4-00%40eu-central-1.amazonses.com.

Re: [Django] #22492: provide a way to prevent database queries on model objects

2023-02-02 Thread Django 
#22492: provide a way to prevent database queries on model objects
-+-
 Reporter:  Chris Jerdonek   |Owner:  Raúl
 |  Cumplido
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  model,queryset,defer,only  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Andrea F):

 I want a feature that is similar to what was original described but for a
 different use case: I have a Celery task that needs a model object in the
 state it was when the task was enqueued, ''not'' in a state reflecting the
 corresponding database row(s) when the task is processed. I pass the
 object to the Celery task by serializing the entity (using
 `django.serializers`) and saving exactly the information I want to make
 available to the task.

 This object model has complex inner workings and multiple foreign keys. I
 want to be able to use the object model functionality and custom logic we
 have implemented in the model class, but I do _not_ want it reading (or
 writing) anything from the database after deserialization in the Celery
 task.

 For this I want something less "smart" than a feature that knows about
 `only` and `defer` and `QuerySet` objects. For this I want to be able to
 set a flag on an object that would disable any further database
 interactions originating from that object.

-- 
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/01070186145d3438-b3970cc6-dc39-43dc-b83d-f57113c05572-00%40eu-central-1.amazonses.com.

[Django] #34308: Feature request: Create Serializers for models

2023-02-02 Thread Django 
#34308: Feature request:  Create Serializers for models
-+-
   Reporter:  Hemedbz|  Owner:  Hemedbz
   Type:  New| Status:  assigned
  feature|
  Component:  Core   |Version:  dev
  (Serialization)|
   Severity:  Normal |   Keywords:  Serializer, Model
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 - Provide CLI to generate corresponding serializers for existing models
 - The serializers will be in a seperate module named model_serializers.py,
 and the serializers module will import from that.
 - The default serializer for each model will include as fields all db
 column names.
 - The serializer default name will be the name of the model and serializer

 Example:

 {{{
 #!python
 class Coffee(models.Model):
type = models.Charfield(db_column='type')
roast_degree = models.IntegerFIeld(db_column='roast_degree)
temperature = models.IntegerFIeld(db_column='temperature')

class Meta:
  db_table = 'coffee'
 }}}

 After running the function:
 {{{
 #!python
 class CoffeeSerializer(serializers.ModelSerializer):
 class Meta:
   model = Coffee
   fields = [
'type',
'roast_degree',
'temperature',
 ]

 }}}

-- 
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/0107018613edbc7a-cc0adfa3-e3f6-4b93-a3d4-a34347d55f4d-00%40eu-central-1.amazonses.com.

Re: [Django] #34259: Management command subparsers don’t retain error formatting

2023-02-02 Thread Django 
#34259: Management command subparsers don’t retain error formatting
-+-
 Reporter:  Adam Johnson |Owner:  Adam
 |  Johnson
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  dev
  commands)  |
 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 Johnson):

 * needs_tests:  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/01070186136414c0-45d2a62b-6647-4f6c-a6a1-1459ce7842f6-00%40eu-central-1.amazonses.com.

Re: [Django] #33638: Saving unique geography fields crashes in the admin on PostGIS.

2023-02-02 Thread Django 
#33638: Saving unique geography fields crashes in the admin on PostGIS.
--+---
 Reporter:  Sebastian Clarke  |Owner:  Jacob Walls
 Type:  Bug   |   Status:  assigned
Component:  GIS   |  Version:  3.2
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+---
Changes (by Jacob Walls):

 * 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/010701861324ee92-6b9723f8-1551-41af-a466-0abf5ad4ded6-00%40eu-central-1.amazonses.com.

Re: [Django] #14810: Admin inline templates need blocks

2023-02-02 Thread Django 
#14810: Admin inline templates need blocks
-+-
 Reporter:  Simon Meers  |Owner:
 |  abdulrahman
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  template, block, | Triage Stage:  Accepted
  inheritance|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by abdulrahman):

 * owner:  Simon Meers => abdulrahman
 * 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/0107018612ce2342-bb985dd1-0b0b-4fae-bbd3-a14546ce08c9-00%40eu-central-1.amazonses.com.

Re: [Django] #33638: Saving unique geography fields crashes in the admin on PostGIS.

2023-02-02 Thread Django 
#33638: Saving unique geography fields crashes in the admin on PostGIS.
--+---
 Reporter:  Sebastian Clarke  |Owner:  Jacob Walls
 Type:  Bug   |   Status:  assigned
Component:  GIS   |  Version:  3.2
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+---
Changes (by Jacob Walls):

 * needs_better_patch:  0 => 1


Comment:

 A MySQL issue to look into.

-- 
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/0107018612c3a4e6-6577440b-9e5b-4eb9-bc2c-4a29b05cd8e2-00%40eu-central-1.amazonses.com.

Re: [Django] #33638: Saving unique geography fields crashes in the admin on PostGIS.

2023-02-02 Thread Django 
#33638: Saving unique geography fields crashes in the admin on PostGIS.
--+---
 Reporter:  Sebastian Clarke  |Owner:  Jacob Walls
 Type:  Bug   |   Status:  assigned
Component:  GIS   |  Version:  3.2
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+---
Changes (by Jacob Walls):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/16519 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/0107018612c14721-8715f314-4a17-4bc1-a64c-625b877b98ae-00%40eu-central-1.amazonses.com.

Re: [Django] #34286: Mixed-case views/templates names causes 404 on :view:/:template: directive.

2023-02-02 Thread Django 
#34286: Mixed-case views/templates names causes 404 on :view:/:template: 
directive.
-+-
 Reporter:  Alex Life|Owner:  Rahmat
 |  Faisal
 Type:  Bug  |   Status:  closed
Component:  contrib.admindocs|  Version:  4.1
 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:"db0e10c03735820aa64e46f015ac04657416f1bb" db0e10c]:
 {{{
 #!CommitTicketReference repository=""
 revision="db0e10c03735820aa64e46f015ac04657416f1bb"
 [4.2.x] Fixed #34286 -- Fixed admindocs markups for case-sensitive
 template/view names.

 Backport of 1250483ebf73f7a82ff820b94092c63ce4238264 from main
 }}}

-- 
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/0107018612634e4e-95fbe35d-5e1f-48c6-a207-ff59ac007a51-00%40eu-central-1.amazonses.com.

Re: [Django] #34286: Mixed-case views/templates names causes 404 on :view:/:template: directive.

2023-02-02 Thread Django 
#34286: Mixed-case views/templates names causes 404 on :view:/:template: 
directive.
-+-
 Reporter:  Alex Life|Owner:  Rahmat
 |  Faisal
 Type:  Bug  |   Status:  closed
Component:  contrib.admindocs|  Version:  4.1
 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:"1250483ebf73f7a82ff820b94092c63ce4238264" 1250483]:
 {{{
 #!CommitTicketReference repository=""
 revision="1250483ebf73f7a82ff820b94092c63ce4238264"
 Fixed #34286 -- Fixed admindocs markups for case-sensitive template/view
 names.
 }}}

-- 
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/010701861262f94f-bbb94d02-998b-420a-b8a2-baac2138afa2-00%40eu-central-1.amazonses.com.

Re: [Django] #34045: Admin changelist checkboxes do not have labels

2023-02-02 Thread Django 
#34045: Admin changelist checkboxes do not have labels
---+---
 Reporter:  Tom Carrick|Owner:  Durval Carvalho
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  dev
 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:  1
---+---
Changes (by Sarah Abderemane):

 * cc: Sarah Abderemane (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/01070186122d5de2-05b84b19-82c9-4bbc-9c68-bf13c042f74a-00%40eu-central-1.amazonses.com.

Re: [Django] #34286: Mixed-case views/templates names causes 404 on :view:/:template: directive.

2023-02-02 Thread Django 
#34286: Mixed-case views/templates names causes 404 on :view:/:template: 
directive.
-+-
 Reporter:  Alex Life|Owner:  Rahmat
 |  Faisal
 Type:  Bug  |   Status:  assigned
Component:  contrib.admindocs|  Version:  4.1
 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 Mariusz Felisiak):

 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0
 * 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/01070186120fd73d-179c9bb3-b0fd-478a-b85e-f62c78c6fd40-00%40eu-central-1.amazonses.com.

Re: [Django] #27079: Refactor LiveServerPort tests to not make extra calls to setUpClass() and tearDownClass()

2023-02-02 Thread Django 
#27079: Refactor LiveServerPort tests to not make extra calls to setUpClass() 
and
tearDownClass()
-+-
 Reporter:  Chris Jerdonek   |Owner:  Jacob
 Type:   |  Walls
  Cleanup/optimization   |   Status:  closed
Component:  Testing framework|  Version:  1.10
 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:"534895f1ace819053f28463fd62b833ba2ced829" 534895f]:
 {{{
 #!CommitTicketReference repository=""
 revision="534895f1ace819053f28463fd62b833ba2ced829"
 [4.0.x] Fixed thread termination in servers.tests.LiveServerPort on Python
 < 3.10.9.

 TestCase.doClassCleanups() cannot be called on Python < 3.10.9 because
 setUpClass()/tearDownClass() are called multiple times in
 LiveServerTestCase tests (refs #27079).
 }}}

-- 
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/01070186120c4c99-b8ee5bb5-cef5-4800-97ac-8c3caf7de1f4-00%40eu-central-1.amazonses.com.

Re: [Django] #7430: Recursively iterating through a template's nodes

2023-02-02 Thread Django 
#7430: Recursively iterating through a template's nodes
-+-
 Reporter:  miracle2k|Owner:  Anders
 |  Hovmöller
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Anders Hovmöller):

 Just FYI I have working code for walking the syntax tree:
 https://github.com/boxed/okrand/blob/main/okrand/__init__.py#L262

 It's... not ideal as it requires two monkey patches that I've found so
 far. But I personally don't think having `__iter__` on stuff is very
 useful. There are multiple child nodelists, so iter would be a little
 weird honestly.

-- 
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/0107018612037250-8de01e58-eb1f-430d-af5d-876aa1c2e23e-00%40eu-central-1.amazonses.com.

Re: [Django] #7430: Recursively iterating through a template's nodes

2023-02-02 Thread Django 
#7430: Recursively iterating through a template's nodes
-+-
 Reporter:  miracle2k|Owner:  Anders
 |  Hovmöller
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * owner:  nobody => Anders Hovmöller
 * 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/0107018611da4642-24be2b6d-8ad6-4854-9108-3b25e8406853-00%40eu-central-1.amazonses.com.

Re: [Django] #7430: Recursively iterating through a template's nodes

2023-02-02 Thread Django 
#7430: Recursively iterating through a template's nodes
-+-
 Reporter:  miracle2k|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * status:  closed => new
 * resolution:  needsinfo =>
 * needs_tests:  1 => 0
 * stage:  Design decision needed => Ready for checkin


Comment:

 As per a [https://github.com/django/django/pull/16473 much later report
 via a PR], `Template.__iter__()` looks broken:

 {{{
 >>> from django.template import Template
 >>> t = Template('Hello, world!')
 >>> next(iter(t))
 ...
 TypeError: 'TextNode' object is not iterable
 }}}

 > I don't recall whether this was by design. Does any Django code actually
 *use* this iter behavior?

 According to the test suite, it doesn't.

 I think this can just be removed (as per 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/0107018611da084d-6d6bace0-9149-4c73-912e-bc50af333bfd-00%40eu-central-1.amazonses.com.

Re: [Django] #31885: Update SMTP Email Backend to use an SSLContext.

2023-02-02 Thread Django 
#31885: Update SMTP Email Backend to use an SSLContext.
---+-
 Reporter:  Luis Saavedra  |Owner:  Luis Saavedra
 Type:  Bug|   Status:  closed
Component:  Core (Mail)|  Version:  dev
 Severity:  Normal |   Resolution:  fixed
 Keywords:  SSL| 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):

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


Comment:

 > ...override the ssl_context property to use custom crt/key files.

 The `ssl_context` still uses the settings, so not sure they need to
 subclass even.
 (I still we expose too much of `smtplib` through the settings here, but
 progress there is likely Jacob's proposal from https://groups.google.com/g
 /django-developers/c/R8ebGynQjK0/m/kc-zggaxAgAJ)

 I agree the narrow ticket here was resolved in
 2848e5d0ce5cf3c31fe87525536093b21d570f69. 

-- 
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/0107018611aa7692-09ee60b5-36b6-468d-97d0-3739d1cf8963-00%40eu-central-1.amazonses.com.

Re: [Django] #31885: Update SMTP Email Backend to use an SSLContext.

2023-02-02 Thread Django 
#31885: Update SMTP Email Backend to use an SSLContext.
---+-
 Reporter:  Luis Saavedra  |Owner:  Luis Saavedra
 Type:  Bug|   Status:  assigned
Component:  Core (Mail)|  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords:  SSL| Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+-
Changes (by Mariusz Felisiak):

 * cc: Carlton Gibson (added)


Comment:

 `EmailBackend` uses `SSLContext` since
 2848e5d0ce5cf3c31fe87525536093b21d570f69. Users can subclass
 `EmailBackend` and override the `ssl_context` property to use custom
 cart/key files. Maybe it's enough to consider this ticket as fixed 樂

-- 
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/01070186119f8dc7-934a2447-6121-4fb5-86b8-2f3b45799104-00%40eu-central-1.amazonses.com.

Re: [Django] #32539: Support accessing the current filtered queryset from within SimpleListFilter.lookups()

2023-02-02 Thread Django 
#32539: Support accessing the current filtered queryset from within
SimpleListFilter.lookups()
+---
 Reporter:  Simon Willison  |Owner:  Sarah Boyce
 Type:  New feature |   Status:  assigned
Component:  contrib.admin   |  Version:  3.1
 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):

 The PR here looks promising. With a
 [https://github.com/carltongibson/django_ticket_32539 simple test project]
 it correctly allows facetted (with counts) filtering.

-- 
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/0107018611668df2-ed151b92-63cb-4af7-8d82-d2dc76fb68ec-00%40eu-central-1.amazonses.com.

Re: [Django] #29850: Add window support for RowRange frames

2023-02-02 Thread Django 
#29850: Add window support for RowRange frames
-+-
 Reporter:  Daniel Fuchs |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  GSoC | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Mariusz Felisiak:

Old description:

> The current RowRange frame is missing handling for several cases.
>
> None of the following are currently supported:
> RowRange(start=-2, end=-1)
> ROWS BETWEEN 2 PRECEDING AND 1 PRECEDING
> RowRange(start=1, end=2)
> ROWS BETWEEN 1 FOLLOWING AND 2 FOLLOWING
>
> It's also missing support for EXCLUDE.
> ROWS BETWEEN 1 PRECEDING AND 1 FOLLOWING EXCLUDE CURRENT ROW
>
> 
>
> Frame exclusion is supported only in [https://www.postgresql.org/docs/11
> /sql-expressions.html#SYNTAX-WINDOW-FUNCTIONS PostgreSQL 11+] and
> [https://www.sqlite.org/windowfunctions.html#wexcls SQLite 3.28+], other
> databases do not support exclusion (see
> [https://docs.oracle.com/en/database/oracle/oracle-database/18/sqlrf
> /Analytic-Functions.html#GUID-527832F7-63C0-4445-8C16-307FA5084056 Oracle
> 18c doc], [https://mariadb.com/kb/en/library/window-functions-overview/
> MariaDB doc], and [https://dev.mysql.com/doc/refman/8.0/en/window-
> functions-frames.html MySQL doc]).

New description:

 The current RowRange frame is missing handling for several cases.

 None of the following are currently supported:
 RowRange(start=-2, end=-1)
 ROWS BETWEEN 2 PRECEDING AND 1 PRECEDING
 RowRange(start=1, end=2)
 ROWS BETWEEN 1 FOLLOWING AND 2 FOLLOWING

 It's also missing support for EXCLUDE.
 ROWS BETWEEN 1 PRECEDING AND 1 FOLLOWING EXCLUDE CURRENT ROW

 

 Frame exclusion is supported in [https://www.postgresql.org/docs/11/sql-
 expressions.html#SYNTAX-WINDOW-FUNCTIONS PostgreSQL 11+],
 [https://www.sqlite.org/windowfunctions.html#wexcls SQLite 3.28+], and
 [https://docs.oracle.com/en/database/oracle/oracle-database/21/sqlrf
 /Analytic-Functions.html#GUID-527832F7-63C0-4445-8C16-307FA5084056 Oracle
 21c+] other databases do not support exclusion
 ([https://mariadb.com/kb/en/library/window-functions-overview/ MariaDB
 doc], and [https://dev.mysql.com/doc/refman/8.0/en/window-functions-
 frames.html MySQL doc]).

--

-- 
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/01070186115c8a2e-0efbf7a1-8cc3-4bd6-8e7b-72bff8953c2d-00%40eu-central-1.amazonses.com.

Re: [Django] #16180: IGNORED_PARAMS customization

2023-02-02 Thread Django 
#16180: IGNORED_PARAMS customization
-+--
 Reporter:  Manuel Saelices  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  dev
 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 Mariusz Felisiak):

 * status:  new => closed
 * needs_better_patch:  1 => 0
 * has_patch:  1 => 0
 * resolution:   => wontfix
 * stage:  Accepted => Unreviewed


Comment:

 It's been 12 years since the ticket was opened. As far as I'm aware, this
 is rather niche and monkey patching a module constant is an acceptable
 approach for the reported issue. It's not worth adding extra hooks.

-- 
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/010701861137b250-7be1cf55-4173-4ea9-821c-cf035350b4b9-00%40eu-central-1.amazonses.com.