Re: [Django] #33671: Migrations crashes when adding/altering collations on indexed columns on Oracle.

2024-04-08 Thread Django 
#33671: Migrations crashes when adding/altering collations on indexed columns on
Oracle.
--+
 Reporter:  Mariusz Felisiak  |Owner:  Mahesh Gupta
 Type:  Bug   |   Status:  assigned
Component:  Migrations|  Version:  4.0
 Severity:  Normal|   Resolution:
 Keywords:  oracle collation  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Comment (by Mahesh Gupta):

 As per https://docs.oracle.com/en/error-help/db/ora-43923/ Collation are
 divided into groups and
 Group 1: BINARY, USING_NLS_COMP, USING_NLS_SORT, USING_NLS_SORT_CS,
 USING_NLS_SORT_VAR1, and USING_NLS_SORT_VAR1_CS
 Group 2: BINARY_CI, USING_NLS_SORT_CI, and USING_NLS_SORT_VAR1_CI
 Group 3: BINARY_AI, USING_NLS_SORT_AI, and USING_NLS_SORT_VAR1_AI
 and action suggested by Oracle is
 When modifying the column collation, specify a new collation that is in
 the same group as the current column collation. If there is no current
 collation, because you changed the column data type at the same time and
 the old data type is not a character data type, then select a collation
 from Group 1 as the new collation.

 Reading this, should we really fix this or this is more of a user error
 and they should act accordingly?
-- 
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/0107018ebf5d627e-bb4ebf2c-623d-4279-afce-72e8044f51f8-00%40eu-central-1.amazonses.com.

Re: [Django] #12264: calendar.js depends on jsi18n but date widgets using it do not specify as required media

2024-04-08 Thread Django 
#12264: calendar.js depends on jsi18n but date widgets using it do not specify 
as
required media
--+-
 Reporter:  tblanchard@…  |Owner:  Adam Zapletal
 Type:  New feature   |   Status:  assigned
Component:  Forms |  Version:  1.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 Adam Zapletal):

 * owner:  nobody => Adam Zapletal
 * status:  new => assigned

Comment:

 Thanks for the activity here! I'm happy to open a pull request when a
 consensus is reached.
-- 
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/0107018ebf5a4ee7-ff4b270a-e9a7-4750-aa9f-1033cf92ca73-00%40eu-central-1.amazonses.com.

Re: [Django] #12264: calendar.js depends on jsi18n but date widgets using it do not specify as required media

2024-04-08 Thread Django 
#12264: calendar.js depends on jsi18n but date widgets using it do not specify 
as
required media
--+
 Reporter:  tblanchard@…  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Forms |  Version:  1.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
--+
Comment (by Tom Carrick):

 I agree completely. In my mind, the admin widgets aren't really that
 suitable for use in user code. If people want to use them, fine, but I
 think it should be at their own risk and we shouldn't add any extra
 maintenance burden in supporting this.

 With this piece of documentation, I feel like is suggesting that any
 visible change we make to a widget could be backwards incompatible and I
 don't think we want that, at least I personally would like the freedom to
 change the admin widgets between releases to make improvements without
 worrying too much that they might affect someone's site otherwise.

 I think we should discourage this by at a minimum removing this paragraph
 and closing this ticket.

 Just my opinion, anyway :)
-- 
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/0107018ebe8f69d3-2f71187b-696e-4d07-b21a-c2a4966553d3-00%40eu-central-1.amazonses.com.

Re: [Django] #27106: Document which template filters can be used in Python code (and how)

2024-04-08 Thread Django 
#27106: Document which template filters can be used in Python code (and how)
-+-
 Reporter:  Baptiste Mispelon|Owner:  Ryan
 Type:   |  Cheley
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  1.10
 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):

 * cc: Baptiste Mispelon (added)

Comment:

 Baptiste, would you have some time to answer the latest question in
 comment:9?
-- 
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/0107018ebe8f113f-cb09959b-376e-48e7-845a-7ee24b3a1287-00%40eu-central-1.amazonses.com.

Re: [Django] #35137: Collapsible error container elements do not indicate that they are interactive

2024-04-08 Thread Django 
#35137: Collapsible error container elements do not indicate that they are
interactive
-+-
 Reporter:  Denis Anuschewski|Owner:  Abhijeet
 Type:   |  Singh
  Cleanup/optimization   |   Status:  assigned
