I believe Adam is (or is planning..) writing a DB backend that includes
MySQL and MariaDB. Adam, did I remember correctly? If so, are you going to
suggest adding this new backend to core as a replacement? Mads, perhaps you
can help with this effort?
Regards,
On Tuesday, 15 November 2016 08:44:
I wouldn't spend too much energy about Python 2.7 stuff. Let the
workarounds in place, and just wait for Python 2 to die. I don't see the
point in forcing people of stable Debian-based distributions to install a
custom Python for 1.11.
--
You received this message because you are subscribed to
Well, I certainly agree with the intent... especially, as you say, for
LTS users who effectively cement themselves to a version for the long haul.
Might as well remind them there are security updates in things other
than OpenSSL, Java, and Django :)
--
C
On 15/11/16 09:49, Tim Graham wrote:
Hi,
I was wondering if Django could or should nudge Python 2 users toward the
latest stable release of 2.7.x? For example, we could require at least
2.7.8 by removing the fallback pbkdf2() implementation in
django.utils.crypto [0]. I guess part of my feeling is that if you're
running 1.11 LTS
Hi,
I got interest in contributing to Django. I started working on a bigger
ticket than the smaller contributions I've previously made.
Adam Chainz pointed out that MariaDB will include support for window
expressions (#26608) from 10.2. I asked on #django-dev what the official
policy for MariaDB