Re: [Django] #31606: Cannot mix Exists expression with keyword arguments to When

2020-05-21 Thread Django
#31606: Cannot mix Exists expression with keyword arguments to When
-+-
 Reporter:  Ryan Heard   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Simon Charette):

 * type:  Cleanup/optimization => New feature
 * version:  3.0 => master
 * component:  Uncategorized => Database layer (models, ORM)
 * stage:  Unreviewed => Accepted


-- 
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/064.1800cd11e530f03b2696dcd67723030d%40djangoproject.com.


Re: [Django] #31520: ManifestStaticFilesStorage should not raise ValueError on missing file when manifest_strict=False

2020-05-21 Thread Django
#31520: ManifestStaticFilesStorage should not raise ValueError on missing file 
when
manifest_strict=False
-+-
 Reporter:  thenewguy|Owner:  thenewguy
 Type:  Bug  |   Status:  assigned
Component:  contrib.staticfiles  |  Version:  3.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 thenewguy):

 * type:  Uncategorized => Bug


-- 
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/067.aa97d38b94cb45766f5fe2f780ee4246%40djangoproject.com.


Re: [Django] #31608: forms.DateTimeField parses ISO 8601 datetime with offset as aware when USE_TZ is False.

2020-05-21 Thread Django
#31608: forms.DateTimeField parses ISO 8601 datetime with offset as aware when
USE_TZ is False.
-+-
 Reporter:  Carlton Gibson   |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  3.1
 Severity:  Release blocker  |   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 Carlton Gibson ):

 In [changeset:"a6c773aa869655e9dbb86ce9b500ddf1159c71b0" a6c773a]:
 {{{
 #!CommitTicketReference repository=""
 revision="a6c773aa869655e9dbb86ce9b500ddf1159c71b0"
 [3.1.x] Fixed #31608 -- Doc'd that form ISO 8601 datetime parsing always
 retains tzinfo.

 Backport of 643207efaebbff4e7c3ebcbf9ca49fb6197137e1 from master
 }}}

-- 
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/071.830d870c423b87b286246cd6c7f83b7b%40djangoproject.com.


Re: [Django] #31608: forms.DateTimeField parses ISO 8601 datetime with offset as aware when USE_TZ is False.

2020-05-21 Thread Django
#31608: forms.DateTimeField parses ISO 8601 datetime with offset as aware when
USE_TZ is False.
-+-
 Reporter:  Carlton Gibson   |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  3.1
 Severity:  Release blocker  |   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 GitHub ):

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


Comment:

 In [changeset:"643207efaebbff4e7c3ebcbf9ca49fb6197137e1" 643207ef]:
 {{{
 #!CommitTicketReference repository=""
 revision="643207efaebbff4e7c3ebcbf9ca49fb6197137e1"
 Fixed #31608 -- Doc'd that form ISO 8601 datetime parsing always retains
 tzinfo.
 }}}

-- 
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/071.a4c9222c49f15481b75ae2e22867ad78%40djangoproject.com.


Re: [Django] #31608: forms.DateTimeField parses ISO 8601 datetime with offset as aware when USE_TZ is False.

2020-05-21 Thread Django
#31608: forms.DateTimeField parses ISO 8601 datetime with offset as aware when
USE_TZ is False.
-+-
 Reporter:  Carlton Gibson   |Owner:  Hasan
 |  Ramezani
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  3.1
 Severity:  Release blocker  |   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 Carlton Gibson):

 * 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/071.47d1186b80bc21f2f4001aceeb4e%40djangoproject.com.


Re: [Django] #27452: Add Postgres serial field to contrib.postgres

2020-05-21 Thread Django
#27452: Add Postgres serial field to contrib.postgres
-+-
 Reporter:  Johannes Hoppe   |Owner:  Johannes
 |  Hoppe
 Type:  New feature  |   Status:  assigned
Component:  contrib.postgres |  Version:  master
 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 InvalidInterrupt):

 * cc: InvalidInterrupt (added)


-- 
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/067.d0d8c62b47f35fb9942b04bfe161bcd1%40djangoproject.com.


Re: [Django] #29707: New admin autocomplete widget ignores limit_choices_to filter in referring FK definition

2020-05-21 Thread Django
#29707: New admin autocomplete widget ignores limit_choices_to filter in 
referring
FK definition
-+-
 Reporter:  David W. Lloyd   |Owner:  Johannes
 Type:   |  Hoppe
  Cleanup/optimization   |   Status:  assigned
