Currently benchmark follows the unittest philosophy of a script being a valid Python script with everything self-contained. pytest takes the view of getting rid of the "boilerplate" by having a special command required to run the script, i.e. the script is not a Python script but a pytest script.
Is it feasible for benchmark to support both approaches or should, like unittest and pytest, the two approaches be two separate benchmarking frameworks?
Currently benchmark follows the unittest philosophy of a script being a valid Python script with everything self-contained. pytest takes the view of getting rid of the "boilerplate" by having a special command required to run the script, i.e. the script is not a Python script but a pytest script.
Is it feasible for benchmark to support both approaches or should, like unittest and pytest, the two approaches be two separate benchmarking frameworks?