Re: [Django] #28719: Better exception message when get_queryset returns None

2017-10-17 Thread Django 
#28719: Better exception message when get_queryset returns None
---+--
 Reporter:  Bjorn Kristinsson  |Owner:  (none)
 Type:  Bug|   Status:  new
Component:  Generic views  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by Zac Yauney):

 * owner:  Zac Yauney => (none)
 * status:  assigned => new


-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.8afdcef519b48335a94106bc71a4459c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28720: Add HttpRequest.get_full_path_info

2017-10-17 Thread Django 
#28720: Add HttpRequest.get_full_path_info
---+--
 Reporter:  Jonas Haag |Owner:  (none)
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Zac Yauney):

 * owner:  Zac Yauney => (none)
 * status:  assigned => new


Comment:

 Didn't realize this was already patched. Oops

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.6e2ecccf8685cef5f5066c4d33a958fb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28720: Add HttpRequest.get_full_path_info

2017-10-17 Thread Django 
#28720: Add HttpRequest.get_full_path_info
---+--
 Reporter:  Jonas Haag |Owner:  Zac Yauney
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by Zac Yauney):

 * owner:  nobody => Zac Yauney
 * 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.1720af86afe355bd583e4192c802e0b4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28291: ArrayField cannot contain JSONField; causes SQL error

2017-10-17 Thread Django 
#28291: ArrayField cannot contain JSONField; causes SQL error
--+--
 Reporter:  Richard Eames |Owner:  Zac Yauney
 Type:  Bug   |   Status:  assigned
Component:  contrib.postgres  |  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 Zac Yauney):

 * owner:  Zac Yauney => Zac Yauney


Comment:

 Using different GitHub Profile

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.0bab17ec9903ea24555f50d1d3f8e884%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28719: Better exception message when get_queryset returns None

2017-10-17 Thread Django 
#28719: Better exception message when get_queryset returns None
---+--
 Reporter:  Bjorn Kristinsson  |Owner:  yauneyz
 Type:  Bug|   Status:  assigned
Component:  Generic views  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by yauneyz):

 * owner:  (none) => yauneyz
 * 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.0bb818537c7efe7615bc0baa3c307279%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28720: Add HttpRequest.get_full_path_info

2017-10-17 Thread Django 
#28720: Add HttpRequest.get_full_path_info
-+
   Reporter:  Jonas Haag |  Owner:  nobody
   Type:  New feature| Status:  new
  Component:  HTTP handling  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 ``HttpRequest.get_full_path`` returns the ``HttpRequest.path`` based full
 path, including query string. Example: ``/posts/12345/?foo=bar``.

 We should add a counterpart for ``HttpRequest.path_info`` that includes
 the ``SCRIPT_NAME``, if set. Example: ``/scriptname/posts/12345/?foo=bar``

 Example use case: Adding hreflang meta tags to your  section.
 This must include the ``SCRIPT_NAME`` prefix as well, otherwise invalid
 URLs are given.

 {{{
 https://yourdomain.com{{
 request.get_full_path_info }}">
 }}}

 Patch: https://github.com/django/django/pull/9253

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.ef898006473736af645c69d0851c282b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28720: Add HttpRequest.get_full_path_info

2017-10-17 Thread Django 
#28720: Add HttpRequest.get_full_path_info
---+--
 Reporter:  Jonas Haag |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Description changed by Jonas Haag:

Old description:

> ``HttpRequest.get_full_path`` returns the ``HttpRequest.path`` based full
> path, including query string. Example: ``/posts/12345/?foo=bar``.
>
> We should add a counterpart for ``HttpRequest.path_info`` that includes
> the ``SCRIPT_NAME``, if set. Example:
> ``/scriptname/posts/12345/?foo=bar``
>
> Example use case: Adding hreflang meta tags to your  section.
> This must include the ``SCRIPT_NAME`` prefix as well, otherwise invalid
> URLs are given.
>
> {{{
> https://yourdomain.com{{
> request.get_full_path_info }}">
> }}}
>
> Patch: https://github.com/django/django/pull/9253

New description:

 `HttpRequest.get_full_path` returns the `HttpRequest.path` based full
 path, including query string. Example: `/posts/12345/?foo=bar`.

 We should add a counterpart for `HttpRequest.path_info` that includes the
 `SCRIPT_NAME`, if set. Example: `/scriptname/posts/12345/?foo=bar`

 Example use case: Adding hreflang meta tags to your `` section. This
 must include the `SCRIPT_NAME` prefix as well, otherwise invalid URLs are
 given.

 {{{
 https://yourdomain.com{{
 request.get_full_path_info }}">
 }}}

 Patch: https://github.com/django/django/pull/9253

