Re: [Django] #29270: KeyError if using 'password' as readonly_fields in UserAdmin

[Django]

#29270: KeyError if using 'password' as readonly_fields in UserAdmin
--+---
 Reporter:  Malte Gerth   |Owner:  Malte Gerth
 Type:  Bug   |   Status:  assigned
Component:  contrib.auth  |  Version:  2.0
 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 Malte Gerth):

 * status:  new => assigned
 * owner:  nobody => Malte Gerth
 * easy:  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 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.0a3df985a66eafc26229c6f711eddd67%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #27936: Add some clarifications to "Spanning multi-valued relationships"

[Django]

#27936: Add some clarifications to "Spanning multi-valued relationships"
--+
 Reporter:  Thomas Güttler|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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 Simon Charette):

 * cc: Simon Charette (added)
 * version:  1.10 => master


Comment:

 Given how often the multi-valued `filter()` chaining behavior is reported
 as a bug I think this might be worth a shot.

 I'm not a big fan of diagrams either and I think a simplified shell
 session would be a good step forward. I guess mixing both is also an
 option.

 If we really want to go with graphs I'd suggest we use the [http://www
 .sphinx-doc.org/en/master/ext/graphviz.html#module-sphinx.ext.graphviz the
 Graphiz extension] which makes it easy to maintain, generate SVGs, and
 should be flexible enough to express the previously mentioned ASCII graph.

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

Re: [Django] #29271: Chaining Filters on a Reverse Foreign Key Produces Multiple Joins

[Django]

#29271: Chaining Filters on a Reverse Foreign Key Produces Multiple Joins
-+-
 Reporter:  Michael MacIntosh|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  filter chain | Triage Stage:  Accepted
  reverse foreign key|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Simon Charette):

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


Comment:

 This is expected behavior as per
 [https://docs.djangoproject.com/en/dev/topics/db/queries/#spanning-multi-
 valued-relationships spanning multi-valued relationships] as `beta` is a
 reverse `ForeignKey` and thus multi-valued.

 I'm not sure how we could give more visibility to this part of the
 documentation as this keeps being reported as a bug given how unintuitive
 it is. Maybe this could be mentioned in the
 [https://docs.djangoproject.com/en/dev/ref/models/querysets/#filter
 filter()] reference documentation?

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

Re: [Django] #29271: Chaining Filters on a Reverse Foreign Key Produces Multiple Joins

[Django]

#29271: Chaining Filters on a Reverse Foreign Key Produces Multiple Joins
-+-
 Reporter:  Michael MacIntosh|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  filter chain | Triage Stage:  Accepted
  reverse foreign key|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 Is this really unexpected behavior? Duplicate of #16554 (closed as
 invalid)?

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

Re: [Django] #27161: TypedChoiceField fails to validate properly when used with ArrayField

[Django]

#27161: TypedChoiceField fails to validate properly when used with ArrayField
-+-
 Reporter:  Roman Karpovich  |Owner:  Rômulo
 |  Rosa Furtado
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  TypedChoiceField | 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):

 No. Per our [https://docs.djangoproject.com/en/dev/internals/release-
 process/#supported-versions supported versions policy], 1.11 is only
 receiving data loss and security fixes.

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

Re: [Django] #29271: Chaining Filters on a Reverse Foreign Key Produces Multiple Joins

[Django]

#29271: Chaining Filters on a Reverse Foreign Key Produces Multiple Joins
-+-
 Reporter:  Michael MacIntosh|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  filter chain | Triage Stage:  Accepted
  reverse foreign key|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Andrew Standley):

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

[Django] #29271: Chaining Filters on a Reverse Foreign Key Produces Multiple Joins

[Django]

