| Age | Commit message (Collapse) | Author |
|---|
|
for XML. Apparently we were carefully changing just the XML files to
use a single "-" to work around this. Enough already, just convert
all copyright year ranges to single "-" and have done with this.
svn path=/branches/tk705/; revision=6427
|
|
svn path=/branches/tk705/; revision=6426
|
|
understands Django's exotic metaclasses, which in turn allows us to
re-enable a number of pylint checks we had disabled. While we were at
this, stripped out a bunch of old pylint pragmas, then added back the
subset that were really needed. As usual with pylint, this turned up
a few real bugs along with an awful lot of noise.
svn path=/branches/tk705/; revision=6162
|
|
else.
svn path=/branches/tk705/; revision=6147
|
|
incorrectly coded UTF-8 in BLOB fields holding ASN.1 DER data. This
is wrong in so many ways that I don't even know where to start, but,
bottom line, forcing Latin1 here is just making MySQL 5.6+ revert to
the behavior in MySQL 5.5.
This is just a workaround. The real solution is probably to switch to
an SQL engine that's not quite such a kludge tower.
svn path=/branches/tk705/; revision=6146
|
|
svn path=/branches/tk705/; revision=6123
|
|
incomprehensible advance depreciation warnings for Django 1.9.
svn path=/branches/tk705/; revision=6100
|
|
particular programs (see #713).
svn path=/branches/tk705/; revision=6098
|