--

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.e9191a35c7705d74aa345238bd53bdd9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28712: Add ability to apply separate attributes to ChoiceWidget options

2017-10-17 Thread Django 
#28712: Add ability to apply separate attributes to ChoiceWidget options
-+--
 Reporter:  Stephen Swatman  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  ChoiceWidget | Triage Stage:  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by Tim Graham):

 * easy:  1 => 0


Comment:

 Could you describe your use case in more detail? Is there a reason that
 overriding `ChoiceWidget.create_option()` wouldn't work?

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.9b6f6c2741ef7972777378a94b1b5e93%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28718: Password reset shouldn't depend on the current password being hashed with a supported hasher (was: Resetting your password shouldn't depend on your current password being hashed w

2017-10-17 Thread Django 
#28718: Password reset shouldn't depend on the current password being hashed 
with a
supported hasher
--+
 Reporter:  Josh Harwood  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.11
 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 Tim Graham):

 * stage:  Unreviewed => Accepted
 * type:  Cleanup/optimization => Bug


Comment:

 It looks like this is a regression in
 aeb1389442d0f9669edf6660b747fd10693b63a7. The change in
 `django/contrib/auth/forms.py` line 234 added the undesired check that the
 password uses a valid hasher.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.14b6a6b7ff8306040024c51c21939dba%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28705: Wrong annotation when used with QuerySet.order_by() (was: Wrong annotation when used with order_by)

2017-10-17 Thread Django 
#28705: Wrong annotation when used with QuerySet.order_by()
-+-
 Reporter:  Rafael Capucho   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.11
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  Annotate, ORM,   | Triage Stage:
  Order_by   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * component:  Uncategorized => Database layer (models, ORM)


Comment:

 Could you add a `tests.py` file that demonstrates the issue (and/or
 replace the screenshot in the description)? The screenshot isn't
 particularly friendly for someone trying to reproduce this since they have
 to retype everything.

 Did you read the
 [https://docs.djangoproject.com/en/dev/topics/db/aggregation
 /#aggregations-and-other-queryset-clauses aggregation topic guide] to
 ensure that none of the documented issues there are the cause of the
 behavior?

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.7e35de0d975fb5da0f55fa3189164ca4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28714: Add system checks for invalid model field names in Indexes (was: Django Makemigrations don't check if field name from indexes exists on model before creating a migration.)

2017-10-17 Thread Django 
#28714: Add system checks for invalid model field names in Indexes
-+-
 Reporter:  Gabriel  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (System |  Version:  1.11
  checks)|
 Severity:  Normal   |   Resolution:
 Keywords:  indexes, migrate,| Triage Stage:  Accepted
  makemigrations |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * type:  Bug => Cleanup/optimization
 * component:  Migrations => Core (System checks)
 * stage:  Unreviewed => Accepted


Comment:

 My first thought is that adding system checks for the `Index` class is the
 way to solve this.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.12c24e42b4d05a68772b8aa9d757a5d1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28719: Better exception message when get_queryset returns None

2017-10-17 Thread Django 
#28719: Better exception message when get_queryset returns None
---+--
 Reporter:  Bjorn Kristinsson  |Owner:  (none)
 Type:  Bug|   Status:  new
Component:  Generic views  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by Bjorn Kristinsson):

 * status:  assigned => new
 * owner:  Bjorn Kristinsson => (none)


Comment:

 Created a pull request, https://github.com/django/django/pull/9255, not
 entirely sure why the tests are failing.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.cf60708350ba68f509f56009a5df4d7e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28719: Better exception message when get_queryset returns None

2017-10-17 Thread Django 
#28719: Better exception message when get_queryset returns None
-+-
 Reporter:  Bjorn Kristinsson|Owner:  Bjorn
 |  Kristinsson
 Type:  Bug  |   Status:  assigned
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Bjorn Kristinsson):

 * owner:  nobody => Bjorn Kristinsson
 * 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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.60c53fc99486fa5e7b33c9cc28d61e78%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28718: Resetting your password shouldn't depend on your current password being hashed with a supported hasher

2017-10-17 Thread Django 
#28718: Resetting your password shouldn't depend on your current password being
hashed with a supported hasher
-+-
 Reporter:  Josh Harwood |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  1.11
 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
-+-

