Re: [Django] #34634: Creating objects with nested MTI crashes.

[Django]

#34634: Creating objects with nested MTI crashes.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Akash
 |  Kumar Sen
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * 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/01070188d7814ae6-24d0d05c-f917-4a46-bc3d-ad2483728d53-00%40eu-central-1.amazonses.com.

Re: [Django] #34658: New assertion `assertNotInHTML`, like `assertContains` has `assertNotContains`

[Django]

#34658: New assertion `assertNotInHTML`, like `assertContains` has
`assertNotContains`
-+-
 Reporter:  Thibaud Colas|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Testing framework|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:  testcases, unit  | Triage Stage:  Accepted
  tests, HTML, assertions, testing   |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * status:  closed => new
 * resolution:  wontfix =>
 * stage:  Unreviewed => Accepted


Comment:

 Accepting based on the [https://forum.djangoproject.com/t/feature-request-
 new-assertion-assertnotinhtml-like-assertcontains-has-
 assertnotcontains/21711 discussion].

 Thibaud, would you like to prepare a patch?

-- 
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/01070188d758afb8-3b23c691-91c1-4dab-8405-2c86d2d2d869-00%40eu-central-1.amazonses.com.

Re: [Django] #33817: Use python-oracledb instead of cx-oracle

[Django]

#33817: Use python-oracledb instead of cx-oracle
-+-
 Reporter:  Alexander Shishenko  |Owner:  Jingbei
 |  Li
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Suraj Shaw):

 After following the logs that has been uploaded , it looks like it is
 crashing inside the code that is displaying all of the variables in the
 stack.  In the debugging code if it can be disabled it may help us to find
 out what the real issue is.

-- 
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/01070188d7581e0a-b3a87ef0-2335-4565-8d6e-28b171853152-00%40eu-central-1.amazonses.com.

Re: [Django] #33817: Use python-oracledb instead of cx-oracle

[Django]

#33817: Use python-oracledb instead of cx-oracle
-+-
 Reporter:  Alexander Shishenko  |Owner:  Jingbei
 |  Li
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 I can take a look but not in June, maybe in July or August. It's not high
 on my priority list. I've already spent too much time in June keeping the
 Oracle backend as functional as the others. As far as I'm aware, it's an
 issue in `python-oracledb` or one of the libraries it uses. Of course, we
 will help you (Oracle) with debugging, even considering the fact that
 you've never helped us maintain the Oracle backend by providing
 infrastructure, knowledge, or money. You have to wait patiently like
 everyone else. It's an open-source.

-- 
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/01070188d6f9b748-336e7e97-54e8-4d1f-82a8-fbf63b7d4715-00%40eu-central-1.amazonses.com.

Re: [Django] #34666: Mysql issue using afirst "The client was disconnected by the server because of inactivity"

[Django]

#34666: Mysql issue using afirst "The client was disconnected by the server 
because
of inactivity"
-+-
 Reporter:  Bernardo Tavares |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  async, afirst,   | Triage Stage:
  mysql, inactivity  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


Comment:

 > In my understanding, Django always opens a connection, executes a query
 and then closes a connection.

 Yes, if you're talking about request-response cycle and connections are
 not persistent.

 > Is it not closing the connection when using ''"afirst()"''? This feels
 seems like a bug to me, or is something in the documentation I'm not
 getting.

 As far as I'm aware, this has nothing to do with `afirst()`.

 > Any help? Thank you in advance!

 I don't think you've explained the issue in enough detail to confirm a bug
 in Django and Trac is not a support channel. Please reopen the ticket if
 you can debug your issue and provide details about why and where Django is
 at fault. A small project that reproduces the issue will also help. If
 you're having trouble debugging, see
 TicketClosingReasons/UseSupportChannels for ways to get help.

-- 
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/01070188d6db3ef0-8a434b23-95c1-4da2-9860-4686c61aef7c-00%40eu-central-1.amazonses.com.

