Re: [Django] #35297: Not showing static file and 404 error instead of GET mathod

[Django]

#35297: Not showing static file and 404 error instead of GET mathod
-+-
 Reporter:  Shihab Khan  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  4.2
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  static file error| Triage Stage:
  404|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by David Sanders):

 * resolution:   => invalid
 * status:  new => 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/0107018e36504ca1-703e1605-a17f-41c5-962e-58c210ad6ad2-00%40eu-central-1.amazonses.com.

Re: [Django] #35297: Not showing static file and 404 error instead of GET mathod

[Django]

#35297: Not showing static file and 404 error instead of GET mathod
-+-
 Reporter:  Shihab Khan  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:  static file error| Triage Stage:
  404|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by David Sanders):

 Shihab Khan, you've been asked not to submit tickets that are support
 questions. Please stop as it is creating unnecessary work for
 contributors. There are many places you can go to get help:
 https://www.djangoproject.com/community/
-- 
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/0107018e36501fb1-1452cfee-3572-4848-9b53-0ec5c31d7d03-00%40eu-central-1.amazonses.com.

[Django] #35297: Not showing static file and 404 error instead of GET mathod

[Django]

#35297: Not showing static file and 404 error instead of GET mathod
-+-
   Reporter:  Shihab |  Owner:  nobody
  Khan   |
   Type:  Bug| Status:  new
  Component: |Version:  4.2
  contrib.staticfiles|   Keywords:  static file error
   Severity:  Normal |  404
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 {{{
 $ python manage.py collectstatic

 You have requested to collect static files at the destination
 location as specified in your settings:

 C:\Users\int\Downloads\New folder\project\assets

 This will overwrite existing files!
 Are you sure you want to do this?

 Type 'yes' to continue, or 'no' to cancel: yes
 Post-processing 'admin\assets\css\vendors\icon\font-awesome\all.min.css'
 failed!

 Traceback (most recent call last):
   File "C:\Users\int\Downloads\New folder\project\manage.py", line 22, in
 
 main()
   File "C:\Users\int\Downloads\New folder\project\manage.py", line 18, in
 main
 execute_from_command_line(sys.argv)
   File "C:\Users\int\AppData\Local\Programs\Python\Python310\lib\site-
 packages\django\core\management\__init__.py", line 442, in
 execute_from_command_line
 utility.execute()
   File "C:\Users\int\AppData\Local\Programs\Python\Python310\lib\site-
 packages\django\core\management\__init__.py", line 436, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "C:\Users\int\AppData\Local\Programs\Python\Python310\lib\site-
 packages\django\core\management\base.py", line 412, in run_from_argv
 self.execute(*args, **cmd_options)
   File "C:\Users\int\AppData\Local\Programs\Python\Python310\lib\site-
 packages\django\core\management\base.py", line 458, in execute
 output = self.handle(*args, **options)
   File "C:\Users\int\AppData\Local\Programs\Python\Python310\lib\site-
 packages\django\contrib\staticfiles\management\commands\collectstatic.py",
 line 209, in handle
 collected = self.collect()
   File "C:\Users\int\AppData\Local\Programs\Python\Python310\lib\site-
 packages\django\contrib\staticfiles\management\commands\collectstatic.py",
 line 154, in collect
 raise processed
 whitenoise.storage.MissingFileError: The file
 'admin/assets/css/vendors/icon/webfonts/fa-brands-400.woff2' could not be
 found with .

 The CSS file 'admin\assets\css\vendors\icon\font-awesome\all.min.css'
 references a file which could not be found:
   admin/assets/css/vendors/icon/webfonts/fa-brands-400.woff2

 Please check the URL references in this CSS file, particularly any
 relative paths which might be pointing to the wrong location.

 }}}
-- 
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/0107018e364c4c56-11393b20-68b2-4b2f-83a5-a3b06c2452cf-00%40eu-central-1.amazonses.com.

Re: [Django] #35294: Queryset explain can be truncated. (was: Queryset explain truncated)

[Django]

#35294: Queryset explain can be truncated.
-+-
 Reporter:  Gordon Wrigley   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  explain  | 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
 * summary:  Queryset explain truncated => Queryset explain can be
  truncated.

Comment:

 Seems valid. Would like like to prepare a patch? (a regression test can be
 tricky.)
-- 
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/0107018e3630d339-c4739497-75f1-4979-a446-71cad67cee40-00%40eu-central-1.amazonses.com.

Re: [Django] #35296: The autoescape parameter to Engine() seems to have no effect on Context. (was: The autoescape parameter to Engine() seems to have no effect)

[Django]

#35296: The autoescape parameter to Engine() seems to have no effect on Context.
-+--
 Reporter:  Roman Donchenko  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Template system  |  Version:  5.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):

 * resolution:   => invalid
 * status:  new => closed
 * summary:  The autoescape parameter to Engine() seems to have no effect =>
 The autoescape parameter to Engine() seems to have no effect on
 Context.

Comment:

 `Context` has it's own `autoescape` parameter that engine shouldn't
 override. You can pass `Context` with `autoespace=False` or use
 `render_to_string()` with a template name.
-- 
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/0107018e3611ecb3-acd3d1e2-8b56-4571-84ff-0aad9e696192-00%40eu-central-1.amazonses.com.

Re: [Django] #28519: Add filter(), exclude(), and other base QuerySet methods to combined QuerySets (union(), etc.)

[Django]

#28519: Add filter(), exclude(), and other base QuerySet methods to combined
QuerySets (union(), etc.)
-+-
 Reporter:  Stanislav Karpov |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  union,   | Triage Stage:  Accepted
  intersection, difference   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e351c59a9-2b69c2ef-6047-46ff-8291-b0b1f832fff9-00%40eu-central-1.amazonses.com.

Re: [Django] #23337: CircularDependencyError when squashing migrations

[Django]

#23337: CircularDependencyError when squashing migrations
---+
 Reporter:  Richard Eames  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Migrations |  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:  0
