TST: win32 fixes
TST: test_indexing dtype comps, closes #5466

TST don't compare invalid indices in eval operations, closes #5467

TST: invalid assignment for np.timedelta64 closes #5465

TST: skip locale checks on windows cloes #5464

TST: dtype comp issue on windows in test_indexing (GH5466)

TST: skip test_pow on windows (GH5467)

so do you have any sense of _why_ these issues occur? Just 32 bit issues? specific to windows?

Just want to be able to keep in mind in the future.
 @jtratner these are all because the tests on a 32-bit windows default with int32 for numpy arange (so the tests are wrong), e.g. in this case numpy creates these as 32-bit integers but they are really 64-bit in the implementation
 Can we add a 32bit Travis build?  Would that help?
 I think that travis was using 32-bit builds...now seem 64-bit....

it DOES help catch stuff (though this is really windows specific oddities)
