Re: [Django] #35179: Admindocs does not recognize methods containing positional-only arguments or keyword-only arguments as such

2024-02-10 Thread Django 
#35179: Admindocs does not recognize methods containing positional-only 
arguments
or keyword-only arguments as such
---+
 Reporter:  David Sanders  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admindocs  |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by David Sanders):

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

Comment:

 Hi Salvo,

 Thanks for picking this up. You're in the right areaa but the patch
 provided appears to break the patched functions.

 My advice is to start with creating a test for admindocs first then take a
 look at the function `method_has_no_args()`.  The fix should be the same
 for ticket #35175 đź‘Ť
-- 
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/0107018d96e800fd-9870c828-5b4f-4bf7-b125-beb3b7e95796-00%40eu-central-1.amazonses.com.

Re: [Django] #9388: Made month and year selectable in admin calender widget.

2024-02-10 Thread Django 
#9388: Made month and year selectable in admin calender widget.
-+-
 Reporter:  Fidel Ramos  |Owner:
 |  ahmadkhalili
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  admin calendar year  | Triage Stage:  Accepted
  previous next widget ui|
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Alexander Lazarević):

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

Comment:

 Replying to [comment:20 Thibaud Colas]:
 > Yes, I would say a big problem here is that this builds upon a date
 picker widget which we already know has many accessibility flaws and needs
 a replacement

 Ok, that wasn't apparent to me. Thanks for the clarification.
-- 
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/0107018d9661cc1d-526746be-16da-4978-9849-96f596b958a8-00%40eu-central-1.amazonses.com.

Re: [Django] #9388: Made month and year selectable in admin calender widget.

2024-02-10 Thread Django 
#9388: Made month and year selectable in admin calender widget.
-+-
 Reporter:  Fidel Ramos  |Owner:
 |  ahmadkhalili
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  admin calendar year  | Triage Stage:  Accepted
  previous next widget ui|
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-
Comment (by Thibaud Colas):

 Yes, I would say a big problem here is that this builds upon a date picker
 widget which we already know has many accessibility flaws and needs a
 replacement (see [https://github.com/django/django/pull/15806 Refs #29822
 -- Improved date, time and datetime HTML inputs #15806]). Personally I
 wouldn’t recommend working on that widget, but if others think incremental
 improvements are the path forward that’s a valid call too.

 Aside from that – there is also one code review comment on the PR which
 the author has yet to address.
-- 
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/0107018d9603672e-4e5739ea-e326-4f73-8fff-ba73b6449279-00%40eu-central-1.amazonses.com.

Re: [Django] #35180: PostgreSQL pattern ops indexes are dropped when changing between CharField and TextField

2024-02-10 Thread Django 
#35180: PostgreSQL pattern ops indexes are dropped when changing between 
CharField
and TextField
-+-
 Reporter:  Robin Ray|Owner:
 |  timbaginski
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  index postgres   | Triage Stage:
  migration  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timbaginski):

 * owner:  nobody => timbaginski
 * 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/0107018d95ef2e93-3c71a58e-c99c-412f-8003-70f2a839399f-00%40eu-central-1.amazonses.com.

Re: [Django] #35179: Admindocs does not recognize methods containing positional-only arguments or keyword-only arguments as such

2024-02-10 Thread Django 
#35179: Admindocs does not recognize methods containing positional-only 
arguments
or keyword-only arguments as such
---+
 Reporter:  David Sanders  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admindocs  |  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 Salvo Polizzi):

 * 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/0107018d94f3fe2b-67a81a47-0e51-457a-812e-d34383c366a0-00%40eu-central-1.amazonses.com.

[Django] #35181: behaviour of makemessage dont follow documentation

2024-02-10 Thread Django 
#35181: behaviour of makemessage dont follow documentation
-+-
   Reporter: |  Owner:  nobody
  pierreloicq|
   Type: | Status:  new
  Cleanup/optimization   |
  Component: |Version:  4.2
  Documentation  |   Keywords:  translation,
   Severity:  Normal |  makemessage
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 Regarding how the makemessage command choose its locale dirs, the truth
 that is described here https://stackoverflow.com/a/76261223/11378446
 doesn't stick with the documentation. LOCALE_PATHS is not taken into
 account.

 So I suggest to adapt the documentation.

 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/0107018d94da05ae-b1140236-9a4a-4963-a176-a4abf73a441b-00%40eu-central-1.amazonses.com.