#29271: Chaining Filters on a Reverse Foreign Key Produces Multiple Joins
-+-
   Reporter:  Michael|  Owner:  nobody
  MacIntosh  |
   Type:  Bug| Status:  new
  Component:  Database   |Version:  2.0
  layer (models, ORM)|   Keywords:  filter chain
   Severity:  Normal |  reverse foreign key
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 When you perform multiple filters on a queryset on a reverse foreign key,
 it produces duplicate joins, which causes the results to multiply.  If
 instead of chaining the filters, you put both of the filters in one
 filter, you do not get duplicate results.

 You also get this behavior if you repeat the same filter.

 This also applies to Q objects that are used in chain filters that
 reference values across reverse foreign keys as well.

 Example Models:

 {{{
 class Alpha(models.Model):
 field = models.CharField(max_length=100)

 class Beta(models.Model):
 field = models.CharField(max_length=100)
 data = models.CharField(max_length=100)
 alpha = models.ForeignKey(Alpha, on_delete=models.CASCADE)
 }}}
 Example Data:

 {{{
 Alpha.objects.all().delete()
 Beta.objects.all().delete()
 alpha = Alpha(field="alpha_text")
 alpha.save()
 beta = Beta(field="beta_text", data="data1", alpha=alpha)
 beta.save()
 beta = Beta(field="beta_text", data="data2", alpha=alpha)
 beta.save()
 }}}

 Example Output:
 {{{
 >>> Alpha.objects.filter(beta__field="beta_text", beta__data="data1")
 ]>
 >>>
 Alpha.objects.filter(beta__field="beta_text").filter(beta__data="data1")
 , ]>
 }}}

 Formatted SQL of the first query (expected):

 {{{
 SELECT "test_app_alpha"."id",
"test_app_alpha"."field"
 FROM   "test_app_alpha"
INNER JOIN "test_app_beta"
ON ( "test_app_alpha"."id" = "test_app_beta"."alpha_id" )
 WHERE  ( "test_app_beta"."field" = beta_text
  AND "test_app_beta"."data" = data1 )
 }}}
 Formatted SQL of the second query (bug)

 {{{
 SELECT "test_app_alpha"."id",
"test_app_alpha"."field"
 FROM   "test_app_alpha"
INNER JOIN "test_app_beta"
ON ( "test_app_alpha"."id" = "test_app_beta"."alpha_id" )
INNER JOIN "test_app_beta" T3
ON ( "test_app_alpha"."id" = T3."alpha_id" )
 WHERE  ( "test_app_beta"."field" = beta_text
  AND T3."data" = data1 )
 }}}

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

Re: [Django] #27161: TypedChoiceField fails to validate properly when used with ArrayField

[Django]

#27161: TypedChoiceField fails to validate properly when used with ArrayField
-+-
 Reporter:  Roman Karpovich  |Owner:  Rômulo
 |  Rosa Furtado
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  TypedChoiceField | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by José Jorge Lorenzo Vila):

 Any plan to port this to django 1.X? 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.1327c38bc2b038ea7e3d757dbccdca57%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #28919: Add support for Common Table Expression (CTE) queries

[Django]

#28919: Add support for Common Table Expression (CTE) queries
-+-
 Reporter:  Daniel Miller|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  QuerySet.extra   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by pwfff):

 I have a PR here, but it's incomplete in some ways:
 https://github.com/dimagi/django-cte/pull/1
 I could use some help from someone more familiar with the Query object and
 how it handles joins/aliases.

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

Re: [Django] #29266: Cannot perform schema migrations without downtime using MySQL in strict mode

[Django]

#29266: Cannot perform schema migrations without downtime using MySQL in strict
mode
-+-
 Reporter:  Paul Tiplady |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  2.0
  (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
-+-
Changes (by Paul Tiplady):

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


Comment:

 Thanks for the link -- I'm happy to carry on the discussion in that
 issue/thread.

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

Re: [Django] #470: Add Field.db_default for defining database defaults

[Django]

#470: Add Field.db_default for defining database defaults
-+-
 Reporter:  jws  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  normal   |   Resolution:
 Keywords:  sql schema   | 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):

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


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

Re: [Django] #29266: Cannot perform schema migrations without downtime using MySQL in strict mode

[Django]

#29266: Cannot perform schema migrations without downtime using MySQL in strict
mode
-+-
 Reporter:  Paul Tiplady |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 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 Tim Graham):

 You can read #470 for the historical "wontfix" decision regarding database
 defaults. I just reopened that ticket in light of the discussion linked to
 in comment 17. Can we close this ticket in light of that?

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

Re: [Django] #470: Add Field.db_default for defining database defaults (was: [patch] "default" values should be expressed in SQL schema)

[Django]

#470: Add Field.db_default for defining database defaults
-+-
 Reporter:  jws  |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  normal   |   Resolution:  wontfix
 Keywords:  sql schema   | 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):

 * needs_better_patch:  1 => 0
 * has_patch:  1 => 0
 * type:  enhancement => New feature
 * stage:  Design decision needed => Accepted


Comment:

 Reopening as per the mailing list discussion in the previous comment.

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

Re: [Django] #29245: ForeignKeyField Renaming leads Remove and AddField instead of RenameField Migration

[Django]

