Lmdb

* Added Environment.max_key_size(), Environment.max_readers().

* CFFI now raises the correct Error subclass associated with an MDB_* return
code.

* Numerous CFFI vs. CPython behavioural inconsistencies have been fixed.

* An endless variety of Unicode related 2.x/3.x/CPython/CFFI fixes were made.

* LMDB 0.9.10 is now bundled, along with some extra fixes from Git.

* Added Environment(meminit=...) option.

* Added support for Environment(..., readahead=False).

* LMDB 0.9.9 is now bundled.

* Many Python 2.5 and 3.x fixes were made. Future changes are automatically
tested via Travis CI <https://travis-ci.org/dw/py-lmdb>.

* When multiple cursors exist, and one cursor performs a mutation,
remaining cursors may have returned corrupt results via key(), value(),
or item(). Mutations are now explicitly tracked and cause the cursor's
data to be refreshed in this case.

* setup.py was adjusted to ensure the distutils default of '-DNDEBUG' is never
defined while building LMDB. This caused many important checks in the engine
to be disabled.

* The old 'transactionless' API was removed. A future version may support the
same API, but the implementation will be different.

* Transaction.pop() and Cursor.pop() helpers added, to complement
Transaction.replace() and Cursor.replace().

engineering) branch.

* CPython previously lacked a Cursor.close() method. Problem was noticed by
Jos Vos.

* Several memory leaks affecting the CFFI implementation when running on
CPython were fixed, apparent only when repeatedly opening and discarding a
large number of environments. Noticed by Jos Vos.

* The CPython extension previously did not support weakrefs on Environment
objects, and the implementation for Transaction objects was flawed. The
extension now correctly invalidates weakrefs during deallocation.

* Both variants now try to avoid taking page faults with the GIL held,
accomplished by touching one byte of every page in a value during reads.
This does not guarantee faults will never occur with the GIL held, but it
drastically reduces the possibility. The binding should now be suitable for
use in multi-threaded applications with databases containing >2KB values
where the entire database does not fit in RAM.