Re: [Django] #33701: Highlight error location in the technical 500 debug page on Python 3.11+.

[Django]

#33701: Highlight error location in the technical 500 debug page on Python 
3.11+.
-+-
 Reporter:  Adam Johnson |Owner:  Giebisch
 Type:  New feature  |   Status:  assigned
Component:  Error reporting  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070184c2426f1f-735c4dd9-d9b8-45b3-ae0c-522bdc0c7557-00%40eu-central-1.amazonses.com.

Re: [Django] #34187: UserCreationForm should save data from ManyToMany form fields

[Django]

#34187: UserCreationForm should save data from ManyToMany form fields
-+-
 Reporter:  Mark Gensler |Owner:  Mark
 |  Gensler
 Type:  New feature  |   Status:  closed
Component:  contrib.auth |  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  UserCreationForm | Triage Stage:  Ready for
  save_m2m   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"9d726c7902979d4ad53945ed8f1037266a88010d" 9d726c7]:
 {{{
 #!CommitTicketReference repository=""
 revision="9d726c7902979d4ad53945ed8f1037266a88010d"
 Fixed #34187 -- Made UserCreationForm save many-to-many fields.
 }}}

-- 
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/01070184c23581f6-9ba006e3-8fc8-42c9-bf7a-1fe44fe3b66e-00%40eu-central-1.amazonses.com.

Re: [Django] #34187: UserCreationForm should save data from ManyToMany form fields

[Django]

#34187: UserCreationForm should save data from ManyToMany form fields
-+-
 Reporter:  Mark Gensler |Owner:  Mark
 |  Gensler
 Type:  New feature  |   Status:  assigned
Component:  contrib.auth |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  UserCreationForm | Triage Stage:  Ready for
  save_m2m   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_docs:  1 => 0
 * stage:  Accepted => Ready for checkin


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070184c1c15dc9-606bf135-628d-4227-a5b0-58765e7aa9f9-00%40eu-central-1.amazonses.com.

[Django] #34188: Add a section on refresh_from_db to the Multiple databases documentation

[Django]