---+
Changes (by bcail):

 * cc: bcail (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/0107018e34541cca-fb73de94-9d00-4c32-8164-1ddee2b4c043-00%40eu-central-1.amazonses.com.

Re: [Django] #35296: The autoescape parameter to Engine() seems to have no effect

[Django]

#35296: The autoescape parameter to Engine() seems to have no effect
-+--
 Reporter:  Roman Donchenko  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Template system  |  Version:  5.0
 Severity:  Normal   |   Resolution:
 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 bcail):

 * cc: bcail (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/0107018e344ff15a-36aa237f-8e38-4867-9936-6010b1d03eb6-00%40eu-central-1.amazonses.com.

Re: [Django] #35296: The autoescape parameter to Engine() seems to have no effect

[Django]

#35296: The autoescape parameter to Engine() seems to have no effect
-+--
 Reporter:  Roman Donchenko  |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  Template system  |  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Comment (by bcail):

 I see the same result. It looks like the `Context` object has an
 `autoescape` parameter (which defaults to True) - so that may sort of be
 overriding the engine value. But, I'm not sure the engine value is always
 checked where it should be.
-- 
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/0107018e344f7525-e73b2f22-f9b0-407b-85b4-eba8d68870dc-00%40eu-central-1.amazonses.com.

Re: [Django] #35295: Use INSERT with multiple rows on Oracle 23c+

[Django]

#35295: Use INSERT with multiple rows on Oracle 23c+
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | 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

Comment:

 The current patch fails on
 
`field_defaults.tests.DefaultTests.test_bulk_create_mixed_db_defaults_function`:
 {{{
 django.db.utils.DatabaseError: ORA-01797: this operator must be followed
 by ANY or ALL
 }}}
-- 
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/0107018e343f79ed-b327fbe6-9ad0-485d-8df4-a68228b640ff-00%40eu-central-1.amazonses.com.

[Django] #35296: The autoescape parameter to Engine() seems to have no effect

[Django]

#35296: The autoescape parameter to Engine() seems to have no effect
---+
   Reporter:  Roman Donchenko  |  Owner:  nobody
   Type:  Uncategorized| Status:  new
  Component:  Template system  |Version:  5.0
   Severity:  Normal   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 The reference documentation for `django.template.Engine` says
 [https://docs.djangoproject.com/en/5.0/ref/templates/api/#configuring-an-
 engine the following]:

 * `autoescape` controls whether HTML autoescaping is enabled.
   It defaults to `True`.

 Based on this, I would expect the following to print `<>`:


 {{{#!python
 import django.template
 django.template.Engine(autoescape=False)
 t = e.from_string('{{x}}')
 print(t.render(django.template.Context({'x': '<>'})))
 }}}

 But it doesn't, it prints `<>`. So it seems that the `autoescape`
 parameter does nothing.

 Either the code should be updated to make the parameter work, or the docs
 should explain what it actually does.
-- 
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/0107018e341e6368-44d05922-a082-4d76-84fa-266e3ed06782-00%40eu-central-1.amazonses.com.

Re: [Django] #35293: Django 5.x changes the date format on an from "2012-10-01" to "01/10/2012"

[Django]

#35293: Django 5.x changes the date format on an  from
"2012-10-01" to "01/10/2012"
-+--
 Reporter:  Shaheed Haque|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  5.0
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Comment (by Claude Paroz):

 Note that Django itself has no widgets having `input type="date"` by
 default. This issue may be related to some custom code. See for example an
 implementation in one of my projects:
 {{{
 class DateInput(forms.DateInput):
 input_type = 'date'

 def format_value(self, value):
 return str(value) if value is not None else None
 }}}
 See also #33113
-- 
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/0107018e33fcc1ec-9ef6b86b-6132-494a-b3e9-f047789f56a1-00%40eu-central-1.amazonses.com.

Re: [Django] #35295: Use INSERT with multiple rows on Oracle 23c+

[Django]

#35295: Use INSERT with multiple rows on Oracle 23c+
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by David Smith):

 * 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/0107018e33e4be2a-81f76203-bc94-4ab4-b328-656033f6a58d-00%40eu-central-1.amazonses.com.

Re: [Django] #35294: Queryset explain truncated

[Django]

#35294: Queryset explain truncated
-+-
 Reporter:  Gordon Wrigley   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  explain  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Gordon Wrigley):

 Yes.
-- 
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/0107018e33d5256c-91c6cc46-c9c9-411c-a958-6cb909a9ccd4-00%40eu-central-1.amazonses.com.

Re: [Django] #35295: Use INSERT with multiple rows on Oracle 23c+

[Django]

#35295: Use INSERT with multiple rows on Oracle 23c+
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 Type:   |  Felisiak
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * has_patch:  0 => 1

Comment:

 [https://github.com/django/django/pull/17969 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/0107018e33d1b48c-c15aaec8-74e4-489d-9e7c-c490c78fe1cb-00%40eu-central-1.amazonses.com.

[Django] #35295: Use INSERT with multiple rows on Oracle 23c+

[Django]

#35295: Use INSERT with multiple rows on Oracle 23c+
-+-
   Reporter:  Mariusz|  Owner:  Mariusz Felisiak
  Felisiak   |
   Type: | Status:  assigned
  Cleanup/optimization   |
  Component:  Database   |Version:  5.0
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  oracle
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Oracle 23c finally allows to `INSERT` multiple rows into a table in a
 single step without a `UNION`-`SELECT` workaround 🎉

 https://oracle-base.com/articles/23c/table-values-constructor-23c#insert
-- 
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/0107018e33ccb5f9-d9863896-e6a2-4d7e-8faa-170f00f79af2-00%40eu-central-1.amazonses.com.

Re: [Django] #35294: Queryset explain truncated

[Django]

#35294: Queryset explain truncated
-+-
 Reporter:  Gordon Wrigley   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  explain  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Mariusz Felisiak):

 Interesting, do you observe the same with psycopg 3+?
-- 
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/0107018e33bfd4e6-a28c3971-944a-4e33-893c-cd1457e60431-00%40eu-central-1.amazonses.com.

Re: [Django] #34277: Add where clause in QuerySet.bulk_create() when update_conflicts=True

[Django]

#34277: Add where clause in QuerySet.bulk_create() when update_conflicts=True
-+-
 Reporter:  Alain Delplanque |Owner:  HAMA
 |  Barhamou
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 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 Natalia Bidart):

 * needs_better_patch:  0 => 1

Comment:

 Setting as patch needs improvement following a reviewer request to rebase
 and squash commits to allow for/ease future review iterations.
-- 
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/0107018e33851ade-5a5bd501-0381-48dd-bf22-1cf00b86c312-00%40eu-central-1.amazonses.com.

Re: [Django] #34277: Add where clause in QuerySet.bulk_create() when update_conflicts=True

[Django]

#34277: Add where clause in QuerySet.bulk_create() when update_conflicts=True
-+-
 Reporter:  Alain Delplanque |Owner:  HAMA
 |  Barhamou
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 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 HAMA Barhamou):

 * needs_better_patch:  1 => 0

Comment:

 ready for another revision
-- 
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/0107018e33626d39-e5c023ad-9abc-4a4e-98a6-6fdff18e757e-00%40eu-central-1.amazonses.com.

Re: [Django] #35294: Queryset explain truncated

[Django]

#35294: Queryset explain truncated
-+-
 Reporter:  Gordon Wrigley   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  explain  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Gordon Wrigley):

 * type:  Uncategorized => Bug

-- 
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/0107018e332e42a0-f2d39b04-6219--9527-a2b42344a56a-00%40eu-central-1.amazonses.com.

[Django] #35294: Queryset explain truncated

[Django]

#35294: Queryset explain truncated
-+-
   Reporter:  Gordon |  Owner:  nobody
  Wrigley|
   Type: | Status:  new
  Uncategorized  |
  Component:  Database   |Version:  4.2
  layer (models, ORM)|
   Severity:  Normal |   Keywords:  explain
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Django 4.2.10
 Python 3.10.13
 Postgres 15.6
 Psycopg2 2.9.9

 I have some very complex querysets I'm trying to optimize and what I've
 run into is explain output is being truncated at 100 lines. As far as I
 can tell this is because of this function on
 django.db.models.sql.compiler.SQLCompiler.

 {{{#!python
 def explain_query(self):
 result = list(self.execute_sql())
 # Some backends return 1 item tuples with strings, and others
 return
 # tuples with integers and strings. Flatten them out into strings.
 format_ = self.query.explain_info.format
 output_formatter = json.dumps if format_ and format_.lower() ==
 "json" else str
 for row in result[0]:
 if not isinstance(row, str):
 yield " ".join(output_formatter(c) for c in row)
 else:
 yield row
 }}}

 Where `result[0]` is ignoring additional results. Monkey patching it to

 {{{#!python
 def explain_query(self):
 results = list(self.execute_sql())
 # Some backends return 1 item tuples with strings, and others
 return
 # tuples with integers and strings. Flatten them out into strings.
 format_ = self.query.explain_info.format
 output_formatter = json.dumps if format_ and format_.lower() ==
 "json" else str
 for result in results:
 for row in result:
 if not isinstance(row, str):
 yield " ".join(output_formatter(c) for c in row)
 else:
 yield row
 }}}

 Gets me the full explain output.
-- 
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/0107018e332e02be-4752f9d4-b015-498e-a09d-2078fff945ca-00%40eu-central-1.amazonses.com.

Re: [Django] #35292: Restore autofocus functionality to admin search box within popup interface

[Django]

#35292: Restore autofocus functionality to admin search box within popup 
interface
-+-
 Reporter:  Mattias L|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  5.0
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  accessibility,   | Triage Stage:
  screen reader, autofocus   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Natalia Bidart):

 * keywords:  accessibility, screen reader, keyboard => accessibility,
 screen reader, autofocus
 * resolution:   => invalid
 * status:  new => closed
 * type:  Uncategorized => Cleanup/optimization

