Re: Pluggable encryption for django auth (design proposal)

On Mon, Feb 21, 2011 at 9:26 AM, Jacob Kaplan-Moss wrote: > On Mon, Feb 21, 2011 at 3:23 PM, poswald wrote: >> Russ, Carl, thanks for your feedback. Russ, I understand what you say >> about not wanting to adopt crypto code because of the additional >>

Re: CSRF Middleware/SSL/Firefox 3.6.8 bug

On Thu, Aug 26, 2010 at 10:23 AM, Mat Clayton wrote: > About to file this as a Bug in Trac but after some opinions first. > We are running django 1.2, and can't personally reproduce this bug, but some > of our users can do. We are using SSL and CSRF to protect our login pages,

Re: Deprecating cmemcache, adding pylibmc

On Sun, Feb 21, 2010 at 8:46 PM, Rajiv Makhijani wrote: > I recently implemented a custom caching backend to add support for pylibmc > on a large site due to issues with cmemcache. > > For the most part the 'pylibmc' APIs are the same as 'python-memcached' and > 'cmemcache'.

Re: Call for comment: #12624 Class based test runners

On Sat, Jan 16, 2010 at 6:26 AM, Russell Keith-Magee wrote: > Hi all, > > This is a quick call for comment on ticket #12624. > > This ticket proposes to make Django's test runner a class-based, > rather than function based operation. One thing:

Is a partial translation acceptable?

How do you guys feel about getting an incomplete translation for some locales? We might want to support some locales that Django doesn't have yet, but I'm trying not to overload our localizers with all the strings in Django (they're already sick of us). I thought that something like

Re: Adding an option to re-test only failed tests

On Tue, Sep 29, 2009 at 8:56 PM, Rob Madole wrote: > > I'll see if I can talk Jeff into adding what he's got as a start to > this.  It looks solid to me. > > Ticket and patches forthcoming... The nose test-runner that I'm currently using is at http://gist.github.com/197593.