Re: [Django] #14611: django.test.Client is missing post *and* get possibility

[Django]

#14611: django.test.Client is missing post *and* get possibility
---+
 Reporter:  Jari Pennanen  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Testing framework  |  Version:  1.2
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Mariusz Felisiak):

 Replying to [comment:6 Dan Strokirk]:
 > Would it be possible to reopen and reevaluate this ticket? It’s 11 years
 later, and I feel this would be a great, simple addition to Django’s
 testing toolset.

 For now, I don't see a consensus in the [https://forum.djangoproject.com/t
 /suggestion-adding-params-to-testclient-http-methods/21246 discussion] and
 we need it to reopen the ticket. I'd wait a little longer and get more
 opinions.

-- 
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/01070188d6d347a2-38da57fb-08b3-46ed-934b-a6d62ed591fd-00%40eu-central-1.amazonses.com.

Re: [Django] #34345: Add system check for filter_horizontal/filter_vertical on ManyToManyFields with intermediary models.

[Django]

#34345: Add system check for filter_horizontal/filter_vertical on 
ManyToManyFields
with intermediary models.
-+-
 Reporter:  David Pratten|Owner:
 Type:   |  Hrushikesh Vaidya
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  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
-+-

Comment (by Hrushikesh Vaidya):

 [https://github.com/django/django/pull/16983 PR] ready for review

-- 
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/01070188d69d673c-fbb7cf43-dc53-45f3-ba49-e5ec9a09957a-00%40eu-central-1.amazonses.com.

Re: [Django] #14611: django.test.Client is missing post *and* get possibility

[Django]

#14611: django.test.Client is missing post *and* get possibility
---+
 Reporter:  Jari Pennanen  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Testing framework  |  Version:  1.2
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  1
  Needs tests:  1  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by Dan Strokirk):

 Would it be possible to reopen and reevaluate this ticket? It’s 11 years
 later, and I feel this would be a great, simple addition to Django’s
 testing toolset.

-- 
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/01070188d5aaff20-c4b7b938-c0ba-4c9a-b9db-89851bcdf39c-00%40eu-central-1.amazonses.com.

Re: [Django] #27079: Refactor LiveServerPort tests to not make extra calls to setUpClass() and tearDownClass()

[Django]

#27079: Refactor LiveServerPort tests to not make extra calls to setUpClass() 
and
tearDownClass()
-+-
 Reporter:  Chris Jerdonek   |Owner:  Jacob
 Type:   |  Walls
  Cleanup/optimization   |   Status:  closed
Component:  Testing framework|  Version:  1.10
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by GitHub ):

 In [changeset:"d6e9ec40145b9edc65e8d0c65bd3f4ef8a7a27bb" d6e9ec4]:
 {{{
 #!CommitTicketReference repository=""
 revision="d6e9ec40145b9edc65e8d0c65bd3f4ef8a7a27bb"
 Refs #27079 -- Used addClassCleanup() in SeleniumTestCase.

 Regression in def09bf4126d4886413adf732eca8e32576b.
 }}}

-- 
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/01070188d4deb0f3-54188e16-ba5d-4ba8-8eeb-c629569fe467-00%40eu-central-1.amazonses.com.

Re: [Django] #34634: Creating objects with nested MTI crashes.

[Django]

#34634: Creating objects with nested MTI crashes.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Akash
 |  Kumar Sen
 Type:  Bug  |   Status:  assigned
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
-+-
Changes (by Akash Kumar Sen):

 * 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/01070188d46a0308-3132fb67-fbea-4e1c-8465-4a82116bd177-00%40eu-central-1.amazonses.com.

Re: [Django] #34210: Show the duration of individual tests

[Django]

#34210: Show the duration of individual tests
-+-
 Reporter:  Paolo Melchiorre |Owner:  David
 |  Smith
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  test, timing,| Triage Stage:  Accepted
  durations  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 Replying to [comment:17 Sarah Boyce]:
 > I think this also will close this ticket:
 https://code.djangoproject.com/ticket/31827

 Probably yes, let's wait for the final release first.