#29245: ForeignKeyField Renaming leads Remove and AddField instead of 
RenameField
Migration
-+-
 Reporter:  Taqi Abbas   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  ForeignKey,  | Triage Stage:  Accepted
  RenameField, db_column |
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:"2156565b5bac2e6f503ad4841e2b6ed44e4de656" 2156565b]:
 {{{
 #!CommitTicketReference repository=""
 revision="2156565b5bac2e6f503ad4841e2b6ed44e4de656"
 Fixed #29245 -- Made autodetector treat field renames + db_column addition
 as RenameField.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To 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.00070b83df68bb6f6620543332a0c922%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29268: Support passing content_type=None to test.Client.post() to get the default value

[Django]

#29268: Support passing content_type=None to test.Client.post() to get the 
default
value
--+
 Reporter:  Chris Jerdonek|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  Version:  2.0
 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 Chris Jerdonek):

 Oh, good observation. I didn't examine the other methods. Yes, I do.

 Generally, I've found this type of style / pattern helpful anywhere an API
 has a default value. Perhaps other areas of Django could use a similar
 treatment. Might it be a candidate for the
 [https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
 /coding-style/ style guide]?

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

Re: [Django] #29265: Docs about static files should explain benefits of using {% static %} template tag

[Django]

#29265: Docs about static files should explain benefits of using {% static %}
template tag
--+
 Reporter:  Ryan Govostes |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  2.0
 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:"ba5f24ea6491780bb245ed6f0e5f015f4defffe9" ba5f24e]:
 {{{
 #!CommitTicketReference repository=""
 revision="ba5f24ea6491780bb245ed6f0e5f015f4defffe9"
 Fixed #29265 -- Removed the suggestion to hardcode static URLs.
 }}}

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

Re: [Django] #29265: Docs about static files should explain benefits of using {% static %} template tag

[Django]

#29265: Docs about static files should explain benefits of using {% static %}
template tag
--+
 Reporter:  Ryan Govostes |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  2.0
 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:"a3007ecf3541ab319892809cf5ea7d7487667ef0" a3007ecf]:
 {{{
 #!CommitTicketReference repository=""
 revision="a3007ecf3541ab319892809cf5ea7d7487667ef0"
 [2.0.x] Fixed #29265 -- Removed the suggestion to hardcode static URLs.

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

Re: [Django] #29270: KeyError if using 'password' as readonly_fields in UserAdmin

[Django]

#29270: KeyError if using 'password' as readonly_fields in UserAdmin
--+
 Reporter:  Malte Gerth   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  2.0
 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


Comment:

 `.keys()` isn't needed, otherwise the fix looks reasonable. A test goes in
 `tests/auth_tests/test_forms.py` -- can you offer a pull request?

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

Re: [Django] #29265: Docs about static files should explain benefits of using {% static %} template tag

[Django]

#29265: Docs about static files should explain benefits of using {% static %}
template tag
--+
 Reporter:  Ryan Govostes |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  2.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 Tim Graham):

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


Comment:

 I agree there's no reason to mention hardcoding URLs.
 [https://github.com/django/django/pull/9831 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.5009e337f39edc0d6d988e7079273e11%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29148: Explain how to use QuerySet.get_or_create() with Q objects

[Django]

#29148: Explain how to use QuerySet.get_or_create() with Q objects
---+---
 Reporter:  Mike Lissner   |Owner:  Dhruv Singh
 Type:  New feature|   Status:  closed
Component:  Documentation  |  Version:  2.0
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  1  |UI/UX:  0
---+---
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"34c522283710c3866833134ddf1a397da03999e8" 34c52228]:
 {{{
 #!CommitTicketReference repository=""
 revision="34c522283710c3866833134ddf1a397da03999e8"
 Fixed #29148 -- Doc'd how to use get_or_create() with Q objects.
 }}}

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

Re: [Django] #29258: Add an error message when passing an authentication backend class to login()'s backend argument where a string is expected

[Django]

#29258: Add an error message when passing an authentication backend class to
login()'s backend argument where a string is expected
-+-
 Reporter:  Ryan Govostes|Owner:  Abeer
 Type:   |  Upadhyay
  Cleanup/optimization   |   Status:  closed
Component:  contrib.auth |  Version:  2.0
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"1bf4646f9133f26547a0dccf2f8a4526d85f2ab3" 1bf4646f]:
 {{{
 #!CommitTicketReference repository=""
 revision="1bf4646f9133f26547a0dccf2f8a4526d85f2ab3"
 Fixed #29258 -- Added type checking for login()'s backend argument.
 }}}

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

Re: [Django] #29268: Support passing content_type=None to test.Client.post() to get the default value

[Django]

#29268: Support passing content_type=None to test.Client.post() to get the 
default
value
--+
 Reporter:  Chris Jerdonek|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Testing framework |  Version:  2.0
 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):

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


