Re: [Django] #35384: Assigning a file without a name property to a FileField results in file getting discarded silently

2024-05-12 Thread Django
#35384: Assigning a file without a name property to a FileField results in file
getting discarded silently
-+-
 Reporter:  john-parton  |Owner:  Jonny
 |  Park
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  5.0
  (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 Sarah Boyce):

 * 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/0107018f70aa2b91-fc66c468-f6fe-4809-a9d5-77e2f113fbc1-00%40eu-central-1.amazonses.com.


Re: [Django] #35408: Optimize post-migrate permission creation

2024-05-12 Thread Django
#35408: Optimize post-migrate permission creation
-+-
 Reporter:  Adam Johnson |Owner:  Adam
 Type:   |  Johnson
  Cleanup/optimization   |   Status:  closed
Component:  contrib.auth |  Version:  dev
 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
-+-
Changes (by Sarah Boyce <42296566+sarahboyce@…>):

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

Comment:

 In [changeset:"d2c5a30e5a8595d06c4a70ff0f66032fee0d3c8e" d2c5a30e]:
 {{{#!CommitTicketReference repository=""
 revision="d2c5a30e5a8595d06c4a70ff0f66032fee0d3c8e"
 Fixed #35408 -- Optimized post-migrate permission creation.

 co-authored-by: Mariusz Felisiak 
 }}}
-- 
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/0107018f70a96c14-d18e9b12-3758-4fe6-b250-5961068b9349-00%40eu-central-1.amazonses.com.


Re: [Django] #35445: Adding model field validators to FloatField and IntegerField is not possible.

2024-05-12 Thread Django
#35445: Adding model field validators to FloatField and IntegerField is not
possible.
--+
 Reporter:  AjmalPonneth  |Owner:  AjmalPonneth
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  5.0
 Severity:  Normal|   Resolution:  invalid
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Sarah Boyce):

 * component:  Database layer (models, ORM) => Core (Other)
 * resolution:   => invalid
 * status:  assigned => closed

Comment:

 Hi AjmalPonneth,
 MinLengthValidator and MaxLengthValidator are not meant to be used for
 floats as it is checking the length. You may want to use MinValueValidator
 and MaxValueValidator.
 If you want to make some tweaks to the docs around which types the
 validators can be used for, feel free 👍
-- 
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/0107018f70a61c79-4453b127-a481-46bd-bada-599453349be7-00%40eu-central-1.amazonses.com.


Re: [Django] #35443: Fix negative numbers for ordinals (was: Support negative numbers for ordinals)

2024-05-12 Thread Django
#35443: Fix negative numbers for ordinals
--+
 Reporter:  Siburg|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.humanize  |  Version:  5.0
 Severity:  Normal|   Resolution:
 Keywords:  humanize ordinal  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Sarah Boyce):

 * stage:  Unreviewed => Accepted
 * summary:  Support negative numbers for ordinals => Fix negative numbers
 for ordinals

Comment:

 I think option 1 with a tweak to the docs, I don't think saying -2nd makes
 sense to support
-- 
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/0107018f70a012d6-10de0c7f-a057-48ac-9f31-35dfeeac489c-00%40eu-central-1.amazonses.com.


Re: [Django] #35441: Context autoescape parameter is not documented

2024-05-12 Thread Django
#35441: Context autoescape parameter is not documented
-+-
 Reporter:  Roman Donchenko  |Owner:  John
 Type:   |  Higgins
  Cleanup/optimization   |   Status:  assigned
Component:  Template system  |  Version:  5.0
 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/0107018f7094deaa-826b7aae-a4c7-4243-a7f1-f9050a02caf4-00%40eu-central-1.amazonses.com.


Re: [Django] #35441: Context autoescape parameter is not documented

2024-05-12 Thread Django
#35441: Context autoescape parameter is not documented
-+-
 Reporter:  Roman Donchenko  |Owner:  John
 Type:   |  Higgins
  Cleanup/optimization   |   Status:  assigned
Component:  Template system  |  Version:  5.0
 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 John Higgins):

 Here's a link to the patch:
 https://github.com/django/django/pull/18161/files
-- 
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/0107018f6fef1622-d2588b6d-7d43-4f20-8fa7-312a6c23cfc3-00%40eu-central-1.amazonses.com.


Re: [Django] #35441: Context autoescape parameter is not documented

2024-05-12 Thread Django
#35441: Context autoescape parameter is not documented
-+-
 Reporter:  Roman Donchenko  |Owner:  John
 Type:   |  Higgins
  Cleanup/optimization   |   Status:  assigned
Component:  Template system  |  Version:  5.0
 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 John Higgins):

 * has_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/0107018f6feca68f-e72315a3-cd6e-4b21-881f-4c30698c56e1-00%40eu-central-1.amazonses.com.


Re: [Django] #35442: N+1 queries from RelatedManager + only("pk")

2024-05-12 Thread Django
#35442: N+1 queries from RelatedManager + only("pk")
-+-
 Reporter:  REGNIER Guillaume|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  4.2
  (models, ORM)  |
 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
-+-
Comment (by Simon Charette):

 For the record, I checked out I checked out Django 1.9 and it seems the
 issue is present there so while the commit mentioned above that landed in
 1.10 did alter a related test it didn't actually break anything in this
 regard.
-- 
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/0107018f6e91264b-d3fa1022-3c37-41ea-acbe-caf5df10adf8-00%40eu-central-1.amazonses.com.


Re: [Django] #35444: Add generic support for order by to Aggregate

2024-05-12 Thread Django
#35444: Add generic support for order by to Aggregate
-+-
 Reporter:  Chris M  |Owner:  Chris M
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  orderableaggmixin| Triage Stage:  Accepted
  aggregate  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

 * cc: Simon Charette (added)
 * stage:  Unreviewed => Accepted

Comment:

 As discussed on the other ticket I think that moving this capability to
 the generic `Aggregate` class makes sense.
-- 
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/0107018f6e81023d-2c58f2fa-6683-4867-bec3-805e5d956ae2-00%40eu-central-1.amazonses.com.


Re: [Django] #31405: LoginRequiredAuthenticationMiddleware force all views to require authentication by default.

2024-05-12 Thread Django
#31405: LoginRequiredAuthenticationMiddleware force all views to require
authentication by default.
--+--
 Reporter:  Mehmet İnce   |Owner:  Hisham Mahmood
 Type:  New feature   |   Status:  assigned
Component:  contrib.auth  |  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 Hisham Mahmood):

 * 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/0107018f6e78f070-1b5c12c3-adf2-4e65-940f-e0d5897ee44a-00%40eu-central-1.amazonses.com.


Re: [Django] #35275: Constraints validation fails on UniqueConstraint using OpClass

2024-05-12 Thread Django
#35275: Constraints validation fails on UniqueConstraint using OpClass
-+-
 Reporter:  Mathieu Kniewallner  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  1 => 0
 * owner:  Mathieu Kniewallner => Mariusz Felisiak

Comment:

 [https://github.com/django/django/pull/18160 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/0107018f6e6c292c-5352dbe2-bb28-4cc3-9e0e-72fed5b33080-00%40eu-central-1.amazonses.com.