#9530 closed Uncategorized (wontfix)
COMMENTS_ALLOW_PROFANITIES not documented.
| Reported by: | Beetle_B | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 1.0 |
| Severity: | Normal | Keywords: | comments profanity lists |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I saw this while browsing the contrib.comments code.
It's not documented...
Change History (5)
comment:1 by , 16 years ago
| Keywords: | comments profanity lists added |
|---|
comment:2 by , 16 years ago
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.
comment:3 by , 15 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
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.
comment:4 by , 10 years ago
| Easy pickings: | unset |
|---|---|
| Severity: | → Normal |
| Type: | → Uncategorized |
| UI/UX: | unset |
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. :)
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.