#3646: ABSOLUTE_URL_OVERRIDES docs are inconsistent with how they actually work
---------------------------+------------------------------------------------
   Reporter:  ubernostrum  |                Owner:  adrian    
     Status:  new          |            Component:  Metasystem
    Version:  SVN          |           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:

 Of the two choices, we should prefer fixing the docs: use the lower-case
 version and point out that people must use the lower-case version.
 
 The {{{capitalize()}}} version won't work for a model called !MyModel.
 Camel- case class names is pretty common in Python (even PEP-8
 compatible).
 
 The ideal solution would be a third option: take the key and lower-case it
 before comparing to the module_name. Then people can use the real Python
 import path in the settings file and not have to worry about Django's
 slightly odd "real men don't use capital letters" approach to lower-casing
 every name in sight. Can't immediately see how to do that in just a line
 or two in {{{django. db.models.base.get_absolute_url()}}}, though.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/3646#comment:6>
Django Code <http://code.djangoproject.com/>
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 [email protected]
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to