On Thu, Oct 7, 2010 at 9:42 AM, Jacob Kaplan-Moss wrote:
> You know, I really don't think this is a big enough deal to bother
> being completely picky about the deprecation policy here. It's a silly
> setting that should have been removed pre-open-source when we did the
> whole Django/Ellington sp
On Wed, Oct 6, 2010 at 10:30 PM, Russell Keith-Magee
wrote:
> Strictly, it needs to be put on a deprecation path [...]
You know, I really don't think this is a big enough deal to bother
being completely picky about the deprecation policy here. It's a silly
setting that should have been removed pr
On Thu, Oct 7, 2010 at 7:33 PM, Luke Plant wrote:
> On Thu, 2010-10-07 at 18:50 +0800, Russell Keith-Magee wrote:
>
>> The set of people that will be affected here are are all opt-in --
>> they've had to set COMMENTS_ALLOW_PROFANITIES=True -- so I would have
>> assumed that some subset will be hap
On Thu, 2010-10-07 at 18:50 +0800, Russell Keith-Magee wrote:
> The set of people that will be affected here are are all opt-in --
> they've had to set COMMENTS_ALLOW_PROFANITIES=True -- so I would have
> assumed that some subset will be happy with the default
> PROFANITIES_LIST as currently defin
On Thu, Oct 7, 2010 at 6:15 PM, Luke Plant wrote:
> On Thu, 2010-10-07 at 11:30 +0800, Russell Keith-Magee wrote:
>
>> Strictly, it needs to be put on a deprecation path, because it *is*
>> documented, in ref/settings.txt. So the earliest we can truly remove
>> it is in 1.5, after a PendingDepreca
On Thu, 2010-10-07 at 11:30 +0800, Russell Keith-Magee wrote:
> Strictly, it needs to be put on a deprecation path, because it *is*
> documented, in ref/settings.txt. So the earliest we can truly remove
> it is in 1.5, after a PendingDeprecationWarning in 1.3 and a full
> Warning in 1.4.
>
> Alon
Well dang! "Magic" just happened.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to
django-developers+unsubscr...@googlegr
On Thu, Oct 7, 2010 at 11:42 AM, Owen Nelson wrote:
> On Wed, Oct 6, 2010 at 11:30 PM, Russell Keith-Magee
> wrote:
>>
>> Strictly, it needs to be put on a deprecation path, because it *is*
>> documented, in ref/settings.txt. So the earliest we can truly remove
>> it is in 1.5, after a PendingDep
On Wed, Oct 6, 2010 at 11:30 PM, Russell Keith-Magee <
russ...@keith-magee.com> wrote:
>
> Strictly, it needs to be put on a deprecation path, because it *is*
> documented, in ref/settings.txt. So the earliest we can truly remove
> it is in 1.5, after a PendingDeprecationWarning in 1.3 and a full
>
On Thu, Oct 7, 2010 at 11:15 AM, Adrian Holovaty wrote:
> On Wed, Oct 6, 2010 at 10:09 PM, Owen Nelson wrote:
>> Moving forward, I'll be skipping the comment-specific setting and simply
>> setting PROFANITIES_LIST to (). Any chance we'll see the setting removed in
>> the near future?
>
> Yes, it
On Wed, Oct 6, 2010 at 10:09 PM, Owen Nelson wrote:
> Moving forward, I'll be skipping the comment-specific setting and simply
> setting PROFANITIES_LIST to (). Any chance we'll see the setting removed in
> the near future?
Yes, it's about time we got rid of this $&*@ thing!
(That was too easy.
So, I've been using django for about 2 years now. Last week was my first
time using django.contrib.comments. Needless to say, I was shocked when it
asked me to clean up my language during a late night coding binge (there may
have been drink involved). I searched the docs, unaware there was ever
12 matches
Mail list logo
