Re: [Django] #29458: Documentation incorrectly says Model._meta.get_field() uses related_name instead of related_query_name

[Django]

#29458: Documentation incorrectly says Model._meta.get_field() uses related_name
instead of related_query_name
---+
 Reporter:  Tomasz Knapik  |Owner:  Jeff
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  2.1
 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:"ddd9272c2e323b4e8937774425ee93ebebf8eeba" ddd9272c]:
 {{{
 #!CommitTicketReference repository=""
 revision="ddd9272c2e323b4e8937774425ee93ebebf8eeba"
 [2.1.x] Fixed #29458 -- Doc'd how related_query_name affects
 Model._meta.get_field().

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

Re: [Django] #29458: Documentation incorrectly says Model._meta.get_field() uses related_name instead of related_query_name

[Django]

#29458: Documentation incorrectly says Model._meta.get_field() uses related_name
instead of related_query_name
---+
 Reporter:  Tomasz Knapik  |Owner:  Jeff
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  2.1
 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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"2d6776ffe0b58f729f4372635b49a59da99ca206" 2d6776f]:
 {{{
 #!CommitTicketReference repository=""
 revision="2d6776ffe0b58f729f4372635b49a59da99ca206"
 Fixed #29458 -- Doc'd how related_query_name affects
 Model._meta.get_field().
 }}}

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

Re: [Django] #29458: Documentation incorrectly says Model._meta.get_field() uses related_name instead of related_query_name

[Django]

#29458: Documentation incorrectly says Model._meta.get_field() uses related_name
instead of related_query_name
---+
 Reporter:  Tomasz Knapik  |Owner:  Jeff
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  2.1
 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 Jeff):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/10105 #29458]

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

Re: [Django] #29458: Documentation incorrectly says Model._meta.get_field() uses related_name instead of related_query_name

[Django]

#29458: Documentation incorrectly says Model._meta.get_field() uses related_name
instead of related_query_name
---+
 Reporter:  Tomasz Knapik  |Owner:  Jeff
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  2.1
 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 Jeff):

 * owner:  nobody => Jeff
 * status:  new => assigned


Comment:

 I've confirmed the reported behavior and agree the docs seem misleading.
 I'll make a 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.c18de513e6b05f5d8508946d48c543d2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #29458: Documentation incorrectly says Model._meta.get_field() uses related_name instead of related_query_name (was: get_field uses related_query_name instead of related_name)

[Django]

#29458: Documentation incorrectly says Model._meta.get_field() uses related_name
instead of related_query_name
---+
 Reporter:  Tomasz Knapik  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  2.1
 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):

 * component:  Uncategorized => Documentation
 * stage:  Unreviewed => Accepted


Comment:

 I haven't investigated in detail but I imagine the documentation should be
 updated.

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