Re: [Django] #34110: Add InMemoryStorage

2022-11-10 Thread Django 
#34110: Add InMemoryStorage
-+-
 Reporter:  Josh |Owner:  Francesco
 |  Panico
 Type:  New feature  |   Status:  assigned
Component:  File |  Version:  dev
  uploads/storage|
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"99b4f90ec6b96e8c2a9f22b360d4eb5589763034" 99b4f90e]:
 {{{
 #!CommitTicketReference repository=""
 revision="99b4f90ec6b96e8c2a9f22b360d4eb5589763034"
 Refs #34110 -- Added StorageSettingsMixin.
 }}}

-- 
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/0107018465765570-2d3d5a7d-b660-4ef8-8c82-905308991532-00%40eu-central-1.amazonses.com.

Re: [Django] #34110: Add InMemoryStorage

2022-11-10 Thread Django 
#34110: Add InMemoryStorage
-+-
 Reporter:  Josh |Owner:  Francesco
 |  Panico
 Type:  New feature  |   Status:  assigned
Component:  File |  Version:  dev
  uploads/storage|
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"032c09c4144eaa278a64b9a4bef838341b35d175" 032c09c4]:
 {{{
 #!CommitTicketReference repository=""
 revision="032c09c4144eaa278a64b9a4bef838341b35d175"
 Refs #34110 -- Reorganized django.core.files.storage into a separate
 module.
 }}}

-- 
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/0107018465765529-79b435f6-5f07-41b0-8b12-b993c652a8e3-00%40eu-central-1.amazonses.com.

Re: [Django] #28987: Migration changing ManyToManyField target to 'self' doesn't work correctly

2022-11-10 Thread Django 
#28987: Migration changing ManyToManyField target to 'self' doesn't work 
correctly
-+
 Reporter:  MSleepyPanda |Owner:  Bhuvnesh
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  ManyToManyField  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Bhuvnesh):

 * has_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/0107018462e35ec8-882d94a0-742b-447a-ab25-41cb5df190af-00%40eu-central-1.amazonses.com.

Re: [Django] #28987: Migration changing ManyToManyField target to 'self' doesn't work correctly

2022-11-10 Thread Django 
#28987: Migration changing ManyToManyField target to 'self' doesn't work 
correctly
-+
 Reporter:  MSleepyPanda |Owner:  Bhuvnesh
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  ManyToManyField  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by Bhuvnesh):

 [https://github.com/django/django/pull/16281 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/0107018462e33cb5-26945ed3-b8cd-4197-9960-4fd7efecf46f-00%40eu-central-1.amazonses.com.

Re: [Django] #28553: Querysets: annotate() columns are forced into a certain position which may disrupt union()

2022-11-10 Thread Django 
#28553: Querysets: annotate() columns are forced into a certain position which 
may
disrupt union()
-+-
 Reporter:  David Sanders|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (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 Matthias Kestenholz):

 I just hit this as well. The solution (workaround) seems to be using `F()`
 and `Value()` freely and consistently for all querysets even if it doesn't
 look necessary on the surface.

 See
 
https://github.com/matthiask/feincms3-forms/commit/c112a7d613e991780f383393fd05f1c84c81a279

 (It's a bit surprising that `values_list` doesn't produce a SQL query with
 the exact same ordering of values, but after thinking about it some more
 I'm not sure if that's really a bug or just a sharp edge of the current
 implementation.)

-- 
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/01070184622d080b-27765196-69d6-4767-9167-eaf6e97dbe23-00%40eu-central-1.amazonses.com.

Re: [Django] #34149: Postgres "ExclusionConstraint with conditions cannot be deferred." seems wrong

2022-11-10 Thread Django 
#34149: Postgres "ExclusionConstraint with conditions cannot be deferred." seems
wrong
-+-
 Reporter:  Márton Salomváry |Owner:  Márton
 |  Salomváry
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  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 Simon Charette):

 Bhuvnesh, it's great that you are enthusiastic about fixing issues but you
 might want to give reporters a chance to reply on whether or not they want
 to provide a patch themselves before assigning the ticket to you.

-- 
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/010701846221a30e-82146f4e-a523-4bf2-ba5b-8f24556bd321-00%40eu-central-1.amazonses.com.

Re: [Django] #28987: Migration changing ManyToManyField target to 'self' doesn't work correctly

2022-11-10 Thread Django 
#28987: Migration changing ManyToManyField target to 'self' doesn't work 
correctly
-+
 Reporter:  MSleepyPanda |Owner:  Bhuvnesh
 Type:  Bug  |   Status:  assigned
Component:  Migrations   |  Version:  2.0
 Severity:  Normal   |   Resolution:
 Keywords:  ManyToManyField  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by Carlton Gibson):

 Hi Bhuvnesh

 > I tried to alter self pointing field and with the changes below its
 working as expected for the above issue and passing all the tests as well.

 If the tests are all passing it's worth opening a PR to make review
 easier. (Make sure to add a new test for the issue here too.)

 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/010701846205a0e0-25a89c9a-d8c1-4f1c-adf3-a89fe38b0632-00%40eu-central-1.amazonses.com.