-- 
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/01070188d43a4d07-66d087f9-c008-4a11-bbac-b134fcf53fe8-00%40eu-central-1.amazonses.com.

Re: [Django] #34210: Show the duration of individual tests

[Django]

#34210: Show the duration of individual tests
-+-
 Reporter:  Paolo Melchiorre |Owner:  David
 |  Smith
 Type:  New feature  |   Status:  assigned
Component:  Testing framework|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  test, timing,| Triage Stage:  Accepted
  durations  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Sarah Boyce):

 I think this also will close this ticket:
 https://code.djangoproject.com/ticket/31827

-- 
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/01070188d4231f4a-b6516460-7046-4e04-8850-3eb9bd54ef45-00%40eu-central-1.amazonses.com.

Re: [Django] #34666: Mysql issue using afirst "The client was disconnected by the server because of inactivity"

[Django]

#34666: Mysql issue using afirst "The client was disconnected by the server 
because
of inactivity"
-+-
 Reporter:  Bernardo Tavares |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  async, afirst,   | Triage Stage:
  mysql, inactivity  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Natalia Bidart):

 I wonder if this is related to #33497...

 Bernardo, do you think you could provide a minimal (but complete) example
 to reproduce this issue? Thanks!

-- 
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/01070188d4109b21-d7c74e35-f414-475d-aba1-3ab5eb704b11-00%40eu-central-1.amazonses.com.

[Django] #34666: Mysql issue using afirst "The client was disconnected by the server because of inactivity"

[Django]

#34666: Mysql issue using afirst "The client was disconnected by the server 
because
of inactivity"
-+-
   Reporter:  Bernardo   |  Owner:  nobody
  Tavares|
   Type:  Bug| Status:  new
  Component:  Database   |Version:  4.2
  layer (models, ORM)|   Keywords:  async, afirst,
   Severity:  Normal |  mysql, inactivity
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 I'm using Django 4.2 connected to a MySQL 8 database.
 I'm running asyncio for a function I really need to run asynchronously:

 {{{
 from django.db import connection
 import asyncio

 example_object = asyncio.run(example(request))
 connection.close()
 }}}


 {{{
 async def example(request):
 object = await ModelExample.objects.filter(example=example).afirst()
 return object
 }}}


 I'm having the following error:
 ''"The client was disconnected by the server because of inactivity. See
 wait_timeout and interactive_timeout for configuring this behavior"''

 Initially the work codes fine, the error only happens after a few hours
 (maybe 8h, like the default wait_timeout variable) after I restart the
 (nginx) server.
 It's a low traffic website so it's very possible the function is executed
 only once a day.

 In my understanding, Django always opens a connection, executes a query
 and then closes a connection.
 Is it not closing the connection when using ''"afirst()"''? This feels
 seems like a bug to me, or is something in the documentation I'm not
 getting.

 Any help? Thank you in advance!


 


 **Other things that I tried:**
 - Before doing the connection.close(), I would have an error like:
 ''"MySQL server has gone away"''
 - Adding close_old_connections() before asyncio.run. Don't understand why
 there is an inactive connection left open at all.
 - Increasing the wait_timeout value and interactive_timeout variables in
 my MySQL config file. I find it very strange that this had no impact at
 all but the ''"SHOW VARIABLES"'' command shows me they are indeed
 currently set to 31536000.
 - Then I thought that maybe the connection from Django is somehow
 independent of that and tried setting ''CONN_HEALTH_CHECKS'' option to
 True, in the hopes that "if the health check fails, the connection will be
 re-established without failing the request"
 - Changing the ''CONN_MAX_AGE'' from the default 0 to "None" in the Django
 settings file, which according to Django docs, means an unlimited
 persistent database connection, but then I would have a ''"Lost connection
 to MySQL server during query"''

