Re: [Django] #32177: ManagementUtility instantiates CommandParser without passing already-computed prog argument

[Django]

#32177: ManagementUtility instantiates CommandParser without passing already-
computed prog argument
-+-
 Reporter:  William Schwartz |Owner:  Douglas
 |  Cueva
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1
 * needs_tests:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Tentatively accepted, looks valid but I was not able to reproduce and
 invalid message (even with mocking `sys.argv`), so a regression test is
 crucial.

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

Re: [Django] #32178: Allow database backends to skip tests and mark expected failures

[Django]

#32178: Allow database backends to skip tests and mark expected failures
-+-
 Reporter:  Tim Graham   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.cdb64cd45715d905708d93add09c05d0%40djangoproject.com.

Re: [Django] #32180: Add a warning if the file system cache location is relative. (was: FileBasedCache accepts relative directorires as a LOCATION documentation say should be absolute)

[Django]

#32180: Add a warning if the file system cache location is relative.
-+-
 Reporter:  Carles Pina Estany   |Owner:  Carles
 Type:   |  Pina Estany
  Cleanup/optimization   |   Status:  assigned
Component:  Core (System |  Version:  master
  checks)|
 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
 * component:  Core (Cache system) => Core (System checks)
 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.3fbf146b41cdc983454d7a1065c01899%40djangoproject.com.

Re: [Django] #31617: Improve overall admin accessibility.

[Django]

#31617: Improve overall admin accessibility.
-+-
 Reporter:  Gustavo Siñovsky |Owner:  Bhavna
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility, ui,   | Triage Stage:
  ux, admin  |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by Nick Pope):

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


Comment:

 Replying to [comment:8 Sourabh Rana]:

 Please don't close tickets that have not yet been resolved.

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

Re: [Django] #31617: Improve overall admin accessibility.

[Django]

#31617: Improve overall admin accessibility.
-+-
 Reporter:  Gustavo Siñovsky |Owner:  Bhavna
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  accessibility, ui,   | Triage Stage:
  ux, admin  |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by Sourabh Rana):

 * status:  assigned => closed
 * resolution:   => 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/067.6089a85c1880624e02bae841643e5d8b%40djangoproject.com.

Re: [Django] #32180: FileBasedCache accepts relative directorires as a LOCATION documentation say should be absolute

[Django]

#32180: FileBasedCache accepts relative directorires as a LOCATION documentation
say should be absolute
-+-
 Reporter:  Carles Pina Estany   |Owner:  Carles
 Type:   |  Pina Estany
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Cache system)  |  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
-+-
Description changed by Carles Pina Estany:

Old description:

> FileBasedCache LOCATION: the documentation says that the path should be
> absolute, Django accepts absolute or relative.
>
> In https://docs.djangoproject.com/en/3.1/topics/cache/#filesystem-caching
>
> It says:
> "The directory path should be absolute – that is, it should start at the
> root of your filesystem."
>
> The code makes them absolute:
> https://github.com/django/django/blob/master/django/core/cache/backends/filebased.py#L22
>
> Enforcing the LOCATION to be specified only in absolute way might have no
> gain and would have backwards compatibility problems for deployments that
> are passing the directory using a relative path.
>
> A possible way to improve the situation without or minimal backwards
> incompatibility changes would be to add a new check (thanks Carlton for
> the idea).

New description:

 FileBasedCache LOCATION: the documentation says that the path should be
 absolute, Django accepts absolute or relative.

 In https://docs.djangoproject.com/en/3.1/topics/cache/#filesystem-caching

 It says:
 "The directory path should be absolute – that is, it should start at the
 root of your filesystem."

 The code makes them absolute:
 
https://github.com/django/django/blob/master/django/core/cache/backends/filebased.py#L22

 Enforcing the LOCATION to be specified only in absolute way might have no
 gain and would have backwards compatibility problems for deployments that
 are passing the directory using a relative path.

 A possible way to improve the situation without or minimal backwards
 incompatibility changes would be to add a new check (thanks Carlton for
 the idea).

 I'm happy to make any changes:
 https://github.com/django/django/pull/13655

--

-- 
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/063.afd4b9e3aaaff29bb8a1619fd959e466%40djangoproject.com.

[Django] #32180: FileBasedCache accepts relative directorires as a LOCATION documentation say should be absolute

[Django]

#32180: FileBasedCache accepts relative directorires as a LOCATION documentation
say should be absolute
-+-
   Reporter:  Carles |  Owner:  Carles Pina Estany
  Pina Estany|
   Type: | Status:  assigned
  Cleanup/optimization   |
  Component:  Core   |Version:  master
  (Cache system) |
   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  |
-+-
 FileBasedCache LOCATION: the documentation says that the path should be
 absolute, Django accepts absolute or relative.

 In https://docs.djangoproject.com/en/3.1/topics/cache/#filesystem-caching

 It says:
 "The directory path should be absolute – that is, it should start at the
 root of your filesystem."

 The code makes them absolute:
 
https://github.com/django/django/blob/master/django/core/cache/backends/filebased.py#L22

 Enforcing the LOCATION to be specified only in absolute way might have no
 gain and would have backwards compatibility problems for deployments that
 are passing the directory using a relative path.

 A possible way to improve the situation without or minimal backwards
 incompatibility changes would be to add a new check (thanks Carlton for
 the idea).

-- 
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/048.b9c854c88bb50b4b357aede2ed99055e%40djangoproject.com.

Re: [Django] #32158: loaddata crashes on SQLite when table names are SQL keywords.

[Django]

#32158: loaddata crashes on SQLite when table names are SQL keywords.
-+-
 Reporter:  Scott Herriman   |Owner:  George
 |  Bezerra
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  3.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  loaddata SqlLite3| Triage Stage:  Accepted
  check_constraints  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Simon Charette):

 * needs_better_patch:  0 => 1


Comment:

 Suggested test improvements to avoid the creation of another model.

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

Re: [Django] #32179: Add JSONObject Func

[Django]

#32179: Add JSONObject Func
-+-
 Reporter:  Chiorufarewerin  |Owner:
 |  Chiorufarewerin
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  json_object, | Triage Stage:  Accepted
  jsonb_build_object, JSONObject |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * 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/073.a1bdf345b00b1faae11787f7f57fc65b%40djangoproject.com.

Re: [Django] #32179: Add JSONObject Func

[Django]

#32179: Add JSONObject Func
-+-
 Reporter:  Chiorufarewerin  |Owner:
 |  Chiorufarewerin
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  json_object, | Triage Stage:  Accepted
  jsonb_build_object, JSONObject |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.8fb689d82bcbf9b0204f7503a655f2e0%40djangoproject.com.