[libre-riscv-dev] [Bug 79] switch to using unittest package for unit testing

bugzilla-daemon at libre-riscv.org bugzilla-daemon at libre-riscv.org
Tue Apr 30 12:13:35 BST 2019


--- Comment #1 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> ---
yes, i know, things have been thrown together somewhat, and
need sorting out.

i have a personal preference for using a Makefile even as
a shortcut / substitute for running a single command,
"nosetests3" or "python3 setup.py test".


it provides a central standardised location, and some uniformity
that makes more sense for more complex tasks (installation etc.)

i also tend to put in things like "make docs":

    epydoc -blahblah

which has sufficiently complex options that i tend to forget what they are.
likewise with autopep8, there are some options that *need* to be disabled.

etc. etc. otherwise you end up with a total mess of disparate "scripts"
and force the developer to go read some arbitrary text file to find out
what they are.

You are receiving this mail because:
You are on the CC list for the bug.

More information about the libre-riscv-dev mailing list