Component:  contrib.admin|  Version:  master
 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 Carsten Fuchs):

 * cc: Carsten Fuchs (added)


-- 
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/067.934efecd67560696e21e0d01da78cb4b%40djangoproject.com.


Re: [Django] #31546: Replace Command.requires_system_checks = True by something like Command.required_system_checks = '__all__'

2020-05-21 Thread Django
#31546: Replace Command.requires_system_checks = True by something like
Command.required_system_checks = '__all__'
-+-
 Reporter:  Hasan Ramezani   |Owner:  Hasan
 Type:   |  Ramezani
  Cleanup/optimization   |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 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 Carlton Gibson ):

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


Comment:

 In [changeset:"c60524c658f197f645b638f9bcc553103bfe2630" c60524c6]:
 {{{
 #!CommitTicketReference repository=""
 revision="c60524c658f197f645b638f9bcc553103bfe2630"
 Fixed #31546 -- Allowed specifying list of tags in
 Command.requires_system_checks.
 }}}

-- 
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/067.69a8160a492ca5f1bb86b2c221a1eb06%40djangoproject.com.


Re: [Django] #30952: KeyError: '_password_reset_token' during password reset.

2020-05-21 Thread Django
#30952: KeyError: '_password_reset_token' during password reset.
--+--
 Reporter:  defigor   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  2.1
 Severity:  Normal|   Resolution:
 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 Andrey Shakurov):

 * cc: Andrey Shakurov (added)
 * status:  closed => new
 * resolution:  needsinfo =>


Comment:

 The same issue can be reproduced in newer versions. I've tested it in
 3.0.4 with database-backed sessions and all of the standard
 django.contrib.auth.urls
 Steps to reproduce:
 1. Open the first tab, login to your app.
 2. Open the second tab on "password_reset" page. Enter the email of a user
 from the first tab. Submit form.
 3. Click the "password_reset_confirm" link from an email that should've
 been received. Fill the form with your new password and submit it.

 This will trigger this line
 
[https://github.com/django/django/blob/master/django/contrib/auth/views.py#L302]
 against session without INTERNAL_RESET_SESSION_TOKEN which will lead to
 KeyError

 Way to fix the issue: use .pop() instead of del

 {{{
 self.request.session.pop(auth_views.INTERNAL_RESET_SESSION_TOKEN, None)
 }}}

-- 
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/065.6adab2b7089e2b8184f2579dbc49cf90%40djangoproject.com.


Re: [Django] #31546: Replace Command.requires_system_checks = True by something like Command.required_system_checks = '__all__'

2020-05-21 Thread Django
#31546: Replace Command.requires_system_checks = True by something like
Command.required_system_checks = '__all__'
-+-
 Reporter:  Hasan Ramezani   |Owner:  Hasan
 Type:   |  Ramezani
  Cleanup/optimization   |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 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 felixxm):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.7af2dc8e787f1d928a53680ad59193fc%40djangoproject.com.


Re: [Django] #30375: Use "NO KEY" when doing select_for_update for PostgreSQL

2020-05-21 Thread Django
#30375: Use "NO KEY" when doing select_for_update for PostgreSQL
-+-
 Reporter:  Manuel Weitzman  |Owner:  Manuel
 Type:   |  Weitzman
  Cleanup/optimization   |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  postgres, lock,  | Triage Stage:  Ready for
  database, operation|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"a4e6030904df63b3f10aa0729b86dc6942b0458e" a4e6030]:
 {{{
 #!CommitTicketReference repository=""
 revision="a4e6030904df63b3f10aa0729b86dc6942b0458e"
 Fixed #30375 -- Added FOR NO KEY UPDATE support to
 QuerySet.select_for_update() on PostgreSQL.
 }}}

-- 
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/064.c5541f7c8bd0a9294fedf42deb9fe826%40djangoproject.com.


Re: [Django] #28872: JSONField __in operator breaks when given a values_list()

2020-05-21 Thread Django
#28872: JSONField __in operator breaks when given a values_list()
--+
 Reporter:  Jerome Leclanche  |Owner:  VCAMP
 Type:  Bug   |   Status:  assigned
Component:  contrib.postgres  |  Version:  master
 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 felixxm):

 * version:  1.11 => master


Comment:

 With the new implementation of `JSONField` this issue is PostgreSQL-
 specific.

-- 
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/068.274af847ebaaced3c2f49dd35bbfc612%40djangoproject.com.