pandas/io/tests/test_excel.py | 6 6 + 0 - 0 !
1 file changed, 6 insertions(+)

 bf: skip two tests which failed when xlwt was n/a

pandas/tests/indexes/common.py | 6 6 + 0 - 0 !
1 file changed, 6 insertions(+)

 bf: skip equivalence test for itemsize and nbytes if "values" ndarray view of type object

pandas/tools/tests/test_tile.py | 5 4 + 1 - 0 !
1 file changed, 4 insertions(+), 1 deletion(-)

 bf: define expected series of correct for arch (eg i386) int

pandas/io/tests/parser/common.py | 14 7 + 7 - 0 !
pandas/tests/series/test_datetime_values.py | 2 1 + 1 - 0 !
pandas/tseries/tests/test_timeseries.py | 2 1 + 1 - 0 !
3 files changed, 9 insertions(+), 9 deletions(-)

 bf(tst): use = (native) instead of < (little endian) for target data types (#14832)

pandas/__init__.py | 5 1 + 4 - 0 !
1 file changed, 1 insertion(+), 4 deletions(-)

---

doc/make.py | 3 2 + 1 - 0 !
1 file changed, 2 insertions(+), 1 deletion(-)

---

pandas/io/tests/test_stata.py | 4 4 + 0 - 0 !
1 file changed, 4 insertions(+)

---

pandas/io/tests/data/macau.html | 19 4 + 15 - 0 !
pandas/io/tests/data/spam.html | 44 4 + 40 - 0 !
2 files changed, 8 insertions(+), 55 deletions(-)

---

pandas/tests/frame/test_constructors.py | 3 3 + 0 - 0 !
1 file changed, 3 insertions(+)

---

pandas/io/tests/test_pytables.py | 10 7 + 3 - 0 !
1 file changed, 7 insertions(+), 3 deletions(-)

 swallow the error from pytables

happens on wheezy and ubuntu 12.04, only in amd64, only if the entire test

pandas/tests/test_expressions.py | 2 1 + 1 - 0 !
1 file changed, 1 insertion(+), 1 deletion(-)

 avoid overflows for now
  Due to a bug in current numpy beta (or numexpr) tests would fail
  if operation on int leads to overflows (e.g. of pow operation).

  as a workaround for now -- avoid big ints

pandas/tests/test_multilevel.py | 12 6 + 6 - 0 !
1 file changed, 6 insertions(+), 6 deletions(-)

 use tiinfo correctly
 The underlying issue (but not strictly a bug as the documentation 
 specifically says not to do that - 
 http://sources.debian.net/src/python-tz/2016.7-0.2/pytz/tzinfo.py/#L247 
 ) is that passing a pytz tzinfo to the datetime constructor uses its 
 first listed offset, not its correct offset for that date:
 .
 >>> datetime.datetime(2017,4,1,tzinfo=pytz.timezone('Europe/London'))
 datetime.datetime(2017, 4, 1, 0, 0, tzinfo=<DstTzInfo 'Europe/London' 
 GMT0:00:00 STD>)
 >>> pytz.timezone('Europe/London').localize(datetime.datetime(2017,4,1))
 datetime.datetime(2017, 4, 1, 0, 0, tzinfo=<DstTzInfo 'Europe/London' 
 BST+1:00:00 DST>)