> On 12 May 2017, at 19:05, Marten Kenbeek <marten.k...@gmail.com> wrote: > > That's not quite right. Django has actually been using the `re.UNICODE` flag > since at least 1.0, so you'd have the same problem on Python 2.
Since 1.0 exactly; this behavior was introduced in https://github.com/django/django/commit/8c85ddf306e6d707e4bd521e7708509a3fb29bf1 <https://github.com/django/django/commit/8c85ddf306e6d707e4bd521e7708509a3fb29bf1>. Since it was hardly noticed in a decade, it can't be too much of a problem in practice... -- Aymeric. -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/E46EABDB-1BEE-407C-91DD-347506DE037D%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