Re: [Django] #35179: Admindocs does not recognize methods containing positional-only arguments or keyword-only arguments as such

2024-02-10 Thread Django 
#35179: Admindocs does not recognize methods containing positional-only 
arguments
or keyword-only arguments as such
---+
 Reporter:  David Sanders  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admindocs  |  Version:  dev
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Salvo Polizzi):

 * has_patch:  0 => 1
 * needs_tests:  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/0107018d94328de9-edb8a3de-134b-4899-9afd-658e9ce7d4d5-00%40eu-central-1.amazonses.com.

Re: [Django] #35180: PostgreSQL pattern ops indexes are dropped when changing between CharField and TextField

2024-02-10 Thread Django 
#35180: PostgreSQL pattern ops indexes are dropped when changing between 
CharField
and TextField
-+-
 Reporter:  Robin Ray|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  index postgres   | Triage Stage:
  migration  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by Robin Ray:

Old description:

> When converting an indexed CharField to a TextField (and vice versa) on
> PostgreSQL, Django drops the existing pattern ops `_like` index for the
> column but does not recreate it with the new pattern ops. When reversing
> the migration, Django does not recreate the initial `_like` index.
>
> I have been able to reproduce this behavior in Django 3.2 and 5.0.
>
> **Reproduction**
>
> 1. Given a model with a CharField that has `db_index=True` on a
> PostgreSQL database
> 2. Inspect the database indexes or migration SQL and see that the indexed
> CharField has two indexes, one of which ends in `_like` and uses
> `varchar_pattern_ops`
> 3. Change the CharField to a TextField and generate a migration
> 4. Run the migration or inspect the SQL with the `sqlmigrate` manage
> command
> 5. Inspect the database indexes or migration SQL and see that the indexed
> TextField does not have a `_like` index
> 6. Reverse the migration
> 7. Inspect the database indexes or migration SQL and see that the indexed
> CharField no longer has a `_like` index
>
> Here is an example project that demonstratest the issue:
> https://github.com/robin-ray/alter_text_index_repro

New description:

 When converting an indexed CharField to a TextField (and vice versa) on
 PostgreSQL, Django drops the existing pattern ops `_like` index for the
 column but does not recreate it with the new pattern ops. When reversing
 the migration, Django does not recreate the initial `_like` index.

 I have been able to reproduce this behavior in Django 3.2 and 5.0.

 **Reproduction**

 1. Given a model with a CharField that has `db_index=True` on a PostgreSQL
 database
 2. Inspect the database indexes or migration SQL and see that the indexed
 CharField has two indexes, one of which ends in `_like` and uses
 `varchar_pattern_ops`
 3. Change the CharField to a TextField and generate a migration
 4. Run the migration or inspect the SQL with the `sqlmigrate` manage
 command
 5. Inspect the database indexes or migration SQL and see that the indexed
 TextField does not have a `_like` index
 6. Reverse the migration
 7. Inspect the database indexes or migration SQL and see that the indexed
 CharField no longer has a `_like` index

 Here is an example project that demonstrates the issue: https://github.com
 /robin-ray/alter_text_index_repro

--
-- 
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/0107018d93cf9bea-a8898e30-3ef1-4131-b098-9486b5f9e9c9-00%40eu-central-1.amazonses.com.

[Django] #35180: PostgreSQL pattern ops indexes are dropped when changing between CharField and TextField

2024-02-10 Thread Django 
#35180: PostgreSQL pattern ops indexes are dropped when changing between 
CharField
and TextField
-+-
   Reporter:  Robin Ray  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Database   |Version:  5.0
  layer (models, ORM)|   Keywords:  index postgres
   Severity:  Normal |  migration
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 When converting an indexed CharField to a TextField (and vice versa) on
 PostgreSQL, Django drops the existing pattern ops `_like` index for the
 column but does not recreate it with the new pattern ops. When reversing
 the migration, Django does not recreate the initial `_like` index.

 I have been able to reproduce this behavior in Django 3.2 and 5.0.

 **Reproduction**

 1. Given a model with a CharField that has `db_index=True` on a PostgreSQL
 database
 2. Inspect the database indexes or migration SQL and see that the indexed
 CharField has two indexes, one of which ends in `_like` and uses
 `varchar_pattern_ops`
 3. Change the CharField to a TextField and generate a migration
 4. Run the migration or inspect the SQL with the `sqlmigrate` manage
 command
 5. Inspect the database indexes or migration SQL and see that the indexed
 TextField does not have a `_like` index
 6. Reverse the migration
 7. Inspect the database indexes or migration SQL and see that the indexed
 CharField no longer has a `_like` index

 Here is an example project that demonstratest the issue:
 https://github.com/robin-ray/alter_text_index_repro
