Re: [Django] #35038: Changing violation_error_message on constraints cause a remove/add operation in migration

[Django]

#35038: Changing violation_error_message on constraints cause a remove/add
operation in migration
--+
 Reporter:  David |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  Version:  4.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 Salvo Polizzi):

 * owner:  Salvo Polizzi => (none)
 * status:  assigned => new


-- 
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/0107018caf652f80-3896da9d-ddbd-47b1-b6df-c97457d9a49e-00%40eu-central-1.amazonses.com.

Re: [Django] #33277: SimpleTestCase does not block database connections in threads

[Django]

#33277: SimpleTestCase does not block database connections in threads
-+-
 Reporter:  Daniel Hahler|Owner:  David
 |  Wobrock
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  Version:  3.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018caf1f308c-8c5ae8df-10ec-41b2-abab-120a9eccd54c-00%40eu-central-1.amazonses.com.

Re: [Django] #35051: HEAD Responses Drop Headers

[Django]

#35051: HEAD Responses Drop Headers
-+-
 Reporter:  Paul Bailey  |Owner:  Paul
 Type:   |  Bailey
  Cleanup/optimization   |   Status:  assigned
Component:  HTTP handling|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018caf0c4154-ec74a817-660e-4d22-a58c-cebe6f84bde1-00%40eu-central-1.amazonses.com.

Re: [Django] #35051: HEAD Responses Drop Headers

[Django]

#35051: HEAD Responses Drop Headers
-+-
 Reporter:  Paul Bailey  |Owner:  Paul
 Type:   |  Bailey
  Cleanup/optimization   |   Status:  assigned
Component:  HTTP handling|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * type:  New feature => Cleanup/optimization


-- 
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/0107018caefb0d31-71480ecc-79aa-4ff0-a733-823885cdc6f3-00%40eu-central-1.amazonses.com.

Re: [Django] #32114: Workaround for subtest issue with parallel test runner

[Django]

#32114: Workaround for subtest issue with parallel test runner
-+-
 Reporter:  Jordan Ephron|Owner:  David
 Type:   |  Wobrock
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  Version:  3.1
 Severity:  Normal   |   Resolution:
 Keywords:  Test subtest | Triage Stage:  Accepted
  parallel   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018caef6a44a-b7913b39-72a4-47e5-a1c0-136506161100-00%40eu-central-1.amazonses.com.

Re: [Django] #35065: Autocomplete field is not rendered with error color border. (was: Django Admin doesn't render autocomplete field whith error color border properly.)

[Django]

#35065: Autocomplete field is not rendered with error color border.
-+-
 Reporter:  Rigoberto Villalta   |Owner:  Rigoberto
 |  Villalta
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:  Django 5.0, Django   | Triage Stage:  Accepted
  4.2, Django Admin  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  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/0107018caed3f5df-134c9447-99ee-49fa-9ad2-89b031fdc6f9-00%40eu-central-1.amazonses.com.

Re: [Django] #35065: Django Admin doesn't render autocomplete field whith error color border properly.

[Django]

#35065: Django Admin doesn't render autocomplete field whith error color border
properly.
-+-
 Reporter:  Rigoberto Villalta   |Owner:  Rigoberto
 |  Villalta
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:  Django 5.0, Django   | Triage Stage:  Accepted
  4.2, Django Admin  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by Mariusz Felisiak):

 * owner:  nobody => Rigoberto Villalta
 * status:  new => assigned
 * has_patch:  1 => 0
 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Thanks for the report, please submit patch via GitHub 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/0107018caed2e175-f341cd08-d916-4a87-9224-940c99e4f480-00%40eu-central-1.amazonses.com.

Re: [Django] #25493: Model instances created with unittest.mock can raise confusing errors

[Django]

#25493: Model instances created with unittest.mock can raise confusing errors
-+-
 Reporter:  Josh Smeaton |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Marcelo Galigniana):

 Hello!

 I ran into this error and I also found the exception too confusing. I
 would like to fix it / improve the error message.

 Could be a fix check in `pre_save_val` if the attr value is a primitive
 python value? (Because is getting an ) object)
 
https://github.com/django/django/blob/751d732a3815a68bdb5b7aceda0e7d5981362c4a/django/db/models/sql/compiler.py#L1755

 Thank you!

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cae5e6798-944a3841-4d65-43a8-9744-245d04c46495-00%40eu-central-1.amazonses.com.

Re: [Django] #35051: HEAD Responses Drop Headers

[Django]

#35051: HEAD Responses Drop Headers
---+---
 Reporter:  Paul Bailey|Owner:  Paul Bailey
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+---
Changes (by Paul Bailey):

 * needs_better_patch:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018caddb5b13-2557084a-3f65-457a-8374-aa01a1fee7d3-00%40eu-central-1.amazonses.com.

