You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks!
perhaps I'm just nitpicking, but in the tests, wouldn't it be better to test for the explicit results rather than just a comparison match between a one-level and two-level groupby in case the the results were the same but incorrect?
Version 0.8.0 beta 2
* tag 'v0.8.0b2': (37 commits)
RLS: 0.8.0 beta 2
BUG: bytes_to_str for read_csv
BUG: import BytesIO for py3compat
BUG: fix compat errors for yahoo data reader
ENH: convert datetime.datetime ourselves, 15x speedup
Make tox work across versions of Python from 2.5 to 3.2
Reenable py31 and py32 in .travis.yml
TST: test coverage
TST: oops, delete stray line
REF: factor out ujson extension into pandasjson for now
TST: eliminate copies in datetime64 serialization; don't copy data in DatetimeIndex, closepandas-dev#1320
DOC: refresh time zone docs closepandas-dev#1447
BUG: always raise exception when concat keys aren't found in passed levels, closepandas-dev#1406
ENH: implement passed quantile array to qcut and document that plus factors, closepandas-dev#1407
ENH: clearer out of bounds error message in cut/qcut, closepandas-dev#1409
ENH: allow renaming of index levels when concatenating, closepandas-dev#1419
BUG: fix MultiIndex bugs described in pandas-dev#1401
DOC: release notes
BUG: implement multiple DataFrame.join / merge on non-unique indexes by multiple merges, closepandas-dev#1421
REF: remove offset names from pandas namespace
...
The text was updated successfully, but these errors were encountered: