Re: [Django] #25579: Lack of type adaptation in ArrayField querying/lookups

[Django]

#25579: Lack of type adaptation in ArrayField querying/lookups
-+-
 Reporter:  freshquiz|Owner:  freshquiz
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  ArrayField query | Triage Stage:  Accepted
  lookup |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by freshquiz):

 With the introduction of this commit:
 
[https://github.com/django/django/commit/2495023a4cae28f494d0a6172abfac3a47a0b816]

 ...I realised that the solution may lie at a higher level.

 The `tests.postgres_tests.models.TagField` class has overridden the
 `get_db_prep_value()` method, with the only change being that it ignores
 the `prepared` keyword-arg and always calls `get_prep_value()` on the
 input value.

 This was introduced because the author of that test code would have
 encountered the type adaptation issue which is what this ticket is about.

 So I can't use the `TagField` class to write tests for a solution to this
 ticket, because the problem is solved by that class.
 I.e. Take away the `TagField`'s overriding implementation of
 `get_db_prep_value()` and the problem of this ticket arises.

--
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.340656369167845da7a4c869d3cfc851%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25839: RequestContext does not apply context processors [regression]

[Django]

#25839: RequestContext does not apply context processors [regression]
-+-
 Reporter:  direx|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  RequestContext,  | Triage Stage:  Accepted
  regression |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 As 1.8 is nearly a year old and we only have a single report of the issue,
 I say it's not worth documenting unless someone offers a patch. If so,
 please reopen. 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 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/063.83c56ba99393275e8f30d7f566f78ac0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26294: Clarify call_command()'s handling of args and options (was: call_command doesn't raise same errors from option parsing as running command)

[Django]

#26294: Clarify call_command()'s handling of args and options
--+
 Reporter:  mbox  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  master
 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 timgraham):

 * has_patch:  0 => 1


Comment:

 Makes sense, Claude. I expanded that a bit with some examples:
 [https://github.com/django/django/pull/6284 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 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/062.0f6c3243952b7e2a5ba412326b7247ff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26283: SplitArrayField failed to validate because remove_trailing_nulls doesn't work properly

[Django]

#26283: SplitArrayField failed to validate because remove_trailing_nulls doesn't
work properly
--+
 Reporter:  mochawich |Owner:  quaspas
 Type:  Bug   |   Status:  closed
Component:  contrib.postgres  |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"91f87b8f91f5f8d01ac4b814dce218be27f56ab2" 91f87b8]:
 {{{
 #!CommitTicketReference repository=""
 revision="91f87b8f91f5f8d01ac4b814dce218be27f56ab2"
 Fixed #26283 -- Fixed removal of trailing nulls for SplitArrayField.
 }}}

--
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.f37257aba5d073d9187a85e1dde0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26283: SplitArrayField failed to validate because remove_trailing_nulls doesn't work properly

[Django]

#26283: SplitArrayField failed to validate because remove_trailing_nulls doesn't
work properly
--+
 Reporter:  mochawich |Owner:  quaspas
 Type:  Bug   |   Status:  assigned
Component:  contrib.postgres  |  Version:  1.8
 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 quaspas):

 * has_patch:  0 => 1


Comment:

 I have a pull request to offer with the changes suggested from this ticket
 https://github.com/django/django/pull/6283.

--
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.2c56f87b4954e26e7caea2d241c93022%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26343: user_login_failed not fired on PermissionDenied

[Django]

#26343: user_login_failed not fired on PermissionDenied
--+---
 Reporter:  knbk  |Owner:  ieatkittens
 Type:  Bug   |   Status:  closed
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"ab8af342b1d5dbe40502f1adfe8c7a6b746c8004" ab8af342]:
 {{{
 #!CommitTicketReference repository=""
 revision="ab8af342b1d5dbe40502f1adfe8c7a6b746c8004"
 Fixed #26343 -- Sent user_login_failed signal if an auth backend raises
 PermissionDenied.
 }}}

--
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/062.81016e549f111336f093ffd9dbbb154b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26283: SplitArrayField failed to validate because remove_trailing_nulls doesn't work properly

[Django]

#26283: SplitArrayField failed to validate because remove_trailing_nulls doesn't
work properly
--+
 Reporter:  mochawich |Owner:  quaspas
 Type:  Bug   |   Status:  assigned
Component:  contrib.postgres  |  Version:  1.8
 Severity:  Normal|   Resolution:
 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 quaspas):

 * owner:   => quaspas
 * 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.4ec003ae85f849ea957133ecd579327e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #10554: Response.set_cookie should allow setting two cookies of the same name.

[Django]

#10554: Response.set_cookie should allow setting two cookies of the same name.
---+
 Reporter:  jdunck |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  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
---+