#34188: Add a section on refresh_from_db to the Multiple databases documentation
-+
   Reporter:  martinmain93   |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Documentation  |Version:  4.1
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+
 I've recently implemented multiple databases in a project using a read-
 replica setup, and everything went quite smoothly. The docs (
 https://docs.djangoproject.com/en/4.1/topics/db/multi-db/) were helpful to
 set up a simple database router and the appropriate config changes. One of
 the first big issues I ran into was that I quickly ran into errors any
 time in the app that `refresh_from_db` was being used. Because of the
 nature of the command, it's usually being issued when some action was
 committed and I want to get the latest data from the database. Of course
 this is going to be an issue with multiple databases. With some digging, I
 discovered that you can indeed use `refresh_from_db(using=db)` to select
 the default database. This quickly solved the issue.

 I think it would be very useful to anyone setting up a multi db setup to
 have a short section on the Multiple Databases docs that includes this
 information.

-- 
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/01070184c062cec5-29c5fa17-fb11-43a8-8920-016c9c5dc963-00%40eu-central-1.amazonses.com.

Re: [Django] #21961: Add support for database-level cascading options

[Django]

#21961: Add support for database-level cascading options
-+-
 Reporter:  Christophe Pettus|Owner:  Thibault
 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 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/01070184bf975891-c0f46fff-806c-41b1-be66-f6ee4155c9be-00%40eu-central-1.amazonses.com.

Re: [Django] #470: Add Field.db_default for defining database defaults

[Django]

#470: Add Field.db_default for defining database defaults
-+-
 Reporter:  jws  |Owner:  Lily
 |  Foote
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  normal   |   Resolution:
 Keywords:  sql schema   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
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/01070184bf91d1ff-441eecc8-9c83-419a-8a3f-e9d7d0d0e299-00%40eu-central-1.amazonses.com.

Re: [Django] #32915: ./manage runserver --nostatic still doesn't return a traceback

[Django]

#32915: ./manage runserver --nostatic still doesn't return a traceback
-+-
 Reporter:  Michael  |Owner:  bcail
 Type:  Bug  |   Status:  assigned
Component:  Core (Management |  Version:  3.2
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bcail):

 * cc: bcail (added)
 * needs_better_patch:  1 => 0
 * status:  new => assigned
 * owner:  (none) => bcail
 * needs_tests:  1 => 0


Comment:

 Opened a new PR from the previous one:
 https://github.com/django/django/pull/16337

-- 
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/01070184bf2c4ffb-52feacac-315e-41d4-b2d4-597a79f697df-00%40eu-central-1.amazonses.com.

Re: [Django] #31949: Allow builtin view decorators to be applied directly to async views.

[Django]

#31949: Allow builtin view decorators to be applied directly to async views.
+-
 Reporter:  Michael Galler  |Owner:  Ben Lomax
 Type:  New feature |   Status:  assigned
Component:  Core (Other)|  Version:  3.1
 Severity:  Normal  |   Resolution:
 Keywords:  async   | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+-
Changes (by Jon Janzen):

 * cc: Jon Janzen (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/01070184bef27061-d77cebc1-2b5a-48b3-b120-c7f3bb321b3f-00%40eu-central-1.amazonses.com.

Re: [Django] #34160: Django 4.1 Expression contains mixed types for (Big/Small)IntegerFields.

[Django]

#34160: Django 4.1 Expression contains mixed types for (Big/Small)IntegerFields.
-+-
 Reporter:  Martin Lehoux|Owner:  Martin
 |  Lehoux
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.1
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 `Case()` is trying to resolve an output type only for specific fields that
 cannot be implicitly cast on PostgreSQL (namely `GenericIPAddressField`,
 `IPAddressField`, `TimeField`, and `UUIDField`) in other cases PostgreSQL
 does the work, see [https://www.postgresql.org/docs/current/typeconv-
 union-case.html docs]. As far as I'm aware, we should be safe to ignore
 errors in resolving an output field in other cases:

 {{{#!diff
 diff --git a/django/db/models/expressions.py
 b/django/db/models/expressions.py
 index c270ef16c7..575712806f 100644
 --- a/django/db/models/expressions.py
 +++ b/django/db/models/expressions.py
 @@ -1483,8 +1483,11 @@ class Case(SQLiteNumericMixin, Expression):
  sql_params.extend(default_params)
  template = template or template_params.get("template",
 self.template)
  sql = template % template_params
 -if self._output_field_or_none is not None:
 -sql = connection.ops.unification_cast_sql(self.output_field)
 % sql
 +try:
 +if self._output_field_or_none is not None:
 +sql =
 connection.ops.unification_cast_sql(self.output_field) % sql
 +except FieldError:
 +pass
  return sql, sql_params

  def get_group_by_cols(self):
 }}}

-- 
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/01070184bd9da48f-428d6a48-324b-4d04-997b-fcfe8e54765e-00%40eu-central-1.amazonses.com.

Re: [Django] #34119: ModelForm fields with callable defaults don't correctly propagate default values

[Django]

#34119: ModelForm fields with callable defaults don't correctly propagate 
default
values
-+-
 Reporter:  Benjamin Rigaud  |Owner:  David
 |  Sanders
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  4.1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  modelform| Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by GitHub ):

 In [changeset:"60a7bd89860e504c0c33b02c78edcac87f6d1b5a" 60a7bd8]:
 {{{
 #!CommitTicketReference repository=""
 revision="60a7bd89860e504c0c33b02c78edcac87f6d1b5a"
 Refs #34119 -- Skipped
 test_callable_default_hidden_widget_value_not_overridden when JSONField is
 not supported.
 }}}

-- 
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/01070184bd6c4388-84eecb40-83a7-4fdd-8c04-0263148e184b-00%40eu-central-1.amazonses.com.

Re: [Django] #31169: Allow parallel test runner to work with Windows/macOS `spawn` process start method.

[Django]

#31169: Allow parallel test runner to work with Windows/macOS `spawn` process 
start
method.
-+-
 Reporter:  Brandon Navra|Owner:  David
 |  Smith
 Type:  New feature  |   Status:  closed
Component:  Testing framework|  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by GitHub ):

 In [changeset:"20d575b101608c1475bc2881f83b04da0e68ef7d" 20d575b]:
 {{{
 #!CommitTicketReference repository=""
 revision="20d575b101608c1475bc2881f83b04da0e68ef7d"
 Refs #31169 -- Skipped test_get_test_db_clone_settings_not_supported on
 not in-memory SQLite database.

 multiprocessing's start method is checked only for in-memory SQLite
 databases.
 }}}

-- 
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/01070184bd5c389e-0290c523-5e46-45e0-969c-650ad3b21525-00%40eu-central-1.amazonses.com.