Comment:

 Hello Mattias, thank you for your report.

 We should confirm with the accessibility team if this is an acceptable
 proposal from the accessibility point of view. I do acknowledge that your
 PR proposes to restore the `autofocus` only when there is a popup, but
 it's unclear whether that will also be confusing screen readers.

 My advice would be to reach out to them in
 [https://forum.djangoproject.com/c/internals/accessibility/26 the
 dedicated Accessibility category in the forum] and seek approval for the
 proposal. Until then, I'll close the ticket as `invalid`, but if they do
 approve this idea, please point us to the discussion and we'll re-open.
-- 
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/0107018e33231cd6-0c52bad3-00cf-4c04-8632-9bac4cd8e24c-00%40eu-central-1.amazonses.com.

Re: [Django] #35289: Chunked transfer encoding is not handled correctly by MultiPartParser

[Django]

#35289: Chunked transfer encoding is not handled correctly by MultiPartParser
-+-
 Reporter:  Kyle Agronick|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  transfer-encoding,   | Triage Stage:
  chunked, multi-part|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Kyle Agronick):

 It looks like the only place `content_length` is used is in
 `MemoryFileUploadHandler` where `self.activated = content_length <=
 settings.FILE_UPLOAD_MAX_MEMORY_SIZE`. Content-length can be spoofed
 causing the `MemoryFileUploadHandler` to read everything into memory. It
 seems like the complexity of `TemporaryFileUploadHandler` and
 `MemoryFileUploadHandler` could be reduced by having one file handler that
 uses
 `SpooledTemporaryFile(max_size=settings.FILE_UPLOAD_MAX_MEMORY_SIZE)`.
-- 
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/0107018e32fae073-31359450-4e86-413d-886c-60c16b85203a-00%40eu-central-1.amazonses.com.

Re: [Django] #6870: pre_delete should be sent before collecting ForeignKey relationships

[Django]

#6870: pre_delete should be sent before collecting ForeignKey relationships
-+-
 Reporter:  Waldemar Kornewald   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  pre_delete signals   | Triage Stage:  Accepted
  related|
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e32f99e3b-1ff7e27a-de0d-4fa0-8cf1-98d73c9c00b3-00%40eu-central-1.amazonses.com.

Re: [Django] #6489: Add selected and enabled_from for JS calendar

[Django]

#6489: Add selected and enabled_from for JS calendar
-+-
 Reporter:  Bastian Kleineidam   |Owner:  nobody
   |
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e32f82693-4764ce00-8252-4633-8486-fbed245ce77d-00%40eu-central-1.amazonses.com.

Re: [Django] #6396: Remove customization-unfriendly admin template tags

[Django]

#6396: Remove customization-unfriendly admin template tags
--+
 Reporter:  korpios   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:  nfa-someday   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e32f77a87-a5a6ad8d-957b-4a36-9e9b-762baf64ed72-00%40eu-central-1.amazonses.com.

Re: [Django] #15759: list_editable should respect per-object permissions

[Django]

#15759: list_editable should respect per-object permissions
---+
 Reporter:  Jeremy Dunck   |Owner:  nobody
 Type:  Bug|   Status:  new
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:  0
---+
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e32f4f9da-3b19bdcd-137d-4c80-bff3-15145df1764c-00%40eu-central-1.amazonses.com.

Re: [Django] #16376: Support for database links

[Django]

#16376: Support for database links
-+-
 Reporter:   |Owner:  nobody
  stephane.benchimol@…   |
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle postgres  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e32f46dc1-5be90271-dca3-4447-a86d-21e7dc8231b5-00%40eu-central-1.amazonses.com.

Re: [Django] #34277: Add where clause in QuerySet.bulk_create() when update_conflicts=True

[Django]

#34277: Add where clause in QuerySet.bulk_create() when update_conflicts=True
-+-
 Reporter:  Alain Delplanque |Owner:  HAMA
 |  Barhamou
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 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 HAMA Barhamou):

 * 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/0107018e32b78bd1-b40458af-7c9e-4cea-a3b6-6e64039aed6d-00%40eu-central-1.amazonses.com.

Re: [Django] #35293: Django 5.x changes the date format on an from "2012-10-01" to "01/10/2012"

[Django]

#35293: Django 5.x changes the date format on an  from
"2012-10-01" to "01/10/2012"
-+--
 Reporter:  Shaheed Haque|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  5.0
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Comment (by Shaheed Haque):

 FWIW, I meant to say I was running version 4.2.11, but I had not spotted
 the need to create custom format files. Thanks for the pointer.
-- 
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/0107018e3281c953-e55b743a-98c2-4a92-8da7-121db696f261-00%40eu-central-1.amazonses.com.

Re: [Django] #35293: Django 5.x changes the date format on an from "2012-10-01" to "01/10/2012"

[Django]

#35293: Django 5.x changes the date format on an  from
"2012-10-01" to "01/10/2012"
-+--
 Reporter:  Shaheed Haque|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  5.0
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Comment (by David Sanders):

 To further Tim's points, if you look back at the 4.0 release notes it
 documents that `USE_L10N = True` is the _default_ behaviour which means
 that in Django 5.0 you now need to override where Django finds its
 localisation if you want to preserve the "old default" values for
 `DATE_FORMAT`, etc.

 Please see: https://docs.djangoproject.com/en/5.0/topics/i18n/formatting
 /#creating-custom-format-files
-- 
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/0107018e325cbf96-c270aad7-f96c-4e68-8da1-a7e266eac168-00%40eu-central-1.amazonses.com.

Re: [Django] #35293: Django 5.x changes the date format on an from "2012-10-01" to "01/10/2012"

[Django]

#35293: Django 5.x changes the date format on an  from
"2012-10-01" to "01/10/2012"
-+--
 Reporter:  Shaheed Haque|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  5.0
 Severity:  Normal   |   Resolution:  needsinfo
 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 Tim Graham):

 * resolution:   => needsinfo
 * status:  new => closed
 * type:  Uncategorized => Bug

