it's last:
I don't know how to provide order of processing outside middlewares...
i stopped on this:
settings.py:
MIDDLEWARE_CLASSES = (
'django.middleware.common.CommonMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
Sorry for the wait. You should have access now. :)
On Tue, Dec 1, 2009 at 8:26 PM, SmileyChris wrote:
> I applied and pushed all but your final whitespace revision.
>
> When Tobias reads this thread again, I'm sure he'll give you commit.
> The fail_silently sounds good,
Hello all,
On Janaury 9-10 in Chicago we'll be holding a development sprint for
Django. This sprint will focus primarily on bugfixing for Django's
upcoming 1.2 release. No prior experience is needed, there'll be
plenty of people there to help you get started! More information can
be found
Russ,
I dont agree to the *it works* theory here - Ian rightly said 'If you
ask me,
anybody foolish enough to use a TextField as a primary key deserves
what they get' and you agreed 'Your comment about foolishness is
definitely correct '
Putting it in context, this is in the 'user control area'
On Tue, Dec 1, 2009 at 4:35 PM, Luke Plant wrote:
> I just converted some code, and the API seems good to me. I had one
> issue, which was the fact that I had some code which only had access
> to the User object, and not the request object, which had to be re-
> plumbed.
Latest patch, including fail_silently, is up for review:
http://code.djangoproject.com/attachment/ticket/4604/django-contrib-messages-e4da706e1152.diff
Cheers,
Tobias
2009/12/3 Tobias McNulty
> The simplest solution is to catch the exception in the generic views.
>>
On Thu, Dec 3, 2009 at 12:58 AM, Tobias McNulty wrote:
>
>
> On Tue, Dec 1, 2009 at 4:35 PM, Luke Plant wrote:
>>
>> I just converted some code, and the API seems good to me. I had one
>> issue, which was the fact that I had some code which only