(the 3.2 upgrade will trigger deprecation warnings, so I'm hesitant to ship this as is, but then I don't think it worth cleaning up setup.py etc for the 2.x branch. Packages that are python3 should really use the cookiecutter/master branches, so should not run into the deprecations after we merge #375, too.)
(the 3.2 upgrade will trigger deprecation warnings, so I'm hesitant to ship this as is, but then I don't think it worth cleaning up setup.py etc for the 2.x branch. Packages that are python3 should really use the
cookiecutter/masterbranches, so should not run into the deprecations after we merge #375, too.)