[Sqlalchemy-tickets] Issue #3436: Supports set in addition to list/tuple in postgres ARRAY type (zzzeek/sqlalchemy)

[thiefmaster <iss...@bi...>]

New issue 3436: Supports set in addition to list/tuple in postgres ARRAY type
https://bitbucket.org/zzzeek/sqlalchemy/issue/3436/supports-set-in-addition-to-list-tuple-in

thiefmaster:

In some cases it would be useful to have a set on the python side, e.g. because you don't need/want duplicates and the set api is nicer to use in that case (as you won't have to worry about removing dupes).

Since there's already `as_tuple`, I'd deprecate this option and have a `python_type` kwarg instead that defaults to `list` but can be set to `tuple` or `set`, too. `as_tuple` and `python_type` would be mutually exclusive.