Thanks for the clarification; I'd say that the cms did not experience any side
effect so far, but I'll apply --vanilla anywya
Thanks!
On 3 September 2016 06:24:53 CEST, Jonas Obrist wrote:
>The old versions will suffer the same issues. This is not something
>newly
Il 02/09/2016 10:45, Jonas Obrist ha scritto:
> Managed to get the tests to work reliably (on Py 3.4 and higher).
> See https://github.com/ojii/django-better-test/pull/9
>
> But had to remove Django 1.6 support (don't think too many people will
> get upset about this) and Py 2.7/3.3 are now
Il 30/08/2016 11:19, Jonas Obrist ha scritto:
> Iacopo, please note that I've not released a better-test update yet, so
> my Dj1.10 compat changes are
> on https://github.com/ojii/django-better-test/tree/dj-1.10. Good number
> of tests failing though I have yet to reproduce
> it
Iacopo, please note that I've not released a better-test update yet, so my
Dj1.10 compat changes are on
https://github.com/ojii/django-better-test/tree/dj-1.10. Good number of
tests failing though I have yet to reproduce it
https://travis-ci.org/ojii/django-better-test. I should have time again
Il 30/08/2016 04:14, Jonas Obrist ha scritto:
> Hi everyone,
>
> Over the weekend at PyCon Malaysia I've updated django-classy-tags and
> django-sekizai to 0.8.0 and 0.10.0 respectively.
>
> Both releases only changed Python/Django compatibility.
>
> Both now support:
>
> - Python 2.7, 3.3,
Awesome job man!
--
Message URL:
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to
django-cms-developers+unsubscr...@googlegroups.com
---
You received this message because you are subscribed to the Google Groups
"django CMS developers"
Hi everyone,
Over the weekend at PyCon Malaysia I've updated django-classy-tags and
django-sekizai to 0.8.0 and 0.10.0 respectively.
Both releases only changed Python/Django compatibility.
Both now support:
- Python 2.7, 3.3, 3.4 and 3.5 (dropped 2.6)
- Django 1.3, 1.4, 1.5, 1.6, 1.7, 1.8,