Re: [Django] #27236: Deprecate Model.Meta.index_together in favour of Model.Meta.indexes

2022-07-17 Thread Django 
#27236: Deprecate Model.Meta.index_together in favour of Model.Meta.indexes
-+-
 Reporter:  Akshesh Doshi|Owner:  David
 Type:   |  Wobrock
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  index_together   | 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):

 * cc: Carlton Gibson (added)


Comment:

 I think we need all three:
 - more descriptive release notes for `AlterIndexTogether`,
 - running checks only on unapplied migrations, and
 - reducing `AlterIndexTogether` with `RenameIndex`.

 Lots of folks don't recreate their databases so they won't have to do
 anything. As for the rest, we can document possible solutions, e.g.
 - squash migrations,
 - update the historical `CreateModel()` operation with
 `options={index_together=[...]}` with the current state of
 `index_together` (as long as all fields existed when the model was
 created),
 - replace `AlterIndexTogether` with `AddIndex`/`RemoveIndex`.

-- 
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/010701820fa1b942-853ddb3b-b773-4be2-83ea-60b7f33a1dcc-00%40eu-central-1.amazonses.com.

Re: [Django] #33854: dbshell additional parameters should be passed before dbname on PostgreSQL.

2022-07-17 Thread Django 
#33854: dbshell additional parameters should be passed before dbname on 
PostgreSQL.
-+-
 Reporter:  Jarrett Keifer   |Owner:  Jarrett
 Type:   |  Keifer
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  psql dbshell | 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 GitHub ):

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


