BUG: Don't error when usecols is a numpy array

doc/source/whatsnew/v0.19.0.txt

@@ -945,6 +945,7 @@ Bug Fixes
 - Bug in ``groupby().cumsum()`` calculating ``cumprod`` when ``axis=1``. (:issue:`13994`)
 - Bug in ``pd.read_csv()``, which may cause a segfault or corruption when iterating in large chunks over a stream/file under rare circumstances (:issue:`13703`)
 - Bug in ``pd.read_csv()``, which caused BOM files to be incorrectly parsed by not ignoring the BOM (:issue:`4793`)
+- Bug in ``pd.read_csv()`` with ``engine='python'`` which raised errors when a numpy array was passed in for ``usecols`` (:issue:`12546`)
 - Bug in ``pd.to_timedelta()`` in which the ``errors`` parameter was not being respected (:issue:`13613`)
 - Bug in ``io.json.json_normalize()``, where non-ascii keys raised an exception (:issue:`13213`)
 - Bug when passing a not-default-indexed ``Series`` as ``xerr`` or ``yerr`` in ``.plot()`` (:issue:`11858`)

pandas/io/parsers.py

@@ -972,6 +972,7 @@ def _validate_usecols_arg(usecols):
                                  'string', 'unicode'):
             raise ValueError(msg)
 
+        return set(usecols)
     return usecols
 
 

pandas/io/tests/parser/usecols.py

@@ -8,6 +8,7 @@
 from datetime import datetime
 import nose
 
+import numpy as np
 import pandas.util.testing as tm
 
 from pandas import DataFrame
@@ -361,3 +362,12 @@ def test_empty_usecols(self):
         expected = DataFrame()
         result = self.read_csv(StringIO(data), usecols=set([]))
         tm.assert_frame_equal(result, expected)
+
+    def test_np_array_usecols(self):
+        # See gh-12546
+        data = 'a,b,c\n1,2,3'
+        usecols = np.array(['a', 'b'])
+
+        expected = DataFrame([[1, 2]], columns=usecols)
+        result = self.read_csv(StringIO(data), usecols=usecols)
+        tm.assert_frame_equal(result, expected)