Re: [Django] #35065: Django Admin doesn't render autocomplete field whith error color border properly.

[Django]

#35065: Django Admin doesn't render autocomplete field whith error color border
properly.
-+-
 Reporter:  Rigoberto Villalta   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:  Django 5.0, Django   | Triage Stage:
  4.2, Django Admin  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Description changed by Rigoberto Villalta:

Old description:

> In Django Admin, if the validations of an autocomplete fields fails, the
> border of the input field isn't´n of the error color (#ba2121 by
> default).
>

> Why? Because in that case the  {{{select html element}}} is hidden.
>
> You can test it int this repo [https://github.com/Rigo-Villalta/django-
> autocomplete-error-not-visible].
>
> Solution: I think the best solution is to add to the end of the file
> ''/static/admin/css/autocomplete.css'' the following rule:
>

> {{{
> .errors .select2-selection {
> border: 1px solid var(--error-fg);
> }
> }}}
>
> Someone could think that add the selector to the '' base.css'' file could
> works, but for inheritance doesn't work.
>
> I will push the pull request in a minutes, but I am not sure if is the
> best solution.

New description:

 In Django Admin, if the validations of an autocomplete fields fails, the
 border of the input field isn't´n of the error color (#ba2121 by default).

 [[Image(ticket:35065:django-admin-sample.PNG)]]

 Why? Because in that case the  {{{select html element}}} is hidden.

 You can test it int this repo [https://github.com/Rigo-Villalta/django-
 autocomplete-error-not-visible].

 Solution: I think the best solution is to add to the end of the file
 ''/static/admin/css/autocomplete.css'' the following rule:


 {{{
 .errors .select2-selection {
 border: 1px solid var(--error-fg);
 }
 }}}

 Someone could think that add the selector to the '' base.css'' file could
 works, but for inheritance doesn't work.

 I will push the pull request in a minutes, but I am not sure if is the
 best solution.

--

-- 
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/0107018cad601fa8-c1954a5e-bd40-4505-85ff-0630630a5d47-00%40eu-central-1.amazonses.com.

Re: [Django] #35065: Django Admin doesn't render autocomplete field whith error color border properly.

[Django]

#35065: Django Admin doesn't render autocomplete field whith error color border
properly.
-+-
 Reporter:  Rigoberto Villalta   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:  Django 5.0, Django   | Triage Stage:
  4.2, Django Admin  |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Rigoberto Villalta):

 * Attachment "django-admin-sample.PNG" 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/0107018cad5d4460-38527ffb-7e0f-4d1d-9fb0-c3f3cac94837-00%40eu-central-1.amazonses.com.

[Django] #35065: Django Admin doesn't render autocomplete field whith error color border properly.

[Django]

#35065: Django Admin doesn't render autocomplete field whith error color border
properly.
-+-
   Reporter:  Rigoberto  |  Owner:  nobody
  Villalta   |
   Type:  Bug| Status:  new
  Component: |Version:  4.2
  contrib.admin  |   Keywords:  Django 5.0, Django
   Severity:  Normal |  4.2, Django Admin
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  1  |
-+-
 In Django Admin, if the validations of an autocomplete fields fails, the
 border of the input field isn't´n of the error color (#ba2121 by default).


 Why? Because in that case the  {{{select html element}}} is hidden.

 You can test it int this repo [https://github.com/Rigo-Villalta/django-
 autocomplete-error-not-visible].

 Solution: I think the best solution is to add to the end of the file
 ''/static/admin/css/autocomplete.css'' the following rule:


 {{{
 .errors .select2-selection {
 border: 1px solid var(--error-fg);
 }
 }}}

 Someone could think that add the selector to the '' base.css'' file could
 works, but for inheritance doesn't work.

 I will push the pull request in a minutes, but I am not sure if is the
 best solution.

-- 
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/0107018cad5cf557-4226e997-9d47-4838-83aa-48a5de69f416-00%40eu-central-1.amazonses.com.

Re: [Django] #35056: admin.E013 on ManyToManyField with related_name crashes.

[Django]

#35056: admin.E013 on ManyToManyField with related_name crashes.
-+-
 Reporter:  Thomas Feldmann  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  5.0
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak ):

 In [changeset:"9a182f3d959d16354e24f34713df602f1bef6556" 9a182f3d]:
 {{{
 #!CommitTicketReference repository=""
 revision="9a182f3d959d16354e24f34713df602f1bef6556"
 [5.0.x] Fixed #35056 -- Fixed system check crash on reverse m2m relations
 with related_name in ModelAdmin.filter_horizontal/vertical.

 Thanks Thomas Feldmann for the report.

 Regression in 107865780aa44914e21d27fdf4ca269bc61c7f01.
 Backport of 751d732a3815a68bdb5b7aceda0e7d5981362c4a from main
 }}}