Re: [Django] #34149: Postgres "ExclusionConstraint with conditions cannot be deferred." seems wrong

2022-11-10 Thread Django 
#34149: Postgres "ExclusionConstraint with conditions cannot be deferred." seems
wrong
-+-
 Reporter:  Márton Salomváry |Owner:  Márton
 |  Salomváry
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  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:"d6cbf39a1ba2053c6211a16ed42d5410e5c5cdd0" d6cbf39]:
 {{{
 #!CommitTicketReference repository=""
 revision="d6cbf39a1ba2053c6211a16ed42d5410e5c5cdd0"
 Fixed #34149 -- Allowed adding deferrable conditional exclusion
 constraints on PostgreSQL.
 }}}

-- 
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/01070184611e4b79-7e90cd41-a67d-4153-b443-2a6ded1053fd-00%40eu-central-1.amazonses.com.

Re: [Django] #34149: Postgres "ExclusionConstraint with conditions cannot be deferred." seems wrong

2022-11-10 Thread Django 
#34149: Postgres "ExclusionConstraint with conditions cannot be deferred." seems
wrong
-+-
 Reporter:  Márton Salomváry |Owner:  Márton
 |  Salomváry
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  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_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/01070184610325c8-4bdb206f-59c7-4914-a9bb-0a25994ad6ff-00%40eu-central-1.amazonses.com.

Re: [Django] #32319: Add support to HashedFilesMixin for ES modules

2022-11-10 Thread Django 
#32319: Add support to HashedFilesMixin for ES modules
-+
 Reporter:  gilmrjc  |Owner:  blighj
 Type:  New feature  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  dev
 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):

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

 > This works with the higlight.js file but not the type definitions from
 this review, #15058 (review). Since they are a feature of typescript and
 not javascript, I think that's a fair trade off.

-- 
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/0107018460fa5f6f-da8a402b-09be-4abb-b656-ae3923cc0d09-00%40eu-central-1.amazonses.com.

Re: [Django] #33662: Choose which items are displayed per language in Sitemap

2022-11-10 Thread Django 
#33662: Choose which items are displayed per language in Sitemap
--+
 Reporter:  roxanebellot  |Owner:  roxanebellot
 Type:  New feature   |   Status:  assigned
Component:  contrib.sitemaps  |  Version:  4.0
 Severity:  Normal|   Resolution:
 Keywords:  sitemap   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Carlton Gibson):

 * has_patch:  1 => 0


Comment:

 @roxanebellot Please open a PR and add it here when you've done so.
 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/0107018460f412c5-2dbf1a2f-5f57-430d-bc58-d488fc4274bc-00%40eu-central-1.amazonses.com.

Re: [Django] #34036: Low text contrast over light blue backgrounds in admin light theme

2022-11-10 Thread Django 
#34036: Low text contrast over light blue backgrounds in admin light theme
-+-
 Reporter:  Thibaud Colas|Owner:  Nimra
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  4.0
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  color contrast, ux |
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


-- 
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/0107018460f1ccf5-29edf7b8-3416-4d03-a12d-21f630d394d4-00%40eu-central-1.amazonses.com.

Re: [Django] #34074: 'headers' argument for test RequestFactory/Client

2022-11-10 Thread Django 
#34074: 'headers' argument for test RequestFactory/Client
-+-
 Reporter:  Adam Johnson |Owner:  David
 |  Wobrock
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  Version:  dev
 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/0107018460e75944-707fe6d4-086d-4f1a-8f0e-75e58e970658-00%40eu-central-1.amazonses.com.

Re: [Django] #29510: QueryDict.copy() returns closed files when the type of file is TemporaryUploadedFile

2022-11-10 Thread Django 
#29510: QueryDict.copy() returns closed files when the type of file is
TemporaryUploadedFile
-+-
 Reporter:  Liquid Scorpio   |Owner:  Dan
 |  Madere
 Type:  Bug  |   Status:  assigned
Component:  File |  Version:  1.11
  uploads/storage|
 Severity:  Normal   |   Resolution:
 Keywords:  QueryDict, upload,   | Triage Stage:  Accepted
  file   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Carlton Gibson):

 > I stepped back, and pondered why are people copying a QueryDict
 anyway...

 This seems like the right thought to me. 樂

 I have to admit I'm struggling to see the use-case — Folks would have to
 be making a copy of `request.FILES` for this to come up no? Why would you
 want a mutable copy of that? (Maybe more ☕️ is needed :)

 Copying `request.GET` in order to edit a query string makes sense.
 Uploaded files though... 樂

 (Sorry if I'm being dense)

-- 
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/0107018460d3b939-0a1bec07-8836-43d1-98f1-7a90df5bfbe5-00%40eu-central-1.amazonses.com.