Comment:

 The description mentions Django 4.11 but this isn't a valid version. Did
 you mean 4.1?

 This looks relevant from the Djagno 5.0 release notes, "The USE_L10N
 setting is removed." (8d98f99a4ab5de6f2c730399f53eba8bf6bea470) Did you
 test your project with deprecation warnings enabled? Does the behavior
 change in Django 4.x if setting `USE_L10N=True`.

 If that's not the cause, you can try
 [https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
 tickets/#bisecting-a-regression bisecting] to find the commit where the
 behavior changed.

 If you need help debugging, see TicketClosingReasons/UseSupportChannels
 and reopen the ticket if you determine this is a bug in 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/0107018e32582f8e-3a83b192-e2bf-40fd-8563-3aaa42150587-00%40eu-central-1.amazonses.com.

[Django] #35293: Django 5.x changes the date format on an from "2012-10-01" to "01/10/2012"

[Django]

#35293: Django 5.x changes the date format on an  from
"2012-10-01" to "01/10/2012"
---+
   Reporter:  Shaheed Haque|  Owner:  nobody
   Type:  Uncategorized| Status:  new
  Component:  Template system  |Version:  5.0
   Severity:  Normal   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 We are attempting to migrate from Django 4.11 to Django 5.0.latest. Our
 tests identified that Date inputs which were previous rendered with a
 "value" attribute in ISO8601 date format now seem to be rendered using en-
 GB. Here is what the 4.x renders:

 {{{
 
 }}}

 versus what 5.x renders:

 {{{
 
 }}}

 Our settings have not changed. Here is a subset of what we have:

 {{{
 LANGUAGE_CODE = 'en-gb'
 LANGUAGES = (
 ('en-gb', _('English (GB)')),
 )
 TIME_ZONE = 'UTC'
 USE_I18N = True
 USE_L10N = False
 USE_TZ = True
 }}}

 Note that we do NOT have any of the DATE_FORMAT, DATE_INPUT_FORMATS etc.
 set, so they should have their default values. I have reviewed the release
 notes but did not see anything relevant. I have tried debugging the code
 in django.utils.formats but is not clear to me where the difference
 originates.

 In case it is relevant, we are using the Jinja backend with bootstrap
 styling and our own templates, but the core "field" rendering should be
 whatever Django does.
-- 
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/0107018e324aec36-736deb4f-4b5e-48f4-ae6b-d3ee81f805d5-00%40eu-central-1.amazonses.com.

Re: [Django] #20757: A more Object-Oriented URLResolver

[Django]

#20757: A more Object-Oriented URLResolver
+
 Reporter:  Flavio Curella  |Owner:  (none)
 Type:  New feature |   Status:  new
Component:  Core (URLs) |  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:  0
+
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e32426df4-418e3e5f-0d18-4774-b718-66aacb6f5faf-00%40eu-central-1.amazonses.com.

Re: [Django] #20768: Create a reference of public Manager methods

[Django]

#20768: Create a reference of public Manager methods
+
 Reporter:  Ramiro Morales  |Owner:  nobody
 Type:  New feature |   Status:  new
Component:  Documentation   |  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:  0
+
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e3241410b-0534ff40-8193-4eb9-b859-f09bf4713a70-00%40eu-central-1.amazonses.com.

Re: [Django] #20799: Document how to use FastCGI via WSGI

[Django]

#20799: Document how to use FastCGI via WSGI
---+
 Reporter:  Tim Graham |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  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:  0
---+
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e3240c74f-a286c100-6561-49cb-9930-66e35996a7be-00%40eu-central-1.amazonses.com.

Re: [Django] #20824: User Auth: A Complete Solution for Email Login Handling

[Django]

#20824: User Auth: A Complete Solution for Email Login Handling
-+-
 Reporter:  JJZolper |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  contrib.auth |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  User Auth Email  | Triage Stage:  Accepted
  Login Handling |
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e32406fa9-0901fe5e-2fa0-4c60-a669-9f0a4a8b721c-00%40eu-central-1.amazonses.com.

Re: [Django] #20915: Remove django.test.client dependency on django.contrib.auth (and .sessions?)

[Django]

#20915: Remove django.test.client dependency on django.contrib.auth (and
.sessions?)
--+
 Reporter:  Ramiro Morales|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  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:  0
--+
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e323f7789-804c2119-60d9-4d70-a02d-b6ab2e999037-00%40eu-central-1.amazonses.com.

Re: [Django] #35292: Restore autofocus functionality to admin search box within popup interface

[Django]

#35292: Restore autofocus functionality to admin search box within popup 
interface
-+-
 Reporter:  mulmat   |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.admin|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:
  screen reader, keyboard|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by mulmat:

Old description:

> After recently upgrading to Django 4, we've had users report issues
> related to the changes made in #34040. The users perform quite a lot of
> these searches, and an extra click to focus the search box annoys them. I
> wonder if it would be possible to restore the autofocus functionality
> when in popup? In the popup context, I think it makes sense to autofocus
> the search box.

New description:

 After recently upgrading to Django 4, we've had users report issues
 related to the changes made in #34040. The users perform quite a lot of
 these searches, and an extra click to focus the search box annoys them. I
 wonder if it would be possible to restore the autofocus functionality when
 in popup? In the popup context, I think it makes sense to autofocus the
 search box since usability greatly improves.

--
-- 
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/0107018e32122097-169f6c64-e22f-493e-a251-3e104f4defd9-00%40eu-central-1.amazonses.com.

Re: [Django] #35290: Whitenoise Not Working when DEBUG = FALSE - Django - Hosting Static Files (was: 500 Server error. Whitenoise Not Working when DEBUG = FALSE - Django - Hosting Static Files)

[Django]

#35290: Whitenoise Not Working when DEBUG = FALSE - Django - Hosting Static 
Files
-+-
 Reporter:  Shihab Khan  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.staticfiles  |  Version:  4.2
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  500 Server error,| Triage Stage:
  Whitenoise,  DEBUG = FALSE |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * resolution:   => invalid
 * status:  new => closed
 * summary:
 500 Server error. Whitenoise Not Working when DEBUG = FALSE - Django -
 Hosting Static Files
 =>
 Whitenoise Not Working when DEBUG = FALSE - Django - Hosting Static
 Files

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/0107018e320f209f-be096746-e1f5-4d7a-b2eb-2cde556b1d5b-00%40eu-central-1.amazonses.com.

Re: [Django] #35291: Whitenoise Not Working when DEBUG = FALSE - Django - Hosting Static Files (was: 500 Server error. Whitenoise Not Working when DEBUG = FALSE - Django - Hosting Static Files)

[Django]

#35291: Whitenoise Not Working when DEBUG = FALSE - Django - Hosting Static 
Files
-+-
 Reporter:  Shihab Khan  |Owner:  (none)
 Type:  Bug  |   Status:  closed
Component:  Uncategorized|  Version:  4.2
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  500 Server error,| Triage Stage:
  Whitenoise,  DEBUG = FALSE |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * summary:
 500 Server error. Whitenoise Not Working when DEBUG = FALSE - Django -
 Hosting Static Files
 =>
 Whitenoise Not Working when DEBUG = FALSE - Django - Hosting Static
 Files

-- 
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/0107018e320d85cf-9e6714b8-20a1-43fc-b9f1-1056acc79442-00%40eu-central-1.amazonses.com.

Re: [Django] #35292: Restore autofocus functionality to admin search box within popup interface

[Django]

#35292: Restore autofocus functionality to admin search box within popup 
interface
-+-
 Reporter:  Mattias L|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.admin|  Version:  5.0
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:
  screen reader, keyboard|  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Mattias L):

 PR up here: https://github.com/django/django/pull/17967
-- 
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/0107018e320d6909-b6d29d72-5ee2-42a9-a1e7-cd911d264da4-00%40eu-central-1.amazonses.com.

Re: [Django] #35291: 500 Server error. Whitenoise Not Working when DEBUG = FALSE - Django - Hosting Static Files

[Django]

#35291: 500 Server error. Whitenoise Not Working when DEBUG = FALSE - Django -
Hosting Static Files
-+-
 Reporter:  Shihab Khan  |Owner:  (none)
 Type:  Bug  |   Status:  closed
Component:  Uncategorized|  Version:  4.2
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  500 Server error,| Triage Stage:
  Whitenoise,  DEBUG = FALSE |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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

Comment:

 Duplicate of #35290.
-- 
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/0107018e320d08db-d9adea1a-9be5-4710-92f3-d814f5f3e8d5-00%40eu-central-1.amazonses.com.

Re: [Django] #35290: 500 Server error. Whitenoise Not Working when DEBUG = FALSE - Django - Hosting Static Files

[Django]

#35290: 500 Server error. Whitenoise Not Working when DEBUG = FALSE - Django -
Hosting Static Files
-+-
 Reporter:  Shihab Khan  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:  500 Server error,| Triage Stage:
  Whitenoise,  DEBUG = FALSE |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Shihab Khan:

Old description:

> I am running a Django website and it's about to go into production. I am
> now at the point where I need to set DEBUG = False in my settings.py
> file. I am getting the typical 500 errors because I have static files
> that are being hosted locally. I am working on getting Whitenoise to work
> to host my static files so I can move on with DEBUG = False. I have
> followed a lot of documentation and a lot of tutorials and think all of
> my configurations are all set but I am still getting the same error. When
> DEBUG = False I am still getting 500 errors on my production pages that
> have static files. Also when I inspect any static files on the page when
> DEBUG = True the URL has not changed at all. I am posting all of my
> configuration below in hopes that there is a simple mistake I made that I
> have been continuously skipped over but Whitenoise doesn't seem to be
> working and there seems to be no different from the way it was before now
> as Whitenoise is "implemented".
>
> I have run python manage.py collect static
>
> I have run pip install whitenoise
>
> I am new to white noise so I am just basing my knowledge on the tutorials
> and documentation I have found.
>

>