Component:  Error reporting  |  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:  1
-+-
Comment (by Sarah Boyce):

 Note that #35189 also deals with collapsible elements and accessibility
 concerns might be similar both (and might make sense to be reviewed
 together).
-- 
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/0107018ebe87150d-3e7ce4f1-473f-4eeb-80c5-695de3a5d6dd-00%40eu-central-1.amazonses.com.

Re: [Django] #35350: Crash on write of new instance when using GeneratedField

2024-04-08 Thread Django 
#35350: Crash on write of new instance when using GeneratedField
-+-
 Reporter:  Matt Hegarty |Owner:  Sarah
 |  Boyce
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  GeneratedField   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sarah Boyce):

 * has_patch:  0 => 1
 * owner:  nobody => Sarah Boyce
 * 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/0107018ebe7f2c95-ec9ecf27-50c3-424d-b965-d4acaa1dfb9b-00%40eu-central-1.amazonses.com.

Re: [Django] #12264: calendar.js depends on jsi18n but date widgets using it do not specify as required media

2024-04-08 Thread Django 
#12264: calendar.js depends on jsi18n but date widgets using it do not specify 
as
required media
--+
 Reporter:  tblanchard@…  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Forms |  Version:  1.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 Natalia Bidart):

 * cc: Claude Paroz, Tom Carrick (added)

Comment:

 Tom, Claude, would you have further insights for the comment:5 above?
-- 
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/0107018ebe73357c-cab0aa8a-c82e-485d-81d1-bb8166fe3d1c-00%40eu-central-1.amazonses.com.

Re: [Django] #35361: SafeMIMEText.set_payload() crash on Python 3.11.9

2024-04-08 Thread Django 
#35361: SafeMIMEText.set_payload() crash on Python 3.11.9
-+-
 Reporter:  Sarah Boyce  |Owner:  Natalia
 |  Bidart
 Type:  Bug  |   Status:  assigned
Component:  Core (Mail)  |  Version:  4.2
 Severity:  Release blocker  |   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 Natalia Bidart):

 * has_patch:  0 => 1
 * owner:  nobody => Natalia Bidart
 * status:  new => assigned

Comment:

 PR for main adding a test (to be backported along with the fix from
 b231bcd19e57267ce1fc21d42d46f0b65fdcfcf8):
 https://github.com/django/django/pull/18057/
-- 
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/0107018ebe6134e8-ed7b1837-0bcd-4b1c-8e5d-3074ac6c3f24-00%40eu-central-1.amazonses.com.

Re: [Django] #35361: SafeMIMEText.set_payload() crash on Python 3.11.9

2024-04-08 Thread Django 
#35361: SafeMIMEText.set_payload() crash on Python 3.11.9
-+
 Reporter:  Sarah Boyce  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Mail)  |  Version:  4.2
 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
-+
Changes (by Natalia Bidart):

 * stage:  Unreviewed => Accepted

Comment:

 Related forum discussion: https://forum.djangoproject.com/t/send-mail-
 throws-unicodeencodeerror-under-python-3-11-9/29871/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/0107018ebdc58686-bc8134f6-48f6-4355-83da-4da74ddcf224-00%40eu-central-1.amazonses.com.

[Django] #35361: SafeMIMEText.set_payload() crash on Python 3.11.9

