[pkgsrc/trunk]: pkgsrc/databases/py-sqlalchemy py-sqlalchemy: updated to 1.2.16

[adam <adam%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/34d13a8f5372
branches:  trunk
changeset: 390004:34d13a8f5372
user:      adam <adam%pkgsrc.org@localhost>
date:      Tue Jan 15 11:51:27 2019 +0000

description:
py-sqlalchemy: updated to 1.2.16

1.2.16:
engine

[engine] [bug] Fixed a regression introduced in version 1.2 where a refactor of the SQLAlchemyError base exception class introduced an inappropriate coercion of a plain string message into Unicode 
under python 2k, which is not handled by the Python interpreter for characters outside of the platform?s encoding (typically ascii). The SQLAlchemyError class now passes a bytestring through under 
Py2K for __str__() as is the behavior of exception objects in general under Py2K, does a safe coercion to unicode utf-8 with backslash fallback for __unicode__(). For Py3K the message is typically 
unicode already, but if not is again safe-coerced with utf-8 with backslash fallback for the __str__() method.

sql

[sql] [bug] [mysql] [oracle] Fixed issue where the DDL emitted for DropTableComment, which will be used by an upcoming version of Alembic, was incorrect for the MySQL and Oracle databases.

postgresql

[postgresql] [bug] Fixed issue where a postgresql.ENUM or a custom domain present in a remote schema would not be recognized within column reflection if the name of the enum/domain or the name of the 
schema required quoting. A new parsing scheme now fully parses out quoted or non-quoted tokens including support for SQL-escaped quotes.

[postgresql] [bug] Fixed issue where multiple postgresql.ENUM objects referred to by the same MetaData object would fail to be created if multiple objects had the same name under different schema 
names. The internal memoization the PostgreSQL dialect uses to track if it has created a particular postgresql.ENUM in the database during a DDL creation sequence now takes schema name into account.

sqlite

[sqlite] [bug] Reflection of an index based on SQL expressions are now skipped with a warning, in the same way as that of the Postgresql dialect, where we currently do not support reflecting indexes 
that have SQL expressions within them. Previously, an index with columns of None were produced which would break tools like Alembic.

misc

Fixed issue in ?expanding IN? feature where using the same bound parameter name more than once in a query would lead to a KeyError within the process of rewriting the parameters in the query

diffstat:

 databases/py-sqlalchemy/Makefile |   4 ++--
 databases/py-sqlalchemy/distinfo |  10 +++++-----
 2 files changed, 7 insertions(+), 7 deletions(-)

diffs (27 lines):

diff -r 19273732e44a -r 34d13a8f5372 databases/py-sqlalchemy/Makefile
--- a/databases/py-sqlalchemy/Makefile  Tue Jan 15 11:48:24 2019 +0000
+++ b/databases/py-sqlalchemy/Makefile  Tue Jan 15 11:51:27 2019 +0000
@@ -1,6 +1,6 @@
-# $NetBSD: Makefile,v 1.47 2018/12/13 11:46:16 adam Exp $
+# $NetBSD: Makefile,v 1.48 2019/01/15 11:51:27 adam Exp $
 
-DISTNAME=      SQLAlchemy-1.2.15
+DISTNAME=      SQLAlchemy-1.2.16
 PKGNAME=       ${PYPKGPREFIX}-${DISTNAME:tl}
 CATEGORIES=    databases python
 MASTER_SITES=  ${MASTER_SITE_PYPI:=S/SQLAlchemy/}
diff -r 19273732e44a -r 34d13a8f5372 databases/py-sqlalchemy/distinfo
--- a/databases/py-sqlalchemy/distinfo  Tue Jan 15 11:48:24 2019 +0000
+++ b/databases/py-sqlalchemy/distinfo  Tue Jan 15 11:51:27 2019 +0000
@@ -1,6 +1,6 @@
-$NetBSD: distinfo,v 1.42 2018/12/13 11:46:16 adam Exp $
+$NetBSD: distinfo,v 1.43 2019/01/15 11:51:27 adam Exp $
 
-SHA1 (SQLAlchemy-1.2.15.tar.gz) = dd645321a887703b9be08434a73abb4041ae220f
-RMD160 (SQLAlchemy-1.2.15.tar.gz) = 7f9f90a5090a48c32a82c44d9a23f1321a7cc921
-SHA512 (SQLAlchemy-1.2.15.tar.gz) = 478583438b2e0f82a5dd1e295ae7a00b308763b669d01875d5e61f43127792ec1ad18929bff664a641a65eff685cb10ef880bf3f1334954720059019bceca7e7
-Size (SQLAlchemy-1.2.15.tar.gz) = 5645275 bytes
+SHA1 (SQLAlchemy-1.2.16.tar.gz) = a315ace39170c2d8eb989e07f47336f65a28ddd3
+RMD160 (SQLAlchemy-1.2.16.tar.gz) = 17a597e1225994494e11ecba9df0b13458683a33
+SHA512 (SQLAlchemy-1.2.16.tar.gz) = b80a6111a34495127ffe4dd0cb8ddc087b355c6fd891df5f829f6b1de3119dee5c6b181bc8dde9089c9a48a9e9ecbac52354bc2314989489f7a1e854fcbb535c
+Size (SQLAlchemy-1.2.16.tar.gz) = 5659983 bytes