Re: [Django] #34650: Document django.shortcuts.resolve_url()

[Django]

#34650: Document django.shortcuts.resolve_url()
--+--
 Reporter:  Adam Johnson  |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  Utilities |  Version:  dev
 Severity:  Normal|   Resolution:  duplicate
 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 David Smith):

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


Comment:

 This appears to be a duplicate #30515. #33032 was also opened with the
 same issue and was closed as a duplicate.

-- 
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/01070188b1df8694-ae14878f-7e7a-46be-b93a-bc6a74ec2a48-00%40eu-central-1.amazonses.com.

[Django] #34650: Document django.shortcuts.resolve_url()

[Django]

#34650: Document django.shortcuts.resolve_url()
+
   Reporter:  Adam Johnson  |  Owner:  nobody
   Type:  New feature   | Status:  new
  Component:  Utilities |Version:  dev
   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 |
+
 This function does most of the work for the `redirect()` shortcut. It's
 been around since a78dd109e6c81c49e90e36e9b793bad67c46c23c (2012-09-08)
 and is useful to call on its own when constructing a different kind of
 redirect response, such as 303, 307, or [https://django-
 htmx.readthedocs.io/en/latest/http.html#django_htmx.http.HttpResponseLocation
 an htmx JavaScript redirect].

 Documenting `resolve_url()` would make it part of Django's dependable
 public API.

-- 
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/01070188b1801067-5634d3db-2258-4ed4-9092-876e8fb2496a-00%40eu-central-1.amazonses.com.

Re: [Django] #34649: Modernise selenium --headless support

[Django]

#34649: Modernise selenium --headless support
--+
 Reporter:  David Smith   |Owner:  aokugel
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Testing framework |  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:  1 |UI/UX:  0
--+
Changes (by aokugel):

 * owner:  (none) => aokugel
 * 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/01070188af9a1bc4-34a06b5f-a9f8-4b31-b49b-e2fc7cbd0859-00%40eu-central-1.amazonses.com.

Re: [Django] #34649: Modernise selenium --headless support

[Django]

#34649: Modernise selenium --headless support
--+
 Reporter:  David Smith   |Owner:  (none)
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  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:  1 |UI/UX:  0
--+
Changes (by Bhuvnesh):

 * owner:  Bhuvnesh => (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/01070188af76e449-b2f534d3-13d5-40ac-8989-f85912088503-00%40eu-central-1.amazonses.com.

Re: [Django] #34649: Modernise selenium --headless support

[Django]

#34649: Modernise selenium --headless support
--+
 Reporter:  David Smith   |Owner:  Bhuvnesh
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Testing framework |  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:  1 |UI/UX:  0
--+
Changes (by Bhuvnesh):

 * owner:  nobody => Bhuvnesh
 * 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/01070188af70fde9-1faf34b8-668a-489c-9ff4-4686b33220e7-00%40eu-central-1.amazonses.com.

Re: [Django] #34309: Documentate how to delete a Django app correctly

[Django]

#34309: Documentate how to delete a Django app correctly
-+-
 Reporter:  Marcelo Galigniana   |Owner:  Marcelo
 |  Galigniana
 Type:  New feature  |   Status:  assigned
Component:  Documentation|  Version:  4.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/01070188af02c62d-2753f1a8-43fa-4d0e-bbcf-d8e193247055-00%40eu-central-1.amazonses.com.

Re: [Django] #34417: AlterField migration on ForeignKey field re-creates foreign key constraints unnecessarily

[Django]

#34417: AlterField migration on ForeignKey field re-creates foreign key 
constraints
unnecessarily
-+-
 Reporter:  Ömer Faruk Abacı |Owner:  Deniz
 Type:   |  Altun
  Cleanup/optimization   |   Status:  assigned
Component:  Migrations   |  Version:  4.1
 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
 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/16922 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/01070188af016c34-37ecebb1-372e-4714-bbee-8c413e5f941f-00%40eu-central-1.amazonses.com.

Re: [Django] #34628: RelatedFieldWidgetWrapper link icons are very hard to see

[Django]

#34628: RelatedFieldWidgetWrapper link icons are very hard to see
-+-
 Reporter:  Thibaud Colas|Owner:  nmenezes0
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  4.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  accessibility,   | Triage Stage:  Ready for
  color contrast |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"1699f8b52ac15f687cc39088401c2641022c71cd" 1699f8b]:
 {{{
 #!CommitTicketReference repository=""
 revision="1699f8b52ac15f687cc39088401c2641022c71cd"
 Fixed #34628 -- Improved icons accessibility of related widget wrapper in
 admin.

 This improves accessibility of icons by making them larger and grayscale
 (when not selected).
 }}}

-- 
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/01070188aee9165e-b98e512e-9f07-458c-b421-60bbf92db12a-00%40eu-central-1.amazonses.com.

Re: [Django] #23577: Rename operations should rename indexes, constraints, sequences and triggers named after their former value

[Django]

#23577: Rename operations should rename indexes, constraints, sequences and
triggers named after their former value
-+
 Reporter:  Chris Woytowitz  |Owner:  (none)
 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
-+

Comment (by Steven Mapes):

 So I ended up created a duplicate of this ticket for issue #34647 but
 thanks to clavay's suggestion I managed to also get a work around by
 running {{{makemigrations}}}then editing the {{{CreateModel}}} and
 changing the name and db_table entries for all tables that were created (I
 use custom table names as the app name prefix breaks the DB naming
 convention policy that's in place for the project.

 I then added {{{migrations.RenameModel}}} statements for each of the
 models I needed to rename back, four of them, then finally had to run a
 {{{migrations.RunSQL}}} to perform the actual rename of the underlying
 databases tables.

-- 
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/01070188aede1139-59f08f5a-69f5-41ac-8589-421504103e98-00%40eu-central-1.amazonses.com.

Re: [Django] #34649: Modernise selenium --headless support

[Django]

#34649: Modernise selenium --headless support
--+
 Reporter:  David Smith   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  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:  1 |UI/UX:  0
--+
Changes (by Sarah Boyce):

 * cc: Sarah Boyce (added)
 * type:  Uncategorized => Cleanup/optimization
 * component:  Uncategorized => Testing framework
 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Thank you for the report!

-- 
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/01070188ae513895-1a90f199-e92c-494d-bc9e-2f1a8c28f29a-00%40eu-central-1.amazonses.com.

Re: [Django] #34628: RelatedFieldWidgetWrapper link icons are very hard to see

[Django]

#34628: RelatedFieldWidgetWrapper link icons are very hard to see
-+-
 Reporter:  Thibaud Colas|Owner:  nmenezes0
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  contrib.admin|  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility,   | Triage Stage:  Ready for
  color contrast |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Mariusz Felisiak):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070188ae51195a-d8365ce4-96c8-4620-b89d-6fd2dfea7a75-00%40eu-central-1.amazonses.com.