Comment (by collinanderson):

 The latest https://tools.ietf.org/html/rfc6265 says we should not do this,
 which makes me think it's not worth it. Is there a real-world problem that
 this would actually solve?

 {{{
Servers SHOULD NOT include more than one Set-Cookie header field in
the same response with the same cookie-name.
 }}}

--
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.fb7a1696aa427f56d625ac7dec576a2c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26350: גינון ברמה אחרת

[Django]

#26350: גינון ברמה אחרת
---+
 Reporter:  haclili|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Core (Other)   |Version:  1.9
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  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 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/050.1306b368177d37795bd709c662b5bb31%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25251: Inconsistent availability of data migrations in TransactionTestCase when using --keepdb

[Django]

#25251: Inconsistent availability of data migrations in TransactionTestCase when
using --keepdb
---+
 Reporter:  davidszotten   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.8
 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 romgar):

 I have updated the rollback section and backward incompatible changes. Not
 really sure if if a good idea to add a "Changed in Django 1.9" and
 "Changed in Django 1.10" sections at the same 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 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.bb385f6f991ef6ce091ee01ba3db8b6b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25251: Inconsistent availability of data migrations in TransactionTestCase when using --keepdb

[Django]

#25251: Inconsistent availability of data migrations in TransactionTestCase when
using --keepdb
---+
 Reporter:  davidszotten   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.8
 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 romgar):

 * 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 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.83fbdf4b00314ba4784352caf397a63a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26345: Clarify that RangeFields always return canonical form of ranges

[Django]

#26345: Clarify that RangeFields always return canonical form of ranges
--+
 Reporter:  dbinetti  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"d3c2d82ddef4b2bcf9d3d0b1ac59d7d65f5a7406" d3c2d82d]:
 {{{
 #!CommitTicketReference repository=""
 revision="d3c2d82ddef4b2bcf9d3d0b1ac59d7d65f5a7406"
 [1.9.x] Fixed #26345 -- Clarified which RangesFields always return a
 canonical form.

 Backport of b3610f38facb33704c1fd77590c6a2fa07c40fa7 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 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.f4cc868f0f4bf41836c59e2aa8bb9f9f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26345: Clarify that RangeFields always return canonical form of ranges

[Django]

#26345: Clarify that RangeFields always return canonical form of ranges
--+
 Reporter:  dbinetti  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.9
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"b3610f38facb33704c1fd77590c6a2fa07c40fa7" b3610f38]:
 {{{
 #!CommitTicketReference repository=""
 revision="b3610f38facb33704c1fd77590c6a2fa07c40fa7"
 Fixed #26345 -- Clarified which RangesFields always return a canonical
 form.
 }}}

--
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.2aaf4b0f5b1a33f3c1b5ff2a666a36c3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25759: Add **kwargs to as_sql method of Expressions

[Django]

#25759: Add **kwargs to as_sql method of Expressions
-+-
 Reporter:  jarshwah |Owner:
 |  kaifeldhoff
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  expressions  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by kaifeldhoff):

 * 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 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.2c886a1fce801729ef5bbc08262be29d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26239: Document auto_now behavior with QuerySet.update()

[Django]

#26239: Document auto_now behavior with QuerySet.update()
--+
 Reporter:  boussouira|Owner:  duane9
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"421ad283d3a0c9814e6cf5b87b393dce09f59474" 421ad283]:
 {{{
 #!CommitTicketReference repository=""
 revision="421ad283d3a0c9814e6cf5b87b393dce09f59474"
 [1.9.x] Fixed #26239 -- Added a note about how auto_now works with
 QuerySet.update().

 Backport of ca5c05ddbe91f4aae38c4543240dbda5f1fb1db2 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 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/068.a04fd6a2050f1ed44feb7ab1c9830f93%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26239: Document auto_now behavior with QuerySet.update()

[Django]

#26239: Document auto_now behavior with QuerySet.update()
--+
 Reporter:  boussouira|Owner:  duane9
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"ca5c05ddbe91f4aae38c4543240dbda5f1fb1db2" ca5c05d]:
 {{{
 #!CommitTicketReference repository=""
 revision="ca5c05ddbe91f4aae38c4543240dbda5f1fb1db2"
 Fixed #26239 -- Added a note about how auto_now works with
 QuerySet.update().
 }}}

--
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/068.acedb11dd39f8eec9dc24cc2ae290fc8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26345: Clarify that RangeFields always return canonical form of ranges

[Django]

#26345: Clarify that RangeFields always return canonical form of ranges
--+
 Reporter:  dbinetti  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.9
 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 timgraham):

 * has_patch:  0 => 1


Comment:

 Thanks for the draft, but this applies to `IntegerRangeField` and
 `BigIntegerRangeField` as well. Here's an
 [https://github.com/django/django/pull/6282 alternate proposal].

--
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.654e29d0008bbccd1c154b1cb98b9353%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26343: user_login_failed not fired on PermissionDenied

[Django]

#26343: user_login_failed not fired on PermissionDenied
--+---
 Reporter:  knbk  |Owner:  ieatkittens
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  Version:  master
 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 ieatkittens):

 * needs_tests:  1 => 0


Comment:

 Regression test 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 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/062.3d23fb87341e0f212d06b7c3a7b0f840%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26239: Document auto_now behavior with QuerySet.update()

[Django]

#26239: Document auto_now behavior with QuerySet.update()
--+
 Reporter:  boussouira|Owner:  duane9
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by duane9):

 Okay, I added a note to that effect.
 https://github.com/django/django/pull/6281