> setting.py
> from pathlib import Path
> import os
>
> # Build paths inside the project like this: BASE_DIR / 'subdir'.
> BASE_DIR = Path(__file__).resolve().parent.parent
>
> def load_env():
> env_file = os.path.join(BASE_DIR, '.env')
> if os.path.exists(env_file):
> with open(env_file, 'r') as file:
> for line in file:
> line = line.strip()
> if line and not line.startswith("#"):
> key, value = line.split('=')
> os.environ[key] = value
>
> # Load environment variables from the .env file
> load_env()
>
> # Quick-start development settings - unsuitable for production
> # See https://docs.djangoproject.com/en/4.2/howto/deployment/checklist/
>
> # SECURITY WARNING: keep the secret key used in production secret!
> SECRET_KEY = 'django-
> insecure-x=qe5@^3%@t1fk)pk@uyv&r!z^#9==^*-&aiqfau3@9x@+j%nm'
>
> # SECURITY WARNING: don't run with debug turned on in production!
> DEBUG = True if os.getenv('DEBUG') == 'True' else False
>
> ALLOWED_HOSTS = os.getenv('ALLOWED_HOSTS').split(',')
>

> # Application definition
>
> INSTALLED_APPS = [
> 'django.contrib.admin',
> 'django.contrib.auth',
> 'django.contrib.contenttypes',
> 'django.contrib.sessions',
> 'django.contrib.messages',
> 'django.contrib.staticfiles',
> 'accounts',
> 'home',
> 'about',
> 'pricing',
> 'blog',
> 'contact',
> 'service',
> 'project',
> 'settings',
> 'legal',
> 'menus',
> 'adminapp',
> 'marketing',
> 'custompage',
> 'ckeditor',
> ]
>
> MIDDLEWARE = [
> 'django.middleware.security.SecurityMiddleware',
> 'django.contrib.sessions.middleware.SessionMiddleware',
> 'django.middleware.common.CommonMiddleware',
> 'django.middleware.csrf.CsrfViewMiddleware',
> 'django.contrib.auth.middleware.AuthenticationMiddleware',
> 'django.contrib.messages.middleware.MessageMiddleware',
> 'django.middleware.clickjacking.XFrameOptionsMiddleware',
> ]
>
> if os.getenv('DEMO_MODE') == 'True':
> MIDDLEWARE.append('core.middleware.middleware.DemoModeMiddleware')
>
> if os.getenv("WHITENOISE_CONFIG") == "True":
> MIDDLEWARE.insert(1, 'whitenoise.middleware.WhiteNoiseMiddleware')
>

