Re: [Django] #9530: COMMENTS_ALLOW_PROFANITIES not documented.

[Django]

#9530: COMMENTS_ALLOW_PROFANITIES not documented.
-+-
 Reporter:  Beetle_B |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Documentation|  Version:  1.0
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  comments profanity   | Triage Stage:
  lists  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timo):

 It's been removed in 1.8 along with `django.contrib.comments`.

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

Re: [Django] #9530: COMMENTS_ALLOW_PROFANITIES not documented.

[Django]

#9530: COMMENTS_ALLOW_PROFANITIES not documented.
-+-
 Reporter:  Beetle_B |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Documentation|  Version:  1.0
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  comments profanity   | Triage Stage:
  lists  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by RecNes):

 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 Do you really still thinking about removing profanity list from settings?
 It's still there but also not documented yet. And, it's getting confusion
 on use of this setting.

 Gosh! it's been 6 years passed and still I can see traces in 1.6. :)

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

Re: [Django] #9530: COMMENTS_ALLOW_PROFANITIES not documented.

[Django]

#9530: COMMENTS_ALLOW_PROFANITIES not documented.
+---
  Reporter:  Beetle_B   | Owner:  nobody  
Status:  closed | Milestone:  
 Component:  Documentation  |   Version:  1.0 
Resolution:  wontfix|  Keywords:  comments profanity lists
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by adrian):

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

Comment:

 I'd like to remove the profanity list as soon as we can do so in a
 backwards-incompatible way. With that in mind, we should leave
 {{{COMMENTS_ALLOW_PROFANITIES}}} undocumented.

-- 
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] #9530: COMMENTS_ALLOW_PROFANITIES not documented.

[Django]

#9530: COMMENTS_ALLOW_PROFANITIES not documented.
+---
  Reporter:  Beetle_B   | Owner:  nobody  
Status:  new| Milestone:  
 Component:  Documentation  |   Version:  1.0 
Resolution: |  Keywords:  comments profanity lists
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by Beetle_B):

 I don't know what the final decision was. I wasn't even aware a list was
 being distributed with 1.0.

 I guess my point was that if this is going to be removed altogether, then
 there's no need to document. But if they plan to keep the code there (and
 have users use their own list), then it needs to be documented.

-- 
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] #9530: COMMENTS_ALLOW_PROFANITIES not documented.

[Django]

#9530: COMMENTS_ALLOW_PROFANITIES not documented.
+---
  Reporter:  Beetle_B   | Owner:  nobody  
Status:  new| Milestone:  
 Component:  Documentation  |   Version:  1.0 
Resolution: |  Keywords:  comments profanity lists
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by thejaswi_puthraya):

  * keywords:  => comments profanity lists
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 As Adrian (one of the BDFL) notes in #8794 that we shouldn't be
 distributing profanity lists along with django. He also recommended that
 it be removed in the next version...so I am not sure if we should still
 document it.

-- 
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
-~--~~~~--~~--~--~---