Re: [Django] #9347: verbose_name option is missing in Model Field reference

[Django]

#9347: verbose_name option is missing in Model Field reference
+---
  Reporter:  marcoberi  | Owner:  timo
Status:  assigned   | Milestone:  post-1.0
 Component:  Documentation  |   Version:  1.0 
Resolution: |  Keywords:  
 Stage:  Ready for checkin  | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

  * stage:  Accepted => Ready for checkin

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9347: verbose_name option is missing in Model Field reference

[Django]

#9347: verbose_name option is missing in Model Field reference
+---
  Reporter:  marcoberi  | Owner:  timo
Status:  assigned   | Milestone:  post-1.0
 Component:  Documentation  |   Version:  1.0 
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * has_patch:  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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9347: verbose_name option is missing in Model Field reference

[Django]

#9347: verbose_name option is missing in Model Field reference
+---
  Reporter:  marcoberi  | Owner:  timo
Status:  assigned   | Milestone:  post-1.0
 Component:  Documentation  |   Version:  1.0 
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * owner:  nobody => timo
  * 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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9347: verbose_name option is missing in Model Field reference

[Django]

#9347: verbose_name option is missing in Model Field reference
+---
  Reporter:  marcoberi  | Owner:  nobody  
Status:  new| Milestone:  post-1.0
 Component:  Documentation  |   Version:  1.0 
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by seniorquico):

 Another vote for a fix. I'm new to Django, and the first place I went was
 http://docs.djangoproject.com/en/dev/ref/models/fields/. I was beginning
 to think it couldn't be done until I stumbled across this ticket.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9347: verbose_name option is missing in Model Field reference

[Django]

#9347: verbose_name option is missing in Model Field reference
+---
  Reporter:  marcoberi  | Owner:  nobody  
Status:  new| Milestone:  post-1.0
 Component:  Documentation  |   Version:  1.0 
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by yoz):

 Speaking as someone who just wasted half an hour looking for the
 functionality offered by verbose_name, and who pored through the model
 field reference multiple times, I strongly endorse this ticket.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9347: verbose_name option is missing in Model Field reference

[Django]

#9347: verbose_name option is missing in Model Field reference
+---
  Reporter:  marcoberi  | Owner:  nobody  
Status:  new| Milestone:  post-1.0
 Component:  Documentation  |   Version:  1.0 
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by ramiro):

 Karen,
 Replying to [comment:4 kmtracey]:
 > Any field can have a verbose_name specified.  Not sure why you think it
 is restricted to relationship fields?  The difference between specifying
 it for non-related and related is you ''may'' simply specify it as the
 first positional argument for any field that is not a !ForeignKey,
 !ManyToManyField or !OneToOneField; that is you are not required to use
 the verbose_name keyword.  But you certainly can.
 It' because the wording used here:
 http://docs.djangoproject.com/en/dev/topics/db/models/#verbose-field-names

 I know that, strictly speaking, that section doesn't say ''normal'' fields
 don't support `verbose_name` but it only mentions they support usage of
 the first positional argument and contrast them agains the
 ''relationship'' fields. I hadn't looked  up at the code that's why I
 wrote `AFAIK`.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9347: verbose_name option is missing in Model Field reference

[Django]

#9347: verbose_name option is missing in Model Field reference
+---
  Reporter:  marcoberi  | Owner:  nobody  
Status:  new| Milestone:  post-1.0
 Component:  Documentation  |   Version:  1.0 
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by kmtracey):

 Any field can have a verbose_name specified.  Not sure why you think it is
 restricted to relationship fields?  The difference between specifying it
 for non-related and related is you ''may'' simply specify it as the first
 positional argument for any field that is not a !ForeignKey,
 !ManyToManyField or !OneToOneField; that is you are not required to use
 the verbose_name keyword.  But you certainly can.  (The reason you cannot
 specify it as first positional for the others is that they require
 different first positional arguments, so for them you must use the
 verbose_name keyword if you want to specify it at all.)

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9347: verbose_name option is missing in Model Field reference

[Django]

#9347: verbose_name option is missing in Model Field reference
+---
  Reporter:  marcoberi  | Owner:  nobody  
Status:  new| Milestone:  post-1.0
 Component:  Documentation  |   Version:  1.0 
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by ramiro):

 Actually, AFAIK, ''normal'' field types do not have a `verbose_name`
 option (it's only set using the first positional parameter of the model
 field declaration) but relationship fields do.

 From the documentation location the OT suggests it seems he wants to add a
 blurb/link to the wrong place, if anything it should be added to the
 http://docs.djangoproject.com/en/dev/ref/models/fields/#module-
 django.db.models.fields.related section further down in the same document.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9347: verbose_name option is missing in Model Field reference

[Django]

#9347: verbose_name option is missing in Model Field reference
+---
  Reporter:  marcoberi  | Owner:  nobody  
Status:  new| Milestone:  post-1.0
 Component:  Documentation  |   Version:  1.0 
Resolution: |  Keywords:  
 Stage:  Accepted   | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by mtredinnick):

  * stage:  Design decision needed => Accepted

Comment:

 We can add a reference for this and then point to the current description.
 The reference section (`ref/` directory) isn't really a complete reference
 if it's missing options. We don't have to duplicate the description, since
 inter-file linking is possible.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9347: verbose_name option is missing in Model Field reference

[Django]

#9347: verbose_name option is missing in Model Field reference
-+--
  Reporter:  marcoberi   | Owner:  nobody  
Status:  new | Milestone:  post-1.0
 Component:  Documentation   |   Version:  1.0 
Resolution:  |  Keywords:  
 Stage:  Design decision needed  | Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by kmtracey):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Design decision needed
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 The verbose_name keyword argument for model fields is described in
 'Writing Models' here:

 http://docs.djangoproject.com/en/dev/topics/db/models/#verbose-field-names

 I do not know that we want to (or generally do?) document things in two
 places.  Someone more involved with the documentation structure needs to
 make that call.

-- 
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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---