available or behaves differently in PyPy. Is it
>worth
>adding PyPy to our continuous integration so we can proactively address
>
>these issues?
>
>(We can't test with pypy3 since that's based on Python 3.2 which we've
>dropped support for in Django 1.9.)
>
>Recent tickets:
>
it running on the CI reasonably easily I see no reason why
>> not.
>>
>> On 2 December 2015 at 16:46, Tim Graham <timog...@gmail.com> wrote:
>>
>>> Once in a while, we get a ticket about failures when running the Django
>>> test suite on PyPy. Some
get a ticket about failures when running the Django
>> test suite on PyPy. Sometimes they are bugs in PyPy, other times we use
>> something that's not available or behaves differently in PyPy. Is it worth
>> adding PyPy to our continuous integration so we can proactively address
>
times we use
> something that's not available or behaves differently in PyPy. Is it worth
> adding PyPy to our continuous integration so we can proactively address
> these issues?
>
> (We can't test with pypy3 since that's based on Python 3.2 which we've
> dropped support for in D
Once in a while, we get a ticket about failures when running the Django
test suite on PyPy. Sometimes they are bugs in PyPy, other times we use
something that's not available or behaves differently in PyPy. Is it worth
adding PyPy to our continuous integration so we can proactively address
