Peewee

For all the winblows lusers out there, added an option to skip compilation of
the SQLite C extensions during installation. Set env var `NO_SQLITE=1` and run
`setup.py install` and you should be able to build without requiring SQLite.

[View commits](https://github.com/coleifer/peewee/compare/3.1.6...3.1.7)

* Added `rekey()` method to SqlCipher database for changing encryption key and
documentation for `set_passphrase()` method.
* Added `convert_values` parameter to `ArrayField` constructor, which will
cause the array values to be processed using the underlying data-type's
conversion logic.
* Fixed unreported bug using `TimestampField` with sub-second resolutions.
* Fixed bug where options were not being processed when calling `drop_table()`.
* Some fixes and improvements to `signals` extension.

[View commits](https://github.com/coleifer/peewee/compare/3.1.5...3.1.6)

Fixed Python 2/3 incompatibility with `itertools.izip_longest()`.

[View commits](https://github.com/coleifer/peewee/compare/3.1.4...3.1.5)

* Added `BigAutoField` to support 64-bit auto-incrementing primary keys.
* Use Peewee-compatible datetime serialization when exporting JSON from
a `DataSet`. Previously the JSON export used ISO-8601 by default. See 1536.
* Added `Database.batch_commit` helper to wrap iterators in chunked
transactions. See 1539 for discussion.

[View commits](https://github.com/coleifer/peewee/compare/3.1.3...3.1.4)

* Fixed issue where scope-specific settings were being updated in-place instead
of copied. 1534.
* Fixed bug where setting a `ForeignKeyField` did not add it to the model's
"dirty" fields list. 1530.
* Use pre-fetched data when using `prefetch()` with `ManyToManyField`. Thanks
to iBelieve for the patch. 1531.
* Use `JSON` data-type for SQLite `JSONField` instances.
* Add a `json_contains` function for use with SQLite `json1` extension.
* Various documentation updates and additions.

[View commits](https://github.com/coleifer/peewee/compare/3.1.2...3.1.3)

New behavior for INSERT queries with RETURNING clause

Investigating 1522, it occurred to me that INSERT queries with non-default
*RETURNING* clauses (postgres-only feature) should always return a cursor
object. Previously, if executing a single-row INSERT query, the last-inserted
row ID would be returned, regardless of what was specified by the RETURNING
clause.

This change only affects INSERT queries with non-default RETURNING clauses and
will cause a cursor to be returned, as opposed to the last-inserted row ID.

[View commits](https://github.com/coleifer/peewee/compare/3.1.1...3.1.2)