#14832: 'first' now really refers to first arg in unittest assertItemsEqual
This appears to have been a mixup introduced when we switched from
'expected/actual' to 'first/second'. The problem doesn't exist
in the corresponding assertCountEqual method in Python3.
diff --git a/Misc/NEWS b/Misc/NEWS
index c2be420..4908f39 100644
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@ -60,6 +60,9 @@
Library
-------
+- Issue #14832: fixed the order of the argument references in the error
+ message produced by unittest's assertItemsEqual.
+
- Issue #14829: Fix bisect issues under 64-bit Windows.
- Issue #14777: tkinter may return undecoded UTF-8 bytes as a string when