-- 
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/0107018cacc89911-78e9cb6f-e486-45cf-891b-b861423c0770-00%40eu-central-1.amazonses.com.

Re: [Django] #35056: admin.E013 on ManyToManyField with related_name crashes.

[Django]

#35056: admin.E013 on ManyToManyField with related_name crashes.
-+-
 Reporter:  Thomas Feldmann  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  5.0
 Severity:  Release blocker  |   Resolution:  fixed
 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 GitHub ):

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


Comment:

 In [changeset:"751d732a3815a68bdb5b7aceda0e7d5981362c4a" 751d732a]:
 {{{
 #!CommitTicketReference repository=""
 revision="751d732a3815a68bdb5b7aceda0e7d5981362c4a"
 Fixed #35056 -- Fixed system check crash on reverse m2m relations with
 related_name in ModelAdmin.filter_horizontal/vertical.

 Thanks Thomas Feldmann for the report.

 Regression in 107865780aa44914e21d27fdf4ca269bc61c7f01.
 }}}

-- 
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/0107018cacc73fb6-cc4eb75a-6ce9-48d1-b989-e2f4b171ac13-00%40eu-central-1.amazonses.com.

Re: [Django] #35064: Window.order_by decimal field is broken on SQLite

[Django]

#35064: Window.order_by decimal field is broken on SQLite
-+-
 Reporter:  Simon Charette   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cacc43521-0cd3de73-d5a2-4d30-8268-f8ec961ff27f-00%40eu-central-1.amazonses.com.

[Django] #35064: Window.order_by decimal field is broken on SQLite

[Django]

#35064: Window.order_by decimal field is broken on SQLite
-+-
   Reporter:  Simon  |  Owner:  nobody
  Charette   |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  3.2
  layer (models, ORM)|
   Severity:  Normal |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Initially reported
 
[https://discord.com/channels/856567261900832808/1180704302847766538/1180704302847766538
 on the Discord] and demonstrated in
 [https://github.com/Quoates/django_rank_order_by this Django project].

 {{{#!python
 class RankTest(models.Model):
 name = models.CharField(max_length=30)
 category = models.CharField(max_length=30)
 rating = models.DecimalField(max_digits=8, decimal_places=5)

 list(
 RankTest.objects.annotate(
 rank=Window(
 expression=Rank(),
 order_by='rating'
 )
 )
 )
 }}}

 The solution implemented in #31723
 (71d10ca8c90ccc1fd0ccd6683716dd3c3116ae6a) wish addressed the improper of
 casting for `Window.expression` caused some problematic one for `order_by`
 and likely `partition_by` as well.

-- 
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/0107018cac9ca853-a8b1913f-62a1-4166-9d79-9599ae40caef-00%40eu-central-1.amazonses.com.

Re: [Django] #32114: Workaround for subtest issue with parallel test runner

[Django]

#32114: Workaround for subtest issue with parallel test runner
-+-
 Reporter:  Jordan Ephron|Owner:  David
 Type:   |  Wobrock
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  Version:  3.1
 Severity:  Normal   |   Resolution:
 Keywords:  Test subtest | Triage Stage:  Accepted
  parallel   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by David Wobrock):

 * owner:  (none) => David Wobrock
 * needs_better_patch:  1 => 0
 * status:  new => assigned


Comment:

 Here's a new minimal [https://github.com/django/django/pull/17650 PR],
 based on previous work.

-- 
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/0107018cac882a7c-de4890ca-91eb-4fa3-89b5-b2751cd52e50-00%40eu-central-1.amazonses.com.

Re: [Django] #35063: Django 5 LOGOUT_REDIRECT_URL does not work correctly

[Django]

#35063: Django 5 LOGOUT_REDIRECT_URL does not work correctly
--+--
 Reporter:  Koljasha  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  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 Tim Graham):

 * status:  new => closed
 * resolution:   => invalid
 * component:  Uncategorized => contrib.auth
 * type:  Uncategorized => Bug


Comment:

 As per the Django 5.0 release notes, support for logging out via GET
 requests in the `django.contrib.auth.views.LogoutView` is removed. You
 must issue a `POST` in order to log out and be redirected.

-- 
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/0107018cac1d2561-9e104667-5cdc-456e-b10f-8110e43cda51-00%40eu-central-1.amazonses.com.

[Django] #35063: Django 5 LOGOUT_REDIRECT_URL does not work correctly

[Django]

#35063: Django 5 LOGOUT_REDIRECT_URL does not work correctly
-+
   Reporter:  Koljasha   |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |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  |
