I guess, my statement doesn't apply if FILE_CHARSET only affects Django
text files, so disregard. My point was that non-UTF data is still actively
used despite the fact that "the whole world moved to Unicode".
--
You received this message because you are subscribed to the Google Groups
"Django
Some Russian companies still store their old data (in databases and/or
files) in KOI8-R. I'm not sure how many of them may be using Django, but I
personally worked for a company in 2014-2015, that maintained a huge
database of articles stored in KOI8-R. I can assume that, similarly, KOI8-U
may
Okay, this seems to produce TypeError in Django 2.0. See here:
https://code.djangoproject.com/ticket/22550
--
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
I can confirm this issue on Django 1.11.15 (Python 3.4.3, MySQL 5.5.61).
Calling 'last()' on a slice produces wrong result:
>>> News.objects.all().order_by('id')[:5].values('id')
>>> News.objects.all().order_by('id')[:5][4].id
5
>>> #But calling 'last' gives us wrong id:
>>> News.objects.all()
I outlined the problem of parent domain cookies included in Django's error
reports, which may be a problem due to GDPR.
There's a ticket in the Django bugtracker:
https://code.djangoproject.com/ticket/29714
And a discussion in the 'developers'
group: https://groups.google.com/forum/#!topic/dj
