The narrow road to the deep North of version 1.0

See original GitHub issue

TODO before we can declare 1.0:

pass the test suite, with as few changes to the suite as possible
fix run tests via nosetests
make a base class for our tests
better temp file handling in test_foreign.py
some kind of memory mix-up still, we get an occasional crash
we want this to be a good Python package, but also compatible with the previous Python binding – if this turns out to be too difficult, we will need to make two packages: this, to provide the actual binding, and another package which sits over this as a compatibility layer
add GValue tests, see examples
we need to move almost all of the sample images outside the package
get it working with py3 – cffi seems to be quite a bit stricter under python3, this will need some changes
how do we keep compatibility with old enum code, can we just define __eq__ on the enum compat classes?
need a metatype for Image at least so we can support pyvips.Image.black(1, 1)
static docs
we could support dynamic docs with help(), we should test in one of the Python IDEs
leak test, both malloc and GObject
benchmark
remove a lot of the logging: we have too much right now
add buffer support and link to NumPy and PIL
test with Windows – we’ll need to at least change the name of the shared library, and maybe look at 32- and 64-bit modes
travis integration
test with macOS – we’ll need to at least fix the lib name
remove test suite temp files in a way that works on Windows, perhaps make a sub dir for all temp files, and delete that dir on exit
fix mysterious pypy leaks
test GC behaviour under write pressure … do we need to trigger GC ourselves? or maybe call __pypy__.add_memory_pressure(n) for PyPy