-+
 Procedure, explanation:
 * create default project 'root': `django-admin startproject root`
 * do migrate: `python manage.py migrate`
 * createsuperuser: `python manage.py createsuperuser`
 * add in `root/settings.py` for example: `LOGOUT_REDIRECT_URL =
 'admin:index'`
 * add in `root/urls.py`: `path('accounts/',
 include('django.contrib.auth.urls')),`
 * after authorization, I do: http://127.0.0.1:8000/accounts/logout/
 - in 4.2.8 correct - redirect:
 http://127.0.0.1:8000/admin/login/?next=/admin/
 - in 5.0 not correct - only white screen and in console: "GET
 /accounts/logout/ HTTP/1.1" 405 0

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cac151716-97a5ca06-2585-4530-b54e-ffd034a5e1f0-00%40eu-central-1.amazonses.com.

Re: [Django] #24686: Support for Moving a model between two Django apps

[Django]

#24686: Support for Moving a model between two Django apps
---+
 Reporter:  Alex Rothberg  |Owner:  Bhuvnesh
 Type:  New feature|   Status:  assigned
Component:  Migrations |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by David Wobrock):

 * cc: David Wobrock (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/0107018cac0bb365-ca022937-04f0-4ea2-8ea5-b68d431085df-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:  Akash
 |  Kumar Sen
 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 Mariusz Felisiak):

 * needs_better_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cab701096-279d3019-e415-41bb-9efe-178f2258a218-00%40eu-central-1.amazonses.com.

Re: [Django] #35058: Update GDAL integration

[Django]

#35058: Update GDAL integration
--+
 Reporter:  David Smith   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  GIS   |  Version:  4.2
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Mariusz Felisiak ):

 In [changeset:"21b0b23a67ee1aa1a35f7f64cd8fe997e4de89d7" 21b0b23]:
 {{{
 #!CommitTicketReference repository=""
 revision="21b0b23a67ee1aa1a35f7f64cd8fe997e4de89d7"
 Refs #35058 -- Made OGRGeomType aware of additional WKB geometry types.

 This commit increases OGRGeomType's knowledge of WKB types and allows
 for improved error messages when Django doesn't yet have a corresponding
 class to wrap a given type.
 }}}

-- 
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/0107018cab197555-3397bba7-2954--8fbc-746102706c6b-00%40eu-central-1.amazonses.com.

Re: [Django] #35033: EmailMessage repeats header if provided via the headers kwargs

[Django]

#35033: EmailMessage repeats header if provided via the headers kwargs
+-
 Reporter:  Aalekh Patel|Owner:  Salvo Polizzi
 Type:  Bug |   Status:  assigned
Component:  Core (Mail) |  Version:  dev
 Severity:  Normal  |   Resolution:
 Keywords:  email, headers  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+-
Changes (by Salvo Polizzi):

 * needs_better_patch:  1 => 0
 * needs_tests:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018cab102f47-b9e465db-3c7c-4682-aae4-ae39adb9b0a9-00%40eu-central-1.amazonses.com.

Re: [Django] #35033: EmailMessage repeats header if provided via the headers kwargs

[Django]

#35033: EmailMessage repeats header if provided via the headers kwargs
+-
 Reporter:  Aalekh Patel|Owner:  Salvo Polizzi
 Type:  Bug |   Status:  assigned
Component:  Core (Mail) |  Version:  dev
 Severity:  Normal  |   Resolution:
 Keywords:  email, headers  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+-

Comment (by Salvo Polizzi):

 Replying to [comment:19 Florian Apolloner]:
 > I do not see any tests in the PR, just because no tests fail after
 changes doesn't mean there are no tests required ;)
 I'm sorry, I will provide tests. Thanks for giving me some feedback

-- 
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/0107018caae2773a-f143b8fb-e5ee-4851-9e69-fd41df133def-00%40eu-central-1.amazonses.com.

Re: [Django] #16281: ContentType.get_object_for_this_type using wrong database for creating object

[Django]

#16281: ContentType.get_object_for_this_type using wrong database for creating
object
-+-
 Reporter:  tfrydrychewicz@… |Owner:  bcail
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  dev
  contrib.contenttypes   |
 Severity:  Normal   |   Resolution:
 Keywords:  contenttype, object  | Triage Stage:  Accepted
  get_object_for_this_type,  |
  database, multiple |
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1
 * needs_tests:  0 => 1
 * needs_docs:  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/0107018caa57209a-7d563790-7472-4d3d-b6a9-edea6d02a631-00%40eu-central-1.amazonses.com.

Re: [Django] #35038: Changing violation_error_message on constraints cause a remove/add operation in migration

[Django]

#35038: Changing violation_error_message on constraints cause a remove/add
operation in migration
-+-
 Reporter:  David|Owner:  Salvo
 Type:   |  Polizzi
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  4.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 Salvo Polizzi):

 * owner:  nobody => Salvo Polizzi
 * status:  new => assigned


-- 
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/0107018caa56e413-52fd651d-d393-45f4-b168-c628050ccc13-00%40eu-central-1.amazonses.com.