On May 06, 2013, at 08:02 PM, Piotr Ożarowski wrote: >with pybuild in unstable it should be a lot easier to add python3-foo >packages (just add binary package in debian/control, build depend on >python3-all-dev, use --buildsystem=pybuild in debian/rules and add some >.install files / export PYBUILD_DESTDIR_python{2,3})
>pybuild does invoke tests by default. I plan to extend pybuild's --test >to use plugin architecture as well (right now each build plugin can >define test method, if it's not implemented, 'python -m unittest discover' >is invoked). If one wants to f.e. use nosetests instead of autodetected >`setup.py test` or python -m unittest discover), (s)he has to: > >| override_dh_auto_test: >| pybuild --test --system=custom --test-args 'cd {build_dir}; nosetests' > >and: > >| override_dh_auto_test: >| pybuild --test-plugin nose > >or even: > >| export PYBUILD_TEST_PLUGIN=nose > >looks less hackish This sounds awesome. >> * What's the current status of pybuild and what should we do to adopt it >> over and above general dh_python2/3 adoption? > >--buildsystem=pybuild doesn't imply --with python2,python3 (hi Jakub! :) >but maybe we should consider it for debian/compat=10 since other helper >tools are deprecated? Hmm, maybe so. >> * Python 3.4 beta 1 is currently scheduled for November 23, 2013. What >> should our plans be related to 3.4? My current thinking is that we could >> support 3.4 but not make it the default. > >I think we should switch to 3.4 as the only supported Python 3.X as soon >as possible (3.4~beta?) The only hesitation I have is the typical lag of PyPI packages once a new version of Python is released. But maybe 3.3->3.4 won't be so bad... let's see. -Barry
signature.asc
Description: PGP signature