Michael Cahill 439f1213d6 Switch the Python API to not allocate objects explicitly, and instead leave that to SWIG typemaps. ...

This avoids making calls into Python's C API from our methods.  The problem with that is that in SWIG "thread" mode, we are not holding the Python interpreter lock, and some Python functions (including allocation functions) expect to be single-threaded.

While in the area, prefer generic SWIG macros to Python-specific ones and avoid int returns that are used purely for error checking.

closes #374

2012-10-24 14:33:39 +11:00

..

src

Retain copyright on the Python API, add the SWIG license to the local

2012-02-02 20:18:52 +00:00

fpacking.py

Retain copyright on the Python API, add the SWIG license to the local

2012-02-02 20:18:52 +00:00

intpack-test.py

Retain copyright on the Python API, add the SWIG license to the local

2012-02-02 20:18:52 +00:00

intpacking.py

Retain copyright on the Python API, add the SWIG license to the local

2012-02-02 20:18:52 +00:00

Makefile.am

Turn on SWIG optimizations and warnings.

2012-10-24 14:33:39 +11:00

packing-test.py

Retain copyright on the Python API, add the SWIG license to the local

2012-02-02 20:18:52 +00:00

packing.py

Retain copyright on the Python API, add the SWIG license to the local

2012-02-02 20:18:52 +00:00

setup.py

lang/python/wiredtiger_wrap.c:5726:3: warning: expression result unused

2012-09-12 15:04:39 +10:00

wiredtiger.i

Switch the Python API to not allocate objects explicitly, and instead leave that to SWIG typemaps.

2012-10-24 14:33:39 +11:00