2024-04-08 Thread Django 
#35361: SafeMIMEText.set_payload() crash on Python 3.11.9
---+
   Reporter:  Sarah Boyce  |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  Core (Mail)  |Version:  4.2
   Severity:  Release blocker  |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 A recent bug fix to Python [https://github.com/python/cpython/issues/76511
 gh-76511] has been back ported to Python 3.11 and 3.12.
 See the release notes of
 [https://docs.python.org/release/3.11.9/whatsnew/changelog.html#python-3-11-9
 Python 3.11.9] and the soon to be released
 [https://docs.python.org/3/whatsnew/changelog.html Python 3.12.3].

 As part of the work to prepare Django for
 [https://code.djangoproject.com/ticket/34900 Python 3.13], a fix for this
 has already been merged to main in
 b231bcd19e57267ce1fc21d42d46f0b65fdcfcf8.

 Believe this needs to be back ported to Django 4.2 and Django 5.0 to
 support the latest (or soon to be latest) Python 3.11 and Python 3.12
 versions.

 Confirmed when testing Django 4.2 against Python 3.11.9, we know have the
 following test failure:

 {{{
 ==
 ERROR [0.034s]: test_dont_base64_encode
 (tests.mail.tests.MailTests.test_dont_base64_encode)
 --
 Traceback (most recent call last):
   File "/tests/django/tests/mail/tests.py", line 902, in
 test_dont_base64_encode
 s = msg.message().as_string()
 ^
   File "/tests/django/django/core/mail/message.py", line 133, in as_string
 g.flatten(self, unixfrom=unixfrom, linesep=linesep)
   File "/usr/local/lib/python3.11/email/generator.py", line 115, in
 flatten
 self._write(msg)
   File "/usr/local/lib/python3.11/email/generator.py", line 180, in _write
 self._dispatch(msg)
   File "/usr/local/lib/python3.11/email/generator.py", line 217, in
 _dispatch
 meth(msg)
   File "/usr/local/lib/python3.11/email/generator.py", line 246, in
 _handle_text
 msg.set_payload(msg._payload, charset)
   File "/tests/django/django/core/mail/message.py", line 168, in
 set_payload
 has_long_lines = any(
  
   File "/tests/django/django/core/mail/message.py", line 169, in 
 len(line.encode()) > RFC5322_EMAIL_LINE_LENGTH_LIMIT
 ^
 UnicodeEncodeError: 'utf-8' codec can't encode characters in position
 28-33: surrogates not allowed

 }}}
-- 
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/0107018ebdbeb580-9e1f95cf-2b4e-4f74-a195-967823e5c1df-00%40eu-central-1.amazonses.com.

Re: [Django] #35356: Issue with OneToOneField and recursive relationships in select_related() and only().

2024-04-08 Thread Django 
#35356: Issue with OneToOneField and recursive relationships in select_related()
and only().
-+-
 Reporter:  Joshua van Besouw|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (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
-+-
Comment (by Joshua van Besouw):

 Thanks for the quick patch on this!

 I can confirm, form my end, that this patch fixes the issue I was
 encountering. The `FieldError` was not raised and the following SQL was
 used in the resulting query:

 {{{
 SELECT
 "test_project_example"."id",
 "test_project_example"."name",
 "test_project_example"."source_id",
 T2."id",
 T2."name",
 T3."id",
 T3."name"
 FROM
 "test_project_example"
 LEFT OUTER JOIN "test_project_example" T2 ON (
 "test_project_example"."source_id" = T2."id"
 )
 LEFT OUTER JOIN "test_project_example" T3 ON (
 "test_project_example"."id" = T3."source_id"
 )
 ORDER BY
 "test_project_example"."id" ASC
 }}}
-- 
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/0107018ebd6ec457-11c3a3d0-0a88-4757-957d-22147fcffc12-00%40eu-central-1.amazonses.com.

Re: [Django] #18119: add DomainNameValidator to validate Internet Domain Names

2024-04-08 Thread Django 
#18119: add DomainNameValidator to validate Internet Domain Names
--+
 Reporter:  michele   |Owner:  Nina Menezes
 Type:  New feature   |   Status:  assigned
Component:  Core (Other)  |  Version:  dev
 Severity:  Normal|   Resolution:
 Keywords:  validators| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Sarah Boyce):

 * needs_better_patch:  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/0107018ebcf81bf5-c5e8d82b-9fc9-46c1-bc49-0c8e293e7d55-00%40eu-central-1.amazonses.com.

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

2024-04-08 Thread 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:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by Sarah Boyce):

 * needs_better_patch:  0 => 1

Comment:

 Marking as patch needs improvement as I failed to follow the instructions
 in the docs successfully, so I don't think they're quite clear enough.
 I plan to do a series of tests once I understand what I should be doing 
 exciting feature!
-- 
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/0107018ebce2ae2f-5155d5ab-dfea-40ef-925b-c276082fe6dd-00%40eu-central-1.amazonses.com.

Re: [Django] #7732: Oracle Backend with SessionPool

2024-04-08 Thread Django 
#7732: Oracle Backend with SessionPool
-+-
 Reporter:  halturin |Owner:  Suraj
 |  Shaw
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  yandex-sprint| Triage Stage:  Accepted
  oracle session pool|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Suraj Shaw):

 * 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/0107018ebcd7e2fc-e495b06c-5530-4dbf-ab84-00bfd18ba058-00%40eu-central-1.amazonses.com.