Comment:

 Should the same design be used for the other HTTP methods that have
 `content_type='application/octet-stream'`?

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

Re: [Django] #29270: KeyError if using 'password' as readonly_fields in UserAdmin

[Django]

#29270: KeyError if using 'password' as readonly_fields in UserAdmin
--+--
 Reporter:  Malte Gerth   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  2.0
 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 Malte Gerth):

 This should fix the issue for now:
 {{{
 class UserChangeForm(forms.ModelForm):
 # ...
 def __init__(self, *args, **kwargs):
 super().__init__(*args, **kwargs)
 if 'password' in self.fields.keys():
 self.fields['password'].help_text =
 self.fields['password'].help_text.format('../password/')
 # ...
 }}}

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

[Django] #29270: KeyError if using 'password' as readonly_fields in UserAdmin

[Django]

#29270: KeyError if using 'password' as readonly_fields in UserAdmin
---+
   Reporter:  Jan Malte Gerth  |  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  contrib.auth |Version:  2.0
   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|
---+
 If 'password' is added as readonly_field in UserAdmin, a KeyError is
 thrown, as the UserChangeForm expects a password field to exists.


 {{{
 from django.contrib.auth.admin import UserAdmin as BaseUserAdmin

 class UserAdmin(BaseUserAdmin):
 readonly_fields = ['username', 'password']

 admin.site.register(User, UserAdmin)
 }}}


 {{{
 class UserChangeForm(forms.ModelForm):
 # ...
 def __init__(self, *args, **kwargs):
 super().__init__(*args, **kwargs)
 self.fields['password'].help_text =
 self.fields['password'].help_text.format('../password/')
 # ...
 }}}

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

Re: [Django] #29267: Refactor ModelForm to support separate fields

[Django]

#29267: Refactor ModelForm to support separate fields
---+--
 Reporter:  Victor Porton  |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Forms  |  Version:  2.0
 Severity:  Normal |   Resolution:  wontfix
 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 Jani Tiainen):

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


Comment:

 Nothing prevents you to use even multiple modelforms within single HTML
 form.

 If you need help with using Django in such a case, either consult #django
 IRC channel on Freenode or Django user group on google groups.

 Closing as won't fix.

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

Re: [Django] #29269: django inspectdb with windows

[Django]

#29269: django inspectdb with windows
---+--
 Reporter:  Balaraju   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Migrations |  Version:  1.11
 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 felixxm):

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


Comment:

 Trac is not the best place to look for support. Please use #django IRC
 channel or
 [https://groups.google.com/forum/?utm_source=digest_medium=email#!forum
 /django-users Django users] group, and reopen this ticket if you confirm
 an issue in Django.

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

[Django] #29269: django inspectdb with windows

[Django]

#29269: django inspectdb with windows
-+
   Reporter:  Balaraju   |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Migrations |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  |
-+
 I tried to integrate django project with legacy db(i tried mysql)  in
 windows environment but it is now working .I am using django 1.11

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

Re: [Django] #25590: Allow fields to set join class

[Django]

#25590: Allow fields to set join class
-+-
 Reporter:  Anssi Kääriäinen |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  duplicate
 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 Josh Smeaton):

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


Comment:

 Closing in favour of: https://code.djangoproject.com/ticket/29262

 Can undo the close if you think this should remain open.

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

Re: [Django] #26426: Add a way to customize a QuerySet's joins

[Django]

#26426: Add a way to customize a QuerySet's joins
-+-
 Reporter:  Charlie DeTar|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  QuerySet.extra   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Josh Smeaton):

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


Comment:

 This specific issue has been fixed with the addition of Exists
 expressions: https://docs.djangoproject.com/en/2.0/ref/models/expressions
 /#exists-subqueries

 The more general problem of supporting custom joins is:
 https://code.djangoproject.com/ticket/29262

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

Re: [Django] #29262: Custom Left Outer Join in Queries

[Django]

#29262: Custom Left Outer Join in Queries
-+-
 Reporter:  Sassan Haradji   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  2.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM Join | 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 Smeaton):

 I've begun a discussion on the mailing list:
 https://groups.google.com/forum/#!topic/django-developers/2ITfPZlbsao

 Please add your example to that thread if it's different to any already
 listed there.

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

Re: [Django] #29262: Custom Left Outer Join in Queries

[Django]

#29262: Custom Left Outer Join in Queries
-+-
 Reporter:  Sassan Haradji   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  ORM Join | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Josh Smeaton):

 * version:  2.0 =>
 * 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 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.84c63196de7fcb25f1563e4abd45bdb0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.