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 "unstable". Without going to great lengths, I don't think I can fix that and I don't want to was too much time on ancient Python versions... Iacopo, do you think this is good enough? Did you see issues in django CMS tests (py2) with tests being "unstable" (in the current version)? Jonas On Tuesday, August 30, 2016 at 11:14:15 AM UTC+9, Jonas Obrist wrote: > > 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, 1.9, 1.10 (Added 1.10) > > Hopefully this doesn't break everything (as it tends to do :D). > > I also tried to update django-better-test to 1.10 (and I got it to support > it), but travis-ci is being uncooperative so I had to delay the release. > > Jonas > -- Message URL: https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id Unsubscribe: send a message to [email protected] --- You received this message because you are subscribed to the Google Groups "django CMS developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/django-cms-developers/b095f127-0c7b-4d5c-82fa-88b71cdf54be%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