-- 
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/0107018d93c9db6f-16c3b072-21b6-48ff-8bcd-0ca0e857fd2a-00%40eu-central-1.amazonses.com.

Re: [Django] #34118: Python 3.12 compatibility

2024-02-10 Thread Django 
#34118: Python 3.12 compatibility
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 |  Felisiak
 Type:  New feature  |   Status:  closed
Component:  Core (Other) |  Version:  dev
 Severity:  Normal   |   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:"86d8034972db5014769cdd4832125067f31b3e8b" 86d8034]:
 {{{#!CommitTicketReference repository=""
 revision="86d8034972db5014769cdd4832125067f31b3e8b"
 [4.2.x] Refs #34900, Refs #34118 -- Updated assertion in
 test_skip_class_unless_db_feature() test on Python 3.12.2+.

 Python 3.12.2 bring back the skipped tests in the number of running
 tests. Refs
 
https://github.com/python/cpython/commit/0a737639dcd3b7181250f5d56694b192eaddeef0

 Backport of bc8471f0aac8f0c215b9471b594d159783bac19b 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/0107018d93c7d7dc-e2e37c95-d098-45d0-a1e9-27aae27aa319-00%40eu-central-1.amazonses.com.

Re: [Django] #34900: Python 3.13 compatibility.

2024-02-10 Thread Django 
#34900: Python 3.13 compatibility.
-+-
 Reporter:  Mariusz Felisiak |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Other) |  Version:  4.2
 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
-+-
Comment (by Mariusz Felisiak ):

 In [changeset:"86d8034972db5014769cdd4832125067f31b3e8b" 86d8034]:
 {{{#!CommitTicketReference repository=""
 revision="86d8034972db5014769cdd4832125067f31b3e8b"
 [4.2.x] Refs #34900, Refs #34118 -- Updated assertion in
 test_skip_class_unless_db_feature() test on Python 3.12.2+.

 Python 3.12.2 bring back the skipped tests in the number of running
 tests. Refs
 
https://github.com/python/cpython/commit/0a737639dcd3b7181250f5d56694b192eaddeef0

 Backport of bc8471f0aac8f0c215b9471b594d159783bac19b 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/0107018d93c7d7b5-5f6e7095-9ca2-454b-8f0f-b2b7af11d0ae-00%40eu-central-1.amazonses.com.

Re: [Django] #34900: Python 3.13 compatibility.

2024-02-10 Thread Django 
#34900: Python 3.13 compatibility.
-+-
 Reporter:  Mariusz Felisiak |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Other) |  Version:  4.2
 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
-+-
Comment (by Mariusz Felisiak ):

 In [changeset:"1ba5afa0f21f10843bb530b443687e07a511516a" 1ba5afa]:
 {{{#!CommitTicketReference repository=""
 revision="1ba5afa0f21f10843bb530b443687e07a511516a"
 [5.0.x] Refs #34900, Refs #34118 -- Updated assertion in
 test_skip_class_unless_db_feature() test on Python 3.12.2+.

 Python 3.12.2 bring back the skipped tests in the number of running
 tests. Refs
 
https://github.com/python/cpython/commit/0a737639dcd3b7181250f5d56694b192eaddeef0

 Backport of bc8471f0aac8f0c215b9471b594d159783bac19b 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/0107018d93c6f289-8d09bf16-4914-4c7e-9148-5ed414324e0c-00%40eu-central-1.amazonses.com.

Re: [Django] #34118: Python 3.12 compatibility

2024-02-10 Thread Django 
#34118: Python 3.12 compatibility
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 |  Felisiak
 Type:  New feature  |   Status:  closed
Component:  Core (Other) |  Version:  dev
 Severity:  Normal   |   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:"1ba5afa0f21f10843bb530b443687e07a511516a" 1ba5afa]:
 {{{#!CommitTicketReference repository=""
 revision="1ba5afa0f21f10843bb530b443687e07a511516a"
 [5.0.x] Refs #34900, Refs #34118 -- Updated assertion in
 test_skip_class_unless_db_feature() test on Python 3.12.2+.

 Python 3.12.2 bring back the skipped tests in the number of running
 tests. Refs
 
https://github.com/python/cpython/commit/0a737639dcd3b7181250f5d56694b192eaddeef0

 Backport of bc8471f0aac8f0c215b9471b594d159783bac19b 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/0107018d93c6f2c2-6ac44277-e27a-4e35-af50-8c5135b575e3-00%40eu-central-1.amazonses.com.

Re: [Django] #34900: Python 3.13 compatibility.

2024-02-10 Thread Django 
#34900: Python 3.13 compatibility.
-+-
 Reporter:  Mariusz Felisiak |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Other) |  Version:  4.2
 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
-+-
Comment (by Mariusz Felisiak ):

 In [changeset:"bc8471f0aac8f0c215b9471b594d159783bac19b" bc8471f0]:
 {{{#!CommitTicketReference repository=""
 revision="bc8471f0aac8f0c215b9471b594d159783bac19b"
 Refs #34900, Refs #34118 -- Updated assertion in
 test_skip_class_unless_db_feature() test on Python 3.12.2+.

 Python 3.12.2 bring back the skipped tests in the number of running
 tests. Refs
 
https://github.com/python/cpython/commit/0a737639dcd3b7181250f5d56694b192eaddeef0
 }}}
-- 
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/0107018d93c66b33-7028a209-65c6-429e-8705-067b47d3203d-00%40eu-central-1.amazonses.com.

Re: [Django] #34118: Python 3.12 compatibility

2024-02-10 Thread Django 
#34118: Python 3.12 compatibility
-+-
 Reporter:  Mariusz Felisiak |Owner:  Mariusz
 |  Felisiak
 Type:  New feature  |   Status:  closed
Component:  Core (Other) |  Version:  dev
 Severity:  Normal   |   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:"bc8471f0aac8f0c215b9471b594d159783bac19b" bc8471f0]:
 {{{#!CommitTicketReference repository=""
 revision="bc8471f0aac8f0c215b9471b594d159783bac19b"
 Refs #34900, Refs #34118 -- Updated assertion in
 test_skip_class_unless_db_feature() test on Python 3.12.2+.

 Python 3.12.2 bring back the skipped tests in the number of running
 tests. Refs
 
https://github.com/python/cpython/commit/0a737639dcd3b7181250f5d56694b192eaddeef0
 }}}
-- 
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/0107018d93c66b5a-ee6939db-2fb3-40a4-86cd-e634a4a21105-00%40eu-central-1.amazonses.com.

Re: [Django] #34976: startproject and startapp should provide feedback

2024-02-10 Thread Django 
#34976: startproject and startapp should provide feedback
-+-
 Reporter:  Thibaud Colas|Owner:  Salvo
 Type:   |  Polizzi
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Management |  Version:  dev
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:  tutorial, command,   | Triage Stage:  Accepted
  startproject, startapp |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Comment (by Thibaud Colas):

 Follow-up PR by @TobeTek with directory structure output:
 [https://github.com/django/django/pull/17838 Refs #34976 -- Print
 directory structure after startapp and startproject #17838]
-- 
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/0107018d93ba50a1-c00381cc-6d91-4704-8c0b-ed7c251dc281-00%40eu-central-1.amazonses.com.

Re: [Django] #33620: Accessibility in pipeline

2024-02-10 Thread Django 
#33620: Accessibility in pipeline
-+-
 Reporter:  Sarah Abderemane |Owner:  Tushar
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  accessibility, ux,   | Triage Stage:  Accepted
  ui, admin  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Comment (by Thibaud Colas):

 We have an update! After contacting the DSF board back in November 2023,
 we now have our answer that moving [https://github.com/mozilla-services
 /axe-selenium-python axe-selenium-python] to the Django org in GitHub
 wouldn’t be appropriate. As it’s not a Django-related package, we don’t
 want to risk its maintenance falling to the Django ops team.

 So -- the accessibility team will proceed another way. Currently we’re
 planning to still try to take over maintenance of the package, but in a
 separate GitHub organization so it’s clearer whose role it is to maintain
 it.

 @Tushar would you be up for helping with maintenance 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/0107018d92f348f6-b4f0355e-6df5-4a44-b22f-45e1d4c3b3ee-00%40eu-central-1.amazonses.com.