[Python-Dev] Python Language Summit at PyCon: Agenda
ncoghlan at gmail.com
Tue Mar 5 01:20:00 CET 2013
On 5 Mar 2013 05:21, "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
> >> 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)?
> One thing to keep in mind is how to invoke this on a system with multiple
> versions of Python available. For example, in Debian, a decision was
> made to drop all the nosetests-X.Y scripts from /usr/bin.
> This makes sense when you think about having at least two major versions
> Python (2.x and 3.x) and maybe up to four (2.6, 2.7, 3.2, 3.3), *plus*
> versions of each. Add to that, we don't actually know at package build
> which versions of Python you might have installed on your system.
> A suggestion was made to provide a main entry point so that `pythonX.Y -m
> nose` would work, which makes sense to me and was adopted by the
> So while a top level `pytest` command may make sense, it also might not
> While PEP 426 has a way to declare test dependencies (a good thing), it
> to have no way to declare how to actually run the tests.
Metadata 2.0 won't cover that, 2.1 probably will. Please give us time to
solve problems incrementally rather than trying to fix everything at once.
>  Start of thread:
>  https://github.com/nose-devs/nose/issues/634
> Python-Dev mailing list
> Python-Dev at python.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev