Re: Django Oracle backend vs. numbers

2012-08-30 Thread Shai Berger
Hi Ian, Jacob, Anssi and all, Thanks for the quick and positive responses. On Wednesday 29 August 2012, Ian Kelly wrote: >https://github.com/ikelly/django/commit/086f502a1c2acb9db27531f7df78cb9df9ab83bd > > Shai, if you would be willing to try this patch, I'd like to hear your > results. Please

Re: Python 3: should we apply unicode_literals everywhere?

2012-08-30 Thread Felipe Prenholato
Here at PDG (Brazil) we are migrating our software to Djang 1.4 and already using unicode_literals. I can count in my fingers places that I needed to use 'b' for byte code string (most on settings.py). In my experience, maintain byte code strings isn't that hard and we should than go to option 2.

Re: GSoC Check-in: Security Enhancements

2012-08-30 Thread Rohan Jain
Hi, Ref Merging Centralized Tokenization. I found out that some tests for sessions are failing with it. Stupidly, I didn't have sessions in my test subset for tokenization. Anyway, I'll try to get it fixed and write some tests for tokens in next few days. -- Thanks Rohan On 10:50 +0100 / 21 Aug,

RawQuerySet as subquery when used with an __in filter

2012-08-30 Thread Alex Hill
Hi, and thanks for making Django. At the moment, when passing a RawQuerySet to an __in filter, the raw query is evaluated and the result passed as a parameter to the filter's SQL. It would be nice to have the option of using the raw SQL in a subquery instead, for performance reasons. I think i

Re: Yak shaving the test framework on the way to pluggable user models (#3011)

2012-08-30 Thread Roger Barnes
On Wednesday, August 29, 2012 6:04:09 PM UTC+10, Alex Ogier wrote: > > On Wed, Aug 29, 2012 at 3:44 AM, Russell Keith-Magee > > wrote: > > > > I suppose you could see it as a semantic nuance. However, to my mind, > > there is a different. A skipped test is something that could -- or > > even *

Re: Django Oracle backend vs. numbers

2012-08-30 Thread Anssi Kääriäinen
On 29 elo, 22:18, Ian Kelly wrote: > There's another option that also hasn't been implemented, because it > would mean dropping support for cx_Oracle versions older than 5.0.1. > Perhaps the time has come to do that (I note that the oldest binary > still listed at the cx_Oracle website is 5.1).  T