RetroSearch Browse

Tue Mar 5 08:19:16 CET 2013 · https://mail.python.org/pipermail/python-dev/2013-March/124601.html

On Mon, 4 Mar 2013 15:47:37 -0800
Eli Bendersky <eliben at gmail.com> wrote:
> On Mon, Mar 4, 2013 at 1:28 PM, Antoine Pitrou <solipsis at pitrou.net> wrote:
> 
> > On Mon, 4 Mar 2013 13:26:57 -0800
> > Eli Bendersky <eliben at gmail.com> wrote:
> > > [Splitting into a separate thread]
> > >
> > > Do we really need to overthink something that requires a trivial alias to
> > > set up for one's own convenience?
> > >
> > > Picking a Python version (as Barry mentions) is just one of the problems.
> > > What's wrong with:
> > >
> > > alias rupytests='python3 -m unittest discover"
> > > alias runpytests2='python2 -m unittest discover"
> > >
> > > ?
> > >
> > > Don't get me wrong, I love the "discover" option and agree that it should
> > > be the recommended way to go - but isn't this largely a documentation
> > issue?
> >
> > I would personally call it a typing issue :-) "python -m unittest
> > discover" is just too long.
> >
> 
> Command-line options for advanced capabilities can get long, yes.

The whole point is that discovery is not "advanced capability", it's
pretty basic by today's standards. So it should actually be the default
behaviour (like it is with nose).

Regards

Antoine.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2013-March/124601.html below:

[Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)