[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
More information about the Python-Dev mailing list
Mon Mar 4 22:28:48 CET 2013
- Previous message: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)
- Next message: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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.
- Previous message: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)
- Next message: [Python-Dev] built-in Python test runner (was: Python Language Summit at PyCon: Agenda)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list