On Tue, Oct 19, 2010 at 10:29 AM, Will Hardy wrote:
> Whilst I agree that messing with contrib.auth is likely to break
> something and create more work, I think it would be good for Django if
> everyone in the Django community went and needlessly ported their real
> world views to CBV, to expose a
Whilst I agree that messing with contrib.auth is likely to break
something and create more work, I think it would be good for Django if
everyone in the Django community went and needlessly ported their real
world views to CBV, to expose any deficiencies in the framework before
release.
Even if the
2010/10/18 Łukasz Rekucki :
> Somehow related, I was wondering today, would it be a good idea to try
> to rewrite contrib.auth views in terms of CBV, so that other parts of
> Django could benefit.
I'm not particularly clear on what other parts would benefit -- fill me in?
In general, I frown on r
On 19 October 2010 01:17, Gabriel Hurley wrote:
> I got my first real taste of the new API today by thoroughly proofing
> the docs for class-based views. I just wanted to say that there's some
> great stuff in there, and I give a big thanks to everyone who
> contributed! I'm really looking forward
I got my first real taste of the new API today by thoroughly proofing
the docs for class-based views. I just wanted to say that there's some
great stuff in there, and I give a big thanks to everyone who
contributed! I'm really looking forward to using the new class-based
views ASAP.
Thanks!
-