> ROOT_URLCONF = 'core.urls'
>
> TEMPLATES = [
> {
> 'BACKEND': 'django.template.backends.django.DjangoTemplates',
> 'DIRS': [os.path.join(BASE_DIR, os.getenv('TEMPLATES_DIRS'))],
> 'APP_DIRS': True,
> 'OPTIONS': {
> 'context_processors': [
> 'django.template.context_processors.debug',
> 'django.template.context_processors.request',
> 'django.contrib.auth.context_processors.auth',
> 'django.contrib.messages.context_processors.messages',
> 'core.context_processors.website_settings_context',
>

[Django] #35292: Restore autofocus functionality to admin search box within popup interface

[Django]

#35292: Restore autofocus functionality to admin search box within popup 
interface
-+-
   Reporter:  mulmat |  Owner:  nobody
   Type: | Status:  new
  Uncategorized  |
  Component: |Version:  5.0
  contrib.admin  |   Keywords:  accessibility,
   Severity:  Normal |  screen reader, keyboard
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 After recently upgrading to Django 4, we've had users report issues
 related to the changes made in #34040. The users perform quite a lot of
 these searches, and an extra click to focus the search box annoys them. I
 wonder if it would be possible to restore the autofocus functionality when
 in popup? In the popup context, I think it makes sense to autofocus the
 search box.
-- 
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/0107018e3202f3a5-4384e763-ca7e-4025-bc89-1544bcf0af15-00%40eu-central-1.amazonses.com.

Re: [Django] #35291: 500 Server error. Whitenoise Not Working when DEBUG = FALSE - Django - Hosting Static Files

[Django]

#35291: 500 Server error. Whitenoise Not Working when DEBUG = FALSE - Django -
Hosting Static Files
-+-
 Reporter:  Shihab Khan  |Owner:  (none)
 Type:  Bug  |   Status:  assigned
Component:  Uncategorized|  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:  500 Server error,| Triage Stage:
  Whitenoise,  DEBUG = FALSE |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Shihab Khan):

 python manage.py collectstaticcommand


 {{{
 (venv) PS C:\Users\intevers\Downloads\django\intevers> python manage.py
 collectstatic

 You have requested to collect static files at the destination
 location as specified in your settings:

 C:\Users\intevers\Downloads\django\intevers\assets

 This will overwrite existing files!
 Are you sure you want to do this?

 Type 'yes' to continue, or 'no' to cancel: yes
 Post-processing 'admin\assets\css\vendors\icon\font-awesome\all.min.css'
 failed!

 Traceback (most recent call last):
   File "C:\Users\intevers\Downloads\django\intevers\manage.py", line 22,
 in 
 main()
   File "C:\Users\intevers\Downloads\django\intevers\manage.py", line 18,
 in main
 execute_from_command_line(sys.argv)
   File "C:\Users\intevers\Downloads\django\intevers\venv\lib\site-
 packages\django\core\management\__init__.py", line 442, in
 execute_from_command_line
 utility.execute()
   File "C:\Users\intevers\Downloads\django\intevers\venv\lib\site-
 packages\django\core\management\__init__.py", line 436, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "C:\Users\intevers\Downloads\django\intevers\venv\lib\site-
 packages\django\core\management\base.py", line 412, in run_from_argv
 self.execute(*args, **cmd_options)
   File "C:\Users\intevers\Downloads\django\intevers\venv\lib\site-
 packages\django\core\management\base.py", line 458, in execute
 output = self.handle(*args, **options)
   File "C:\Users\intevers\Downloads\django\intevers\venv\lib\site-
 packages\django\contrib\staticfiles\management\commands\collectstatic.py",
 line 209, in hand
 le
 collected = self.collect()
   File "C:\Users\intevers\Downloads\django\intevers\venv\lib\site-
 packages\django\contrib\staticfiles\management\commands\collectstatic.py",
 line 154, in coll
 ect
 raise processed
 whitenoise.storage.MissingFileError: The file
 'admin/assets/css/vendors/icon/webfonts/fa-brands-400.woff2' could not be
 found with .

 The CSS file 'admin\assets\css\vendors\icon\font-awesome\all.min.css'
 references a file which could not be found:
   admin/assets/css/vendors/icon/webfonts/fa-brands-400.woff2

 Please check the URL references in this CSS file, particularly any
 relative paths which might be pointing to the wrong location.
 }}}
-- 
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/0107018e31fce0f5-29dfb2c7-47dc-45b8-85e3-9a436f8d77d4-00%40eu-central-1.amazonses.com.

Re: [Django] #35290: 500 Server error. Whitenoise Not Working when DEBUG = FALSE - Django - Hosting Static Files

[Django]

#35290: 500 Server error. Whitenoise Not Working when DEBUG = FALSE - Django -
Hosting Static Files
-+-
 Reporter:  Shihab Khan  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:  500 Server error,| Triage Stage:
  Whitenoise,  DEBUG = FALSE |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Shihab Khan):

 python manage.py collectstaticcommand


 {{{
 (venv) PS C:\Users\intevers\Downloads\django\intevers> python manage.py
 collectstatic

 You have requested to collect static files at the destination
 location as specified in your settings:

 C:\Users\intevers\Downloads\django\intevers\assets

 This will overwrite existing files!
 Are you sure you want to do this?

 Type 'yes' to continue, or 'no' to cancel: yes
 Post-processing 'admin\assets\css\vendors\icon\font-awesome\all.min.css'
 failed!

 Traceback (most recent call last):
   File "C:\Users\intevers\Downloads\django\intevers\manage.py", line 22,
 in 
 main()
   File "C:\Users\intevers\Downloads\django\intevers\manage.py", line 18,
 in main
 execute_from_command_line(sys.argv)
   File "C:\Users\intevers\Downloads\django\intevers\venv\lib\site-
 packages\django\core\management\__init__.py", line 442, in
 execute_from_command_line
 utility.execute()
   File "C:\Users\intevers\Downloads\django\intevers\venv\lib\site-
 packages\django\core\management\__init__.py", line 436, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "C:\Users\intevers\Downloads\django\intevers\venv\lib\site-
 packages\django\core\management\base.py", line 412, in run_from_argv
 self.execute(*args, **cmd_options)
   File "C:\Users\intevers\Downloads\django\intevers\venv\lib\site-
 packages\django\core\management\base.py", line 458, in execute
 output = self.handle(*args, **options)
   File "C:\Users\intevers\Downloads\django\intevers\venv\lib\site-
 packages\django\contrib\staticfiles\management\commands\collectstatic.py",
 line 209, in hand
 le
 collected = self.collect()
   File "C:\Users\intevers\Downloads\django\intevers\venv\lib\site-
 packages\django\contrib\staticfiles\management\commands\collectstatic.py",
 line 154, in coll
 ect
 raise processed
 whitenoise.storage.MissingFileError: The file
 'admin/assets/css/vendors/icon/webfonts/fa-brands-400.woff2' could not be
 found with .

 The CSS file 'admin\assets\css\vendors\icon\font-awesome\all.min.css'
 references a file which could not be found:
   admin/assets/css/vendors/icon/webfonts/fa-brands-400.woff2

 Please check the URL references in this CSS file, particularly any
 relative paths which might be pointing to the wrong location.
 }}}
-- 
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/0107018e31fc94f1-33aa3843-b392-423f-836a-d390c8cc06e5-00%40eu-central-1.amazonses.com.

Re: [Django] #35291: 500 Server error. Whitenoise Not Working when DEBUG = FALSE - Django - Hosting Static Files

[Django]

#35291: 500 Server error. Whitenoise Not Working when DEBUG = FALSE - Django -
Hosting Static Files
-+-
 Reporter:  Shihab Khan  |Owner:  (none)
 Type:  Bug  |   Status:  assigned
Component:  Uncategorized|  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:  500 Server error,| Triage Stage:
  Whitenoise,  DEBUG = FALSE |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Shihab Khan):

 * Attachment "aaaCapture.JPG" 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/0107018e31f5c96c-79401515-7c68-43f9-accd-4015a4a15b51-00%40eu-central-1.amazonses.com.

[Django] #35291: 500 Server error. Whitenoise Not Working when DEBUG = FALSE - Django - Hosting Static Files

[Django]

#35291: 500 Server error. Whitenoise Not Working when DEBUG = FALSE - Django -
Hosting Static Files
-+-
   Reporter:  Shihab |  Owner:  (none)
  Khan   |
   Type:  Bug| Status:  assigned
  Component: |Version:  4.2
  Uncategorized  |   Keywords:  500 Server error,
   Severity:  Normal |  Whitenoise,  DEBUG = FALSE
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I am running a Django website and it's about to go into production. I am
 now at the point where I need to set DEBUG = False in my settings.py file.
 I am getting the typical 500 errors because I have static files that are
 being hosted locally. I am working on getting Whitenoise to work to host
 my static files so I can move on with DEBUG = False. I have followed a lot
 of documentation and a lot of tutorials and think all of my configurations
 are all set but I am still getting the same error. When DEBUG = False I am
 still getting 500 errors on my production pages that have static files.
 Also when I inspect any static files on the page when DEBUG = True the URL
 has not changed at all. I am posting all of my configuration below in
 hopes that there is a simple mistake I made that I have been continuously
 skipped over but Whitenoise doesn't seem to be working and there seems to
 be no different from the way it was before now as Whitenoise is
 "implemented".
 I have run python manage.py collect static
 I have run pip install whitenoise
 I am new to white noise so I am just basing my knowledge on the tutorials
 and documentation I have found.


 settings.py

 {{{
 from pathlib import Path
 import os

 # Build paths inside the project like this: BASE_DIR / 'subdir'.
 BASE_DIR = Path(__file__).resolve().parent.parent

 def load_env():
 env_file = os.path.join(BASE_DIR, '.env')
 if os.path.exists(env_file):
 with open(env_file, 'r') as file:
 for line in file:
 line = line.strip()
 if line and not line.startswith("#"):
 key, value = line.split('=')
 os.environ[key] = value

 # Load environment variables from the .env file
 load_env()

 # Quick-start development settings - unsuitable for production
 # See https://docs.djangoproject.com/en/4.2/howto/deployment/checklist/

 # SECURITY WARNING: keep the secret key used in production secret!
 SECRET_KEY = 'django-
 insecure-x=qe5@^3%@t1fk)pk@uyv&r!z^#9==^*-&aiqfau3@9x@+j%nm'

 # SECURITY WARNING: don't run with debug turned on in production!
 DEBUG = True if os.getenv('DEBUG') == 'True' else False

 ALLOWED_HOSTS = os.getenv('ALLOWED_HOSTS').split(',')


 # Application definition

 INSTALLED_APPS = [
 'django.contrib.admin',
 'django.contrib.auth',
 'django.contrib.contenttypes',
 'django.contrib.sessions',
 'django.contrib.messages',
 'django.contrib.staticfiles',
 'accounts',
 'home',
 'about',
 'pricing',
 'blog',
 'contact',
 'service',
 'project',
 'settings',
 'legal',
 'menus',
 'adminapp',
 'marketing',
 'custompage',
 'ckeditor',
 ]

 MIDDLEWARE = [
 'django.middleware.security.SecurityMiddleware',
 'django.contrib.sessions.middleware.SessionMiddleware',
 'django.middleware.common.CommonMiddleware',
 'django.middleware.csrf.CsrfViewMiddleware',
 'django.contrib.auth.middleware.AuthenticationMiddleware',
 'django.contrib.messages.middleware.MessageMiddleware',
 'django.middleware.clickjacking.XFrameOptionsMiddleware',
 ]

 if os.getenv('DEMO_MODE') == 'True':
 MIDDLEWARE.append('core.middleware.middleware.DemoModeMiddleware')

 if os.getenv("WHITENOISE_CONFIG") == "True":
 MIDDLEWARE.insert(1, 'whitenoise.middleware.WhiteNoiseMiddleware')


 ROOT_URLCONF = 'core.urls'

 TEMPLATES = [
 {
 'BACKEND': 'django.template.backends.django.DjangoTemplates',
 'DIRS': [os.path.join(BASE_DIR, os.getenv('TEMPLATES_DIRS'))],
 'APP_DIRS': True,
 'OPTIONS': {
 'context_processors': [
 'django.template.context_processors.debug',
 'django.template.context_processors.request',
 'django.contrib.auth.context_processors.auth',
 'django.contrib.messages.context_processors.messages',
 'core.context_processors.website_settings_context',
 'core.context_processors.seo_settings_context',
 'core.context_processors.header_footer_context',

[Django] #35290: 500 Server error. Whitenoise Not Working when DEBUG = FALSE - Django - Hosting Static Files

[Django]

#35290: 500 Server error. Whitenoise Not Working when DEBUG = FALSE - Django -
Hosting Static Files
-+-
   Reporter: |  Owner:  nobody
  cyberindav |
   Type:  Bug| Status:  new
  Component: |Version:  4.2
  contrib.staticfiles|   Keywords:  500 Server error,
   Severity:  Normal |  Whitenoise,  DEBUG = FALSE
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I am running a Django website and it's about to go into production. I am
 now at the point where I need to set DEBUG = False in my settings.py file.
 I am getting the typical 500 errors because I have static files that are
 being hosted locally. I am working on getting Whitenoise to work to host
 my static files so I can move on with DEBUG = False. I have followed a lot
 of documentation and a lot of tutorials and think all of my configurations
 are all set but I am still getting the same error. When DEBUG = False I am
 still getting 500 errors on my production pages that have static files.
 Also when I inspect any static files on the page when DEBUG = True the URL
 has not changed at all. I am posting all of my configuration below in
 hopes that there is a simple mistake I made that I have been continuously
 skipped over but Whitenoise doesn't seem to be working and there seems to
 be no different from the way it was before now as Whitenoise is
 "implemented".

 I have run python manage.py collect static

 I have run pip install whitenoise

 I am new to white noise so I am just basing my knowledge on the tutorials
 and documentation I have found.




 setting.py
 from pathlib import Path
 import os

 # Build paths inside the project like this: BASE_DIR / 'subdir'.
 BASE_DIR = Path(__file__).resolve().parent.parent

 def load_env():
 env_file = os.path.join(BASE_DIR, '.env')
 if os.path.exists(env_file):
 with open(env_file, 'r') as file:
 for line in file:
 line = line.strip()
 if line and not line.startswith("#"):
 key, value = line.split('=')
 os.environ[key] = value

 # Load environment variables from the .env file
 load_env()

 # Quick-start development settings - unsuitable for production
 # See https://docs.djangoproject.com/en/4.2/howto/deployment/checklist/

 # SECURITY WARNING: keep the secret key used in production secret!
 SECRET_KEY = 'django-
 insecure-x=qe5@^3%@t1fk)pk@uyv&r!z^#9==^*-&aiqfau3@9x@+j%nm'

 # SECURITY WARNING: don't run with debug turned on in production!
 DEBUG = True if os.getenv('DEBUG') == 'True' else False

 ALLOWED_HOSTS = os.getenv('ALLOWED_HOSTS').split(',')


 # Application definition

 INSTALLED_APPS = [
 'django.contrib.admin',
 'django.contrib.auth',
 'django.contrib.contenttypes',
 'django.contrib.sessions',
 'django.contrib.messages',
 'django.contrib.staticfiles',
 'accounts',
 'home',
 'about',
 'pricing',
 'blog',
 'contact',
 'service',
 'project',
 'settings',
 'legal',
 'menus',
 'adminapp',
 'marketing',
 'custompage',
 'ckeditor',
 ]

 MIDDLEWARE = [
 'django.middleware.security.SecurityMiddleware',
 'django.contrib.sessions.middleware.SessionMiddleware',
 'django.middleware.common.CommonMiddleware',
 'django.middleware.csrf.CsrfViewMiddleware',
 'django.contrib.auth.middleware.AuthenticationMiddleware',
 'django.contrib.messages.middleware.MessageMiddleware',
 'django.middleware.clickjacking.XFrameOptionsMiddleware',
 ]

 if os.getenv('DEMO_MODE') == 'True':
 MIDDLEWARE.append('core.middleware.middleware.DemoModeMiddleware')

 if os.getenv("WHITENOISE_CONFIG") == "True":
 MIDDLEWARE.insert(1, 'whitenoise.middleware.WhiteNoiseMiddleware')


 ROOT_URLCONF = 'core.urls'

 TEMPLATES = [
 {
 'BACKEND': 'django.template.backends.django.DjangoTemplates',
 'DIRS': [os.path.join(BASE_DIR, os.getenv('TEMPLATES_DIRS'))],
 'APP_DIRS': True,
 'OPTIONS': {
 'context_processors': [
 'django.template.context_processors.debug',
 'django.template.context_processors.request',
 'django.contrib.auth.context_processors.auth',
 'django.contrib.messages.context_processors.messages',
 'core.context_processors.website_settings_context',
 'core.context_processors.seo_settings_context',
 'core.context_processors.header_footer_context',
 'core.

Re: [Django] #21295: Add on_update support

[Django]

#21295: Add on_update support
-+-
 Reporter:  Anssi Kääriäinen |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 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
-+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e31dfcfdd-8feef03b-5e96-4f70-9749-472ebea809c2-00%40eu-central-1.amazonses.com.

Re: [Django] #24800: Add logging of applied/unapplied migrations

[Django]

#24800: Add logging of applied/unapplied migrations
---+
 Reporter:  Markus Holtermann  |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  Migrations |  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 Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e31def3d8-202ad838-2e89-4712-8313-9948a801dabc-00%40eu-central-1.amazonses.com.

Re: [Django] #24901: makemigrations should create empty migrations dir for any installed app without it

[Django]

#24901: makemigrations should create empty migrations dir for any installed app
without it
-+-
 Reporter:  Andriy Sokolovskiy   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Migrations   |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e31de524d-7421db3b-6a0f-46bc-88a9-ed38c0474f77-00%40eu-central-1.amazonses.com.

Re: [Django] #24928: Add UUIDField, RangeField, JSONField, etc to database introspection

[Django]

#24928: Add UUIDField, RangeField, JSONField, etc to database introspection
-+-
 Reporter:  Markus Holtermann|Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 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 Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e31dd5564-c27acb82-5a43-4f52-b9d2-e76359675229-00%40eu-central-1.amazonses.com.

Re: [Django] #25195: update_or_create doesn't understand F() operations

[Django]

#25195: update_or_create doesn't understand F() operations
-+-
 Reporter:  Marc Tamlyn  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (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 Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e31dd14fa-40c4e5f0-b8a0-4342-bd8c-dee802e368e3-00%40eu-central-1.amazonses.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:  (none)
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  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:  0
--+
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e31a2d516-cbd1fe41-eee9-438f-9a93-ac93b84bb8b9-00%40eu-central-1.amazonses.com.

Re: [Django] #32340: Usability issues with Django form fields expecting specific patterns

[Django]

#32340: Usability issues with Django form fields expecting specific patterns
-+-
 Reporter:  Thibaud Colas|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Accepted
  usability, forms   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e3190e40f-83a1d4ea-25c2-47d5-a5fe-691c7d656169-00%40eu-central-1.amazonses.com.

Re: [Django] #29640: Document (deprecate?) Paginator._get_page

[Django]

#29640: Document (deprecate?) Paginator._get_page
--+
 Reporter:  Josh Schneier |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  Version:  2.1
 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 Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e318dfa4a-87447503-f1ed-4a47-9522-b127fe5c9b41-00%40eu-central-1.amazonses.com.

Re: [Django] #29702: QuerySet database-side pattern regexp support

[Django]

#29702: QuerySet database-side pattern regexp support
-+-
 Reporter:  Alex Damian  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  new feature, | Triage Stage:  Accepted
  queryset, regex|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e318d4601-51cfd722-a337-4821-8ff8-f0dcdaa587b2-00%40eu-central-1.amazonses.com.

Re: [Django] #29762: Document how database routers are used for related object access

[Django]

#29762: Document how database routers are used for related object access
--+
 Reporter:  Vackar Afzal  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  2.0
 Severity:  Normal|   Resolution:
 Keywords:  oracle, multidb   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e318ca080-384c3744-a79d-4067-8b1e-5945dce803b5-00%40eu-central-1.amazonses.com.

Re: [Django] #29717: Provide a way for tests to run on an existing empty DB

[Django]

#29717: Provide a way for tests to run on an existing empty DB
-+-
 Reporter:  Curtis Maloney   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  2.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e318b464c-4b0742a4-0633-42f7-b461-f47f2c79e320-00%40eu-central-1.amazonses.com.

Re: [Django] #29790: Migration that switches a model to a UUID primary key fails with "duplicate column name: id"

[Django]

#29790: Migration that switches a model to a UUID primary key fails with 
"duplicate
column name: id"
-+-
 Reporter:  Richard Ebeling  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  2.1
 Severity:  Normal   |   Resolution:
 Keywords:  multiple primary | Triage Stage:  Accepted
  keys migration id uuid |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e318983e1-8164de98-3a6a-4a5f-bc03-d0cc2b9f4ae2-00%40eu-central-1.amazonses.com.

Re: [Django] #29884: QuerySet.filter() with TruncBase functions not working as expected when USE_TZ= True

[Django]

#29884: QuerySet.filter() with TruncBase functions not working as expected when
USE_TZ= True
-+-
 Reporter:  slide33  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.1
  (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 Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (added)


Old description:

> ** Tested PostgreSQL only **
> ** USE_TZ=True **
>
> Consider the following model:
>
> {{{
> class TimeStampModel(models.Model):
> timestamp = models.DateTimeField()
> }}}
>
> Create some data:
>
> {{{
>
> TimeStampModel.objects.bulk_create([
> TimeStampModel(timestamp=datetime.datetime(2018, 10, 24, 5, 13,
> tzinfo=pytz.utc)),
> TimeStampModel(timestamp=datetime.datetime(2018, 10, 24, 7, 4,
> tzinfo=pytz.utc)),
> TimeStampModel(timestamp=datetime.datetime(2018, 10, 24, 8, 56,
> tzinfo=pytz.utc)),
> TimeStampModel(timestamp=datetime.datetime(2018, 10, 24, 13, 49,
> tzinfo=pytz.utc)),
> TimeStampModel(timestamp=datetime.datetime(2018, 10, 24, 15, 33,
> tzinfo=pytz.utc)),
> TimeStampModel(timestamp=datetime.datetime(2018, 10, 24, 18, 29,
> tzinfo=pytz.utc)),
> TimeStampModel(timestamp=datetime.datetime(2018, 10, 24, 19, 12,
> tzinfo=pytz.utc)),
> TimeStampModel(timestamp=datetime.datetime(2018, 10, 24, 21, 37,
> tzinfo=pytz.utc)),
> TimeStampModel(timestamp=datetime.datetime(2018, 10, 24, 21, 9,
> tzinfo=pytz.utc)),
> TimeStampModel(timestamp=datetime.datetime(2018, 10, 24, 23, 23,
> tzinfo=pytz.utc)),
> ])
>
> }}}
>
> The following code shoud definitely return the data. But it returns an
> empty queryset, because the SQL generated is not correct.
>
> {{{
> >>> from django.db.models.functions import *
> >>> from django.utils import timezone
> >>> import datetime, pytz
> >>> TimeStampModel.objects.annotate(
> ... day=TruncDay('timestamp',
> tzinfo=pytz.timezone('Europe/Berlin'))).filter(
> ... day=timezone.make_aware(datetime.datetime(2018, 10, 24),
> pytz.timezone('Europe/Berlin'))
> ... )
> DEBUG: (0.000) SELECT "truncbase_timestampmodel"."id",
> "truncbase_timestampmodel"."timestamp", DATE_TRUNC('day',
> "truncbase_timestampmodel"."timestamp" AT TIME ZONE 'Europe/Berlin') AS
> "day" FROM "truncbase_timestampmodel" WHERE DATE_TRUNC('day',
> "truncbase_timestampmodel"."timestamp" AT TIME ZONE 'Europe/Berlin') =
> '2018-10-24T00:00:00+02:00'::timestamptz LIMIT 21;
> args=('datetime.datetime(2018, 10, 24, 0, 0, tzinfo= 'Europe/Berlin' CEST+2:00:00 DST>)')
> 
> }}}
>
> The SQL should be (note the additional `AT TIME ZONE 'Europe/Berlin'`):
>
> {{{
> SELECT "truncbase_timestampmodel"."id",
>"truncbase_timestampmodel"."timestamp",
>DATE_TRUNC('day', "truncbase_timestampmodel"."timestamp" AT TIME
> ZONE 'Europe/Berlin') AT TIME ZONE 'Europe/Berlin' AS "day"
> FROM "truncbase_timestampmodel"
> WHERE DATE_TRUNC('day', "truncbase_timestampmodel"."timestamp" AT TIME
> ZONE 'Europe/Berlin') AT TIME ZONE 'Europe/Berlin' =
> '2018-10-24T00:00:00+02:00'::timestamptz
> LIMIT 21;
> }}}
>
> https://www.postgresql.org/docs/9.2/static/functions-datetime.html
> #FUNCTIONS-DATETIME-ZONECONVERT
> This fix will also make sure that the returned value from the database
> driver is an aware dateime. Currently the returned value is native and
> manually made aware in
> `django.db.models.functions.datetime.TruncBase.convert_value`!
>
> I'm not sure how the problem relates to databases without timezone
> support. But for those with time zone support like PostgreSQL this should
> work as expected. For Postgres the fix should be pretty easy:
> `django.db.backends.postgresql.operations.DatabaseOperations.datetime_trunc_sql`
> has to be patched and
> `django.db.models.functions.datetime.TruncBase.convert_value` should be
> patched. The latter will also affect other database engines.

New description:

 ** Tested PostgreSQL only **
 ** USE_TZ=True **

 Consider the following model:

 {{{
 class TimeStampModel(models.Model):
 timestamp = models.DateTimeField()
 }}}

 Create some data:

 {{{

 TimeStampModel.objects.bulk_create([
 TimeStampModel(timestamp=datetime.datetime(2018, 10, 24, 5, 13,
 tzinfo=pytz.utc)),
 TimeStampModel(timestamp=datetime.datetime(2018, 10, 24, 7, 4,
 tzinfo=pytz.utc)),
 TimeStampModel(timestamp=datetime.datetime(2018, 10, 24, 8, 56,
 tzinfo=pytz.utc)),
 TimeStampModel(timestamp=datetime.datetime(2018, 10, 24, 13, 49,
 tzinf

Re: [Django] #30149: Empty value selected check in Admin Filter prevents subclassing

[Django]

#30149: Empty value selected check in Admin Filter prevents subclassing
--+
 Reporter:  Sardorbek Imomaliev   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:  admin | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e31876a27-be8e3b6c-be8f-451b-bc77-b227cb8f8290-00%40eu-central-1.amazonses.com.

Re: [Django] #30200: Add support for using indexes in update() for ArrayFields.

[Django]

#30200: Add support for using indexes in update() for ArrayFields.
-+-
 Reporter:  Mariusz Felisiak |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  contrib.postgres |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  ArrayField   | Triage Stage:  Accepted
  PostreSQL index update |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e31867016-2661fea0-d59d-432f-b955-4f4ceff7bea1-00%40eu-central-1.amazonses.com.

Re: [Django] #30138: Allow QuerySet.bulk_create() to set pk of created objects when ignore_conflicts=True

[Django]

#30138: Allow QuerySet.bulk_create() to set pk of created objects when
ignore_conflicts=True
-+-
 Reporter:  saber solooki|Owner:  (none)
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  2.2
  (models, ORM)  |
 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 Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e31854a12-fa3623a7-6cb5-4d8c-8246-b9248d4c5c32-00%40eu-central-1.amazonses.com.

Re: [Django] #31383: Make createcachetable use SchemaEditor for SQL generation

[Django]

#31383: Make createcachetable use SchemaEditor for SQL generation
-+-
 Reporter:  Tim Graham   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
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:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e3183d878-1399222c-37d4-4078-b914-6b17cdf9ee8a-00%40eu-central-1.amazonses.com.

Re: [Django] #25197: Add a more friendly widget for HStoreField

[Django]

#25197: Add a more friendly widget for HStoreField
---+
 Reporter:  gam_phon   |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords:  widget | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e3179968d-ca3b5e81-9819-4d2d-88d0-40f3740a888a-00%40eu-central-1.amazonses.com.

Re: [Django] #17664: {% if %} template tag silences exceptions inconsistently

[Django]

#17664: {% if %} template tag silences exceptions inconsistently
-+-
 Reporter:  Tai Lee  |Owner:  (none)
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  smart if tag | Triage Stage:  Accepted
  queryset exception silenced|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Ülgen Sarıkavak):

 * cc: Ülgen Sarıkavak (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/0107018e3176fdbd-55f952ac-acef-4cbc-8f83-bfd9139eb523-00%40eu-central-1.amazonses.com.