[Python-Dev] Python Language Summit at PyCon: Agenda (original) (raw)
Daniel Holth dholth at gmail.com
Mon Mar 4 21:02:35 CET 2013
- Previous message: [Python-Dev] Python Language Summit at PyCon: Agenda
- Next message: [Python-Dev] Python Language Summit at PyCon: Agenda
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Mar 4, 2013 at 2:26 PM, Berker Peksağ <berker.peksag at gmail.com> wrote:
On Mon, Mar 4, 2013 at 9:14 PM, Barry Warsaw <barry at python.org> wrote:
On Mar 04, 2013, at 07:41 PM, Antoine Pitrou wrote:
$ python -m unittest discover $ python setup.py test $ python setup.py nosetests $ python -m nose test $ nosetests-X.Y
Besides having a multitude of choices, there's almost no way to automatically discover (e.g. by metadata inspection or some such) how to invoke the tests. You're often lucky if there's a README.test and it's still accurate. I hope we can have a "pytest" utility that does the right thing in 3.4 :-) Typing "python -m unittest discover" is too cumbersome. Where is this work being done (e.g. is there a PEP)? There is an open issue on the tracker: http://bugs.python.org/issue14266 --Berker
setup.py's setup(test_suite="x")... not sure if this is a distutils or setuptools feature. PEP 426 has an extension mechanism that could do the job.
- Previous message: [Python-Dev] Python Language Summit at PyCon: Agenda
- Next message: [Python-Dev] Python Language Summit at PyCon: Agenda
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]