--
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/068.c5992bce0cdedf03fbc515aff777da5a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26343: user_login_failed not fired on PermissionDenied

[Django]

#26343: user_login_failed not fired on PermissionDenied
--+---
 Reporter:  knbk  |Owner:  ieatkittens
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+---
Changes (by timgraham):

 * has_patch:  0 => 1
 * needs_tests:  0 => 1


Comment:

 When adding a link to the pull request, please check "Has patch". Please
 uncheck "Needs tests" when you update your pull request with one.

--
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/062.3393ed0739acb8d07b43d545d87655e1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26338: Getting Queryset item by index with PostgreSQL behaves randomly

[Django]

#26338: Getting Queryset item by index with PostgreSQL behaves randomly
-+-
 Reporter:  pawelad  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  postgresql   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by pawelad):

 OK, sorry for the inconvenience.

--
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/065.4a8fb0ed5dd5162723277953cbc3a276%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26338: Getting Queryset item by index with PostgreSQL behaves randomly

[Django]

#26338: Getting Queryset item by index with PostgreSQL behaves randomly
-+-
 Reporter:  pawelad  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  postgresql   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 Again, I'd ask if you could please provide more details such as a test for
 Django's test suite (ideally) or a sample project to reproduce the issue.
 Although I suspect a bug in your code rather than in Django, there aren't
 enough details here currently to investigate the issue. Ideally, "is it a
 bug?" questions would first be directed to our support channels
 (TicketClosingReasons/UseSupportChannels) and reported here only if
 someone else confirms the problem as a probable bug. 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 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/065.265fe3a0214a85dd2788310b14a97363%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26343: user_login_failed not fired on PermissionDenied

[Django]

#26343: user_login_failed not fired on PermissionDenied
--+---
 Reporter:  knbk  |Owner:  ieatkittens
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+---

Comment (by ieatkittens):

 Work is available at
 https://github.com/ieatkittens/django/tree/ticket_26343.  Docs build fine
 and tests pass under Postgresql.  First time contributing so please let me
 know if I am missing anything!

--
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/062.3ce1091e9f3b0eec23d658062828eda6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26338: Getting Queryset item by index with PostgreSQL behaves randomly

[Django]

#26338: Getting Queryset item by index with PostgreSQL behaves randomly
-+-
 Reporter:  pawelad  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  postgresql   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by pawelad):

 You were right with the {{{order_by}}}, but why setting it on model level
 isn't taking care of that?
 Shouldn't that be enough?
 {{{
 class Meta:
 ordering = ['-field1, '-field2', 'field3']
 }}}

--
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/065.a9a1d28162e171cfae562e26c5ad7768%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25579: Lack of type adaptation in ArrayField querying/lookups

[Django]

#25579: Lack of type adaptation in ArrayField querying/lookups
-+-
 Reporter:  freshquiz|Owner:  freshquiz
 Type:  Bug  |   Status:  assigned
Component:  contrib.postgres |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  ArrayField query | Triage Stage:  Accepted
  lookup |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  0 => 1


Comment:

 Left comments for improvement on the PR. Please uncheck "patch needs
 improvement" when you update it. 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 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.f362e024c4086e37449b2aba5ca46b99%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25143: ArrayField should implement from_db_value()

[Django]

#25143: ArrayField should implement from_db_value()
-+-
 Reporter:  Odahi|Owner:  Tim
 |  Graham 
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 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 Tim Graham ):

 * status:  new => closed
 * owner:   => Tim Graham 
 * resolution:   => fixed


Comment:

 In [changeset:"2495023a4cae28f494d0a6172abfac3a47a0b816" 2495023]:
 {{{
 #!CommitTicketReference repository=""
 revision="2495023a4cae28f494d0a6172abfac3a47a0b816"
 Fixed #25143 -- Added ArrayField.from_db_value().

 Thanks Karan Lyons for contributing to the 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 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/063.014604f67b4b19babd9e8604d6a4839d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.