A RetroSearch Logo

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

Search Query:

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

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

[Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda) [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)Antoine Pitrou solipsis at pitrou.net
Mon Mar 4 22:28:48 CET 2013
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.

Regards

Antoine.


More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4