- Original Message -
> But the stuff you run is not really benchmarking anything. As far as I
> know django benchmarks benchmark something like mostly DB creation and
> deletion, although that might differ between CPython and PyPy. How
> about running *actual* django benchmarks, instead
On Wed, Mar 7, 2012 at 2:36 PM, Vinay Sajip wrote:
> Armin Ronacher active-4.com> writes:
>
>> What are you trying to argue? That the overall Django testsuite does
>> not do a lot of string processing, less processing with native strings?
>>
>> I'm surprised you see a difference at all over the
On Thu, Mar 8, 2012 at 8:36 AM, Vinay Sajip wrote:
> Anyway, it doesn't really
> matter now, since the latest version of the PEP no longer mentions those
> figures.
Indeed, I deliberately removed the part about performance concerns,
since I considered it a distraction from what I see as the hear
Armin Ronacher active-4.com> writes:
> What are you trying to argue? That the overall Django testsuite does
> not do a lot of string processing, less processing with native strings?
>
> I'm surprised you see a difference at all over the whole Django
> testsuite and I wonder why you get a slowdo
Hi,
On 3/3/12 2:28 AM, Vinay Sajip wrote:
> So, looking at a large project in a relevant problem domain, unicode_literals
> and native string markers would appear not to adversely impact readability or
> performance.
What are you trying to argue? That the overall Django testsuite does
not do a lo