-- 
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/01070188d406352b-0a033ab0-021d-45e1-9a9b-fa664649f534-00%40eu-central-1.amazonses.com.

Re: [Django] #34642: File.open to support different encodings

[Django]

#34642: File.open to support different encodings
---+
 Reporter:  Tomasz Melcer  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Core (Other)   |  Version:  dev
 Severity:  Normal |   Resolution:  wontfix
 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 Natalia Bidart):

 * easy:  0 => 1
 * stage:  Unreviewed => Accepted


Comment:

 Reopening and accepting since there seems to be a consensus in the
 [https://forum.djangoproject.com/t/file-open-to-support-different-
 encodings/21491 developer forum].

-- 
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/01070188d3c1813c-2c9bdbaf-b8b0-4904-9df7-94970dcd5a26-00%40eu-central-1.amazonses.com.

Re: [Django] #32210: Django Admin with Inlines not using UUIDField default value

[Django]

#32210: Django Admin with Inlines not using UUIDField default value
--+
 Reporter:  Joseph Metzinger  |Owner:  Neeraj Kumar
 Type:  Bug   |   Status:  assigned
Component:  Forms |  Version:  4.2
 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 Natalia Bidart):

 * needs_tests:  1 => 0


Comment:

 Resetting the PR flags to ensure the new PR gets picked up in the review
 queue.

-- 
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/01070188d3a3aad9-3496ce61-dcd5-44bd-943f-80b8d6b8c1e7-00%40eu-central-1.amazonses.com.

Re: [Django] #34634: Creating objects with nested MTI crashes.

[Django]

#34634: Creating objects with nested MTI crashes.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Akash
 |  Kumar Sen
 Type:  Bug  |   Status:  assigned
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:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Akash Kumar Sen):

 Please share your thoughts about the following
 [https://github.com/django/django/pull/16952#discussion_r1233827427
 comment]. I will update the patch 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/01070188d39881ad-f333879e-338e-40e7-9373-fcd5e7a8774e-00%40eu-central-1.amazonses.com.

Re: [Django] #34634: Creating objects with nested MTI crashes.

[Django]

#34634: Creating objects with nested MTI crashes.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Akash
 |  Kumar Sen
 Type:  Bug  |   Status:  assigned
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:  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/01070188d38a3293-526d3fdb-12a4-4554-b97c-848732a28b9a-00%40eu-central-1.amazonses.com.

Re: [Django] #34661: Peppering user passwords

[Django]

#34661: Peppering user passwords
--+--
 Reporter:  Fatih Erikli  |Owner:  nobody
 Type:  New feature   |   Status:  closed
Component:  contrib.auth  |  Version:  4.2
 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 Mariusz Felisiak):

 * type:  Uncategorized => New 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/01070188d3609d9f-bccb305c-7891-4beb-b16d-c3b77e55acd1-00%40eu-central-1.amazonses.com.

Re: [Django] #34542: Required fields allowed to be blank are not accepted non-interactively using createsuperuser

[Django]

#34542: Required fields allowed to be blank are not accepted non-interactively
using createsuperuser
-+-
 Reporter:  Lantizia |Owner:  Anvansh
 |  Singh
 Type:  Bug  |   Status:  assigned
Component:  contrib.auth |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  auth | Triage Stage:  Accepted
  createsuperuser superuser email|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Natalia Bidart):

 Syed, can you please your whole invocation and shell result? For me, your
 command prompts for password:

 {{{
 $ python manage.py createsuperuser --email "" --user admin
 Password:
 Operation cancelled.
 }}}

 And when passing `--nopinput`, I get an error:

 {{{
 $ python manage.py createsuperuser --email "" --user admin --noinput
 CommandError: You must use --email with --noinput.
 }}}

-- 
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/01070188d36039e9-62e14bfe-7143-4ae9-9369-9c68812af9ab-00%40eu-central-1.amazonses.com.

