Re: [GSoC 2012] Improved error reporting

2012-03-14 Thread Russell Keith-Magee
On 15/03/2012, at 1:23 PM, Boris Bobrov wrote: > Hi! > I'd like to participate in GSoC-2012 and the interesting task for me is [0]. > > What kind of plan would you expect from me? Should it be detailed ("I'll fix > error handling in part X by doing A") or it can be more general ("I'll fix > er

[GSoC 2012] Improved error reporting

2012-03-14 Thread Boris Bobrov
Hi! I'd like to participate in GSoC-2012 and the interesting task for me is [0]. What kind of plan would you expect from me? Should it be detailed ("I'll fix error handling in part X by doing A") or it can be more general ("I'll fix error handling in part X after reviewing A, B, C") or even move

ANN: Django 1.4 release candidate 2 issued

2012-03-14 Thread James Bennett
Subject line says it all, and details, as always, are on the weblog: https://www.djangoproject.com/weblog/2012/mar/14/14rc2/ -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroup

Re: authentication by email

2012-03-14 Thread Clay McClure
On Sun, Mar 11, 2012 at 4:39 AM, Clay McClure wrote: What you are really saying is this: being pragmatic means that we >> prioritise *your* immediate need above the need to keep the code and the >> docs maintainable, and above the need to maintain compatibility with >> existing installations. > >

Re: Making sure Web APIs built with Django don't have CSRF vulnerabilities.

2012-03-14 Thread Carl Meyer
Hi Tom, Thanks for raising this. On 03/14/2012 11:20 AM, Tom Christie wrote: [snip] > One idea to mitigating this in Django core that I've considered would be > introducing a '@csrf_defered' decorator, that would act like > '@csrf_exempt', but wrap request.session in a lazily evaluated > '@csrf_p

Making sure Web APIs built with Django don't have CSRF vulnerabilities.

2012-03-14 Thread Tom Christie
Hi all, This is a follow on to an issue that's been discussed on django-security. It's been suggested that it should be raised in this forum instead, so... Most of the time when building Web APIs with Django the right thing to do is to wrap API views in @csrf_exempt. Generally Web APIs shou

Re: Migrating to 1.4

2012-03-14 Thread Adrian Holovaty
On Wed, Mar 14, 2012 at 10:22 AM, Dan Fairs wrote: > - We have a custom template tag that derives from ExtendsNode, and overrides > get_parent > - We have a custom Library implementation that overrides inclusion_tag(), > which knows >   about our template lookup logic; it broke because the signatu

Re: Migrating to 1.4

2012-03-14 Thread Philippe Raoult
Thanks for the heads-up. My 50k python lines project is still running 1.2.7 + #12823. For some reason this patch can't seem to be commited, despite being a potiential data-loss. I'm still worrying about migrating to 1.3.1! Best regards, Philippe On 14 March 2012 16:22, Dan Fairs wrote: > Hi, >

Re: Migrating to 1.4

2012-03-14 Thread Dustin Farris
Wow, that's a big project! Thanks for sharing your success story. :) On Wednesday, March 14, 2012 11:22:07 AM UTC-4, Dan Fairs wrote: > > Hi, > > Since most people only ever report bugs, I wanted to report success in the > initial migration of a relatively large project (~35k lines of Python >

Migrating to 1.4

2012-03-14 Thread Dan Fairs
Hi, Since most people only ever report bugs, I wanted to report success in the initial migration of a relatively large project (~35k lines of Python application code, excluding comments and migrations, with ~43k lines of test code over ~2.5k tests) to Django 1.4 rc1. The production environment