Comment (by Josh Harwood):

 Replying to [comment:1 Tim Graham]:
 > Where's that restriction implemented?

 This line with "has_usable_password":
 https://github.com/django/django/blob/master/django/contrib/auth/forms.py#L264

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.3f3fde1f7dfd52f8b3111424ba79b529%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28719: Better exception message when get_queryset returns None

2017-10-17 Thread Django 
#28719: Better exception message when get_queryset returns None
-+
   Reporter:  Bjorn Kristinsson  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  Generic views  |Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+
 One of my `ListViews` suddenly started raising `TemplateDoesNotExist` with
 a rather cryptic (to me) message:

 {{{
 Template-loader postmortem

 Django tried loading these templates, in this order:

 Using engine :
 This engine did not provide a list of tried templates.
 }}}

 It took me a while to realise this was because my get_queryset wasn't
 returning anything. It did some filtering based on user settings, and I
 didn't have a fallback for when none of the filtering steps applied.

 Thought it might be helpful to have a better message is no template names
 are found and `object_list` is `None`. Suggesting: "Expected a queryset,
 but found None. Please check that .get_queryset() returns a
 queryset." Pull request coming up.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.86ab5971f43dfd09738812efe65f0fdd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28718: Resetting your password shouldn't depend on your current password being hashed with a supported hasher

2017-10-17 Thread Django 
#28718: Resetting your password shouldn't depend on your current password being
hashed with a supported hasher
-+-
 Reporter:  Josh Harwood |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.auth |  Version:  1.11
 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 Tim Graham):

 * type:  Bug => Cleanup/optimization


Comment:

 Where's that restriction implemented?

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.2004c5476a9dfb4f7b8edf28eb0a27a7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28694: Make django.utils.text.slugify() remove redundant dashes and underscores (was: django.utils.text.slugify Django slugify correction)

2017-10-17 Thread Django 
#28694: Make django.utils.text.slugify() remove redundant dashes and underscores
-+-
 Reporter:  Elinaldo do  |Owner:  Elinaldo
  Nascimento Monteiro|  do Nascimento Monteiro
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Utilities|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  slugify, util| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham):

 * stage:  Unreviewed => Accepted
 * type:  New feature => Cleanup/optimization


-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.690f8848587a68281e66f5f35a5fdd3e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #28718: Resetting your password shouldn't depend on your current password being hashed with a supported hasher

2017-10-17 Thread Django 
#28718: Resetting your password shouldn't depend on your current password being
hashed with a supported hasher
-+
   Reporter:  mr-bo-jangles  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component:  contrib.auth   |Version:  1.11
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 Currently the built in django password reset system requires that you have
 an active account and that your password can be compared to by an enabled
 hasher.

 I think that this is in error, as you are about to reset the password to
 something new (hence resetting it) and the standard process of password
 resetting requires an email confirmation. I can see no way in which this
 is able to be abused by a malicious 3rd party. If I'm mistaken here then
 feel free to correct me.

 I propose that the system is changed to just require that the user is
 active and that their password is not marked disabled as per the
 UNUSABLE_PASSWORD_PREFIX.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/056.b556015ac55901bafbb52e3b2c8d0ffa%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26056: ArrayField does not work with ValueListQuerySet

2017-10-17 Thread Django 
#26056: ArrayField does not work with ValueListQuerySet
--+
 Reporter:  Przemek   |Owner:  (none)
 Type:  New feature   |   Status:  new
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
--+

Comment (by kosz85):

 I posted solution here:
 https://github.com/django/django/pull/7838#issuecomment-337223376
 It's Array with Subquery, just pure subquery isn't enough.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.790db99b646dbbf0b2e376d6b1e8ae35%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28636: Allow customizing the translation fallback language

2017-10-17 Thread Django 
#28636: Allow customizing the translation fallback language
-+-
 Reporter:  Denis Anuschewski|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:   |  Version:  master
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  translation, | Triage Stage:  Accepted
  internationalization, request  |
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Denis Anuschewski):

 Nevermind, I fixed it myself :-)

 The problem was my default of `LANGUAGE_FALLBACK` (I used `LANGUAGE_CODE`
 for that). In normal cases it works fine, but in unit tests it gives
 unintended results when you mock `LANGUAGE_CODE`. The language code then
 changes, but the fallback stays the same, giving you English values as
 result.

 I solved this by setting `LANGUAGE_FALLBACK` to `None` by default, because
 when it gets used in `get_fallback()` it will be overwritten with
 `LANGUAGE_CODE` anyway if not set properly.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.79dea3d9a2fb5fda528909ecc8894146%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.