Comment:

 In [changeset:"3e3e8141662c70d74d3aaef9d4b053c9636ea0d7" 3e3e8141]:
 {{{
 #!CommitTicketReference repository=""
 revision="3e3e8141662c70d74d3aaef9d4b053c9636ea0d7"
 Fixed #33854 -- Corrected the order of parameters in dbshell 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/010701820f929333-3176f515-6f07-40c9-a067-a88b0e4c0f8e-00%40eu-central-1.amazonses.com.

Re: [Django] #23251: Use a temporary folder to store uploaded files during tests

2022-07-17 Thread Django 
#23251: Use a temporary folder to store uploaded files during tests
-+-
 Reporter:  Shai Berger  |Owner:  Bhavya
 |  Peshavaria
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  file storage upload  | 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):

 Replying to [comment:18 Shai Berger]:
 > In the years since this ticket was first filed, cloud services have
 become even more pervasive and important than they were. IMO, this means
 that the `TEST_MEDIA_ROOT` approach is inferior to a `TEST_FILE_STORAGE`,
 where the whole default storage is replaced for tests. That would allow
 users to choose if the media in their tests are saved to memory (as
 suggested in comment:5), to a different bucket in their cloud object
 storage, or to a local file. Of course, if a user explicitly creates their
 own storage in code, there's little Django can do as a framework.

 Agreed, we should first resolved #26029
 ([https://github.com/django/django/pull/15610 PR]) to add `STORAGES`, then
 we can add support for the new `test` key.

-- 
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/010701820f910472-e2a2d24c-3249-49f3-a915-17b2c893f5c8-00%40eu-central-1.amazonses.com.

Re: [Django] #33854: dbshell additional parameters should be passed before dbname on PostgreSQL.

2022-07-17 Thread Django 
#33854: dbshell additional parameters should be passed before dbname on 
PostgreSQL.
-+-
 Reporter:  Jarrett Keifer   |Owner:  Jarrett
 Type:   |  Keifer
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  psql dbshell | 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):

 * 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/010701820f85174c-6229fda6-e9d2-4dfc-a83b-57ab948c1ff2-00%40eu-central-1.amazonses.com.

Re: [Django] #33854: dbshell additional parameters should be passed before dbname on PostgreSQL. (was: dbshell additional parameters does not work with psql)

2022-07-17 Thread Django 
#33854: dbshell additional parameters should be passed before dbname on 
PostgreSQL.
-+-
 Reporter:  Jarrett Keifer   |Owner:  Jarrett
 Type:   |  Keifer
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  psql dbshell | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  nobody => Jarrett Keifer
 * status:  new => assigned
 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 I cannot reproduce these warning with `psql` (12.11) 樂, nevertheless I
 agree that we should pass `options` as
 [https://www.postgresql.org/docs/current/app-psql.html documented].

-- 
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/010701820f802f86-218c803a-cbe2-4858-92b5-d4ab37e975bd-00%40eu-central-1.amazonses.com.

Re: [Django] #33726: Django admin needs a skip link

2022-07-17 Thread Django 
#33726: Django admin needs a skip link
-+-
 Reporter:  Thibaud Colas|Owner:  Marcelo
 |  Galigniana
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  keyboard, ux   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Marcelo Galigniana):

 * 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/010701820f7accce-2aa4c855-2d12-4847-9a85-a3f1221ceeaf-00%40eu-central-1.amazonses.com.

[Django] #33854: dbshell additional parameters does not work with psql

2022-07-17 Thread Django 
#33854: dbshell additional parameters does not work with psql
-+-
   Reporter:  Jarrett|  Owner:  nobody
  Keifer |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  4.0
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  psql dbshell
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 `psql` expects all options to proceed the database name, if provided. So,
 if doing something like `./manage.py dbshell -- -c "select * from
 some_table;" one will get this:

 {{{
 $ ./manage.py dbshell -- -c "select * from some_table;"
 psql: warning: extra command-line argument "-c" ignored
 psql: warning: extra command-line argument "select * from some_table;"
 ignored
 psql (10.21)
 Type "help" for help.

 some_database=>
 }}}

 It appears the args list just need to be constructed in the proper order,
 leaving the database name for the end of the args list.

-- 
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/010701820ed3dc06-78aa58da-eca1-4a91-8e1d-172247938a45-00%40eu-central-1.amazonses.com.

Re: [Django] #33728: Tab order should match visual order for admin model forms’ submit buttons

2022-07-17 Thread Django 
#33728: Tab order should match visual order for admin model forms’ submit 
buttons
-+-
 Reporter:  Thibaud Colas|Owner:  Alexander
 Type:   |  Freyr Lúðvíksson
  Cleanup/optimization   |   Status:  closed
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  accessibility,   | Triage Stage:  Ready for
  keyboard, ux   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"b4817d20b9e55df30be0b1b2ca8c8bb6d61aab07" b4817d20]:
 {{{
 #!CommitTicketReference repository=""
 revision="b4817d20b9e55df30be0b1b2ca8c8bb6d61aab07"
 Fixed #33728 -- Reordered submit buttons in admin.

 Thanks Tom Carrick and Thibaud Colas for reviews.
 }}}

-- 
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/010701820d849565-7cfb432d-a4fd-432e-8eb5-852560ef0dfd-00%40eu-central-1.amazonses.com.

Re: [Django] #33728: Tab order should match visual order for admin model forms’ submit buttons

2022-07-17 Thread Django 
#33728: Tab order should match visual order for admin model forms’ submit 
buttons
-+-
 Reporter:  Thibaud Colas|Owner:  Alexander
 Type:   |  Freyr Lúðvíksson
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Ready for
  keyboard, ux   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  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/010701820be35d7b-6ee18415-8ca7-4188-9e27-436c8bb31c5f-00%40eu-central-1.amazonses.com.

Re: [Django] #23251: Use a temporary folder to store uploaded files during tests

2022-07-17 Thread Django 
#23251: Use a temporary folder to store uploaded files during tests
-+-
 Reporter:  Shai Berger  |Owner:  Bhavya
 |  Peshavaria
 Type:  Bug  |   Status:  assigned
Component:  Testing framework|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  file storage upload  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Shai Berger):

 In the years since this ticket was first filed, cloud services have become
 even more pervasive and important than they were. IMO, this means that the
 `TEST_MEDIA_ROOT` approach is inferior to a `TEST_FILE_STORAGE`, where the
 whole default storage is replaced for tests. That would allow users to
 choose if the media in their tests are saved to memory (as suggested in
 comment:5), to a different bucket in their cloud object storage, or to a
 local file. Of course, if a user explicitly creates their own storage in
 code, there's little Django can do as a framework.

 Also, I don't think backwards compatibility in the sense of "keep putting
 test files into production folders" is something we want here. I'd much
 prefer things working properly out of the box -- meaning, the default
 should be that media files go into a temporary folder on the local system.

-- 
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/010701820b33e9eb-35e331c4-b11d-43d6-b82b-9128e4ec7824-00%40eu-central-1.amazonses.com.

Re: [Django] #33853: delete polymorphism basemodel

2022-07-17 Thread Django 
#33853: delete polymorphism basemodel
---+--
 Reporter:  joejoe-am  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  4.0
 Severity:  Normal |   Resolution:  invalid
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Mariusz Felisiak):

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


Comment:

 Please don't use Trac as a support channel. Closing per
 TicketClosingReasons/UseSupportChannels.

-- 
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/010701820b09c299-08e55be6-8b4f-4b90-b9d1-95a23eaecdf6-00%40eu-central-1.amazonses.com.