Re: [Django] #34661: Peppering user passwords

[Django]

#34661: Peppering user passwords
---+--
 Reporter:  Fatih Erikli   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.auth   |  Version:  4.2
 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 Mariusz Felisiak):

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


Comment:

 Duplicate of #30561.

-- 
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/01070188d35e056b-8113ae48-0470-4614-b0aa-3a9634f9385f-00%40eu-central-1.amazonses.com.

Re: [Django] #34658: New assertion `assertNotInHTML`, like `assertContains` has `assertNotContains`

[Django]

#34658: New assertion `assertNotInHTML`, like `assertContains` has
`assertNotContains`
-+-
 Reporter:  Thibaud Colas|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Testing framework|  Version:
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  testcases, unit  | Triage Stage:
  tests, HTML, assertions, testing   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Thibaud Colas):

 Sorry about that, I thought I had read the ticket creation guidelines to
 check what the protocol is, but clearly missed the most important bits.

-- 
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/01070188d2d309b7-b58ed705-84b3-4944-b8d3-941735c72c1b-00%40eu-central-1.amazonses.com.

Re: [Django] #34657: Testing assertions `assertContains` and `assertInHTML` should output the haystack on failure

[Django]

#34657: Testing assertions `assertContains` and `assertInHTML` should output the
haystack on failure
-+-
 Reporter:  Thibaud Colas|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Testing framework|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:  HTML, assertions,| Triage Stage:  Accepted
  testing|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Thibaud Colas):

 Sorry, I didn’t realise feature requests require a forum post! I’ll know
 for next time.

-- 
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/01070188d2d1b2ac-84086167-c889-4423-8974-80dc5b38b681-00%40eu-central-1.amazonses.com.

Re: [Django] #34656: Wrong HTML generation in Django admin's change_password form

[Django]

#34656: Wrong HTML generation in Django admin's change_password  form
-+-
 Reporter:  Yaser Amiri  |Owner:  Yaser
 |  Amiri
 Type:  Bug  |   Status:  closed
Component:  contrib.admin|  Version:  4.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  1
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"3f1bcfeeaeaeaa97ba221b7d6e41962162e7" 3f1bc222]:
 {{{
 #!CommitTicketReference repository=""
 revision="3f1bcfeeaeaeaa97ba221b7d6e41962162e7"
 Fixed #34656 -- Fixed unclosed div in admin password change template.

 Regression in 6991880109e35c879b71b7d9d9c154baeec12b89.
 }}}

-- 
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/01070188d27c9e84-721ed4ca-34e8-43bc-be4b-484bf92bf9cc-00%40eu-central-1.amazonses.com.

Re: [Django] #34665: CreateModel with manually added RenameField crashes on SQLite. (was: An OperationalError is thrown when using SQLite database in Django 4.1 during 'migrate', while it works normal

[Django]

#34665: CreateModel with manually added RenameField crashes on SQLite.
-+-
 Reporter:  Amchii   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  sqlite3  | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

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


Comment:

 It worked on Django 4.0 because the `person` table was recreated by the
 second migrations (which is no longer necessary in SQLite 3.35.5+, see
 3702819227fd0cdd9b581cd99e11d1561d51cbeb), however in all versions of
 Django index is created on a wrong column:
 {{{
 ALTER TABLE "person" RENAME COLUMN "open_id" TO "open_uid";
 CREATE INDEX "person_open_id_aac92076" ON "person" ("open_id");
 }}}

 > Although I manually added a line instead of using makemigrations when
 renaming the 'open_id' field, it should still work properly?

 In general, you can edit migrations manually, but you do so at your own
 risk. In this case you should update the column name in the `CreateModel`
 operation instead of adding `RenameField`.

-- 
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/01070188d27ac1f0-36db43be-a4d5-47eb-a1ec-abf4154a07e6-00%40eu-central-1.amazonses.com.