> On 03 Dec 2015, at 17:04, Carl Meyer <[email protected]> wrote:
> 
>> I use Python 3.5, SQLite 3.9.2 and I can reproduce the crash on Django
>>> =1.8.4,<1.9.
> 
> This might be useful information to add to
> https://code.djangoproject.com/ticket/24080, if it's not already present
> there.
> 
> Does the version range you give imply that the issue goes away in Django
> 1.9, or just that you've never tried it there?

So, having ported my application to Django 1.9, I can say that the error is 
gone in Django 1.9. It happens in Django 1.8.X, X>=4.

I can’t test on Django 1.8.X, X<4, because the application needs #25160 fixed. 
I can’t test at all on Django < 1.8.

Another observation is that the error only appears *without* migrations, i.e. 
if the “migrations” directory doesn’t exist. It works for 1.8.X, X>=4 if proper 
migrations exists.

Also, the error only happens when `raise SkipTest` isn’t used correctly, as 
shown earlier in this thread.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/C0FD1C0A-C9F4-4586-8C9B-97D9CE91721F%40lophus.org.
For more options, visit https://groups.google.com/d/optout.

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to