Set warning stacklevels for validation

[bmcfee]

Validator functions often raise warnings when something isn't quite right, eg:

mir_eval/mir_eval/chord.py

Lines 640 to 644 in 57f7c31

	# When either label list is empty, warn the user
	if len(reference_labels) == 0:
	warnings.warn('Reference labels are empty')
	if len(estimated_labels) == 0:
	warnings.warn('Estimated labels are empty')

However, the warning shows up to the user as coming from the validate function, which is not all that helpful since they never call this directly. We can make this more useful by setting stacklevel=2.

This way the warning will point to the evaluator that called validate, which is a little more helpful for debugging purposes, especially when the user is calling a module-level evaluate() function.

[craffel]

Good idea! Didn't know you could specify where in the stack the warning should come up.