Pandas
Pandas
toolkit
Release 0.16.2
1 Whats New 3
1.1 v0.16.2 (June 12, 2015) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 v0.16.1 (May 11, 2015) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 v0.16.0 (March 22, 2015) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.4 v0.15.2 (December 12, 2014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
1.5 v0.15.1 (November 9, 2014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
1.6 v0.15.0 (October 18, 2014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
1.7 v0.14.1 (July 11, 2014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
1.8 v0.14.0 (May 31 , 2014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
1.9 v0.13.1 (February 3, 2014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
1.10 v0.13.0 (January 3, 2014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
1.11 v0.12.0 (July 24, 2013) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
1.12 v0.11.0 (April 22, 2013) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
1.13 v0.10.1 (January 22, 2013) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
1.14 v0.10.0 (December 17, 2012) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
1.15 v0.9.1 (November 14, 2012) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
1.16 v0.9.0 (October 7, 2012) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
1.17 v0.8.1 (July 22, 2012) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
1.18 v0.8.0 (June 29, 2012) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
1.19 v.0.7.3 (April 12, 2012) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
1.20 v.0.7.2 (March 16, 2012) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
1.21 v.0.7.1 (February 29, 2012) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
1.22 v.0.7.0 (February 9, 2012) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
1.23 v.0.6.1 (December 13, 2011) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
1.24 v.0.6.0 (November 25, 2011) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
1.25 v.0.5.0 (October 24, 2011) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
1.26 v.0.4.3 through v0.4.1 (September 25 - October 9, 2011) . . . . . . . . . . . . . . . . . . . . . . . . 196
2 Installation 199
2.1 Python version support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
2.2 Installing pandas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
2.3 Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
i
4 Frequently Asked Questions (FAQ) 217
4.1 DataFrame memory usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
4.2 Migrating from scikits.timeseries to pandas >= 0.8.0 . . . . . . . . . . . . . . . . . . . . . . . . . . 218
4.3 Byte-Ordering Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
4.4 Visualizing Data in Qt applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
7 Tutorials 253
7.1 Internal Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
7.2 pandas Cookbook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
7.3 Lessons for New pandas Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
7.4 Practical data analysis with Python . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
7.5 Excel charts with pandas, vincent and xlsxwriter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
7.6 Various Tutorials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
8 Cookbook 257
8.1 Idioms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
8.2 Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
8.3 MultiIndexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
8.4 Missing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
8.5 Grouping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
8.6 Timeseries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
8.7 Merge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
8.8 Plotting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
8.9 Data In/Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
8.10 Computation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
8.11 Timedeltas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
8.12 Aliasing Axis Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
8.13 Creating Example Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
ii
9.3 Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
9.4 Panel4D (Experimental) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
9.5 PanelND (Experimental) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
iii
14 MultiIndex / Advanced Indexing 425
14.1 Hierarchical indexing (MultiIndex) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
14.2 Advanced indexing with hierarchical index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
14.3 The need for sortedness with MultiIndex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
14.4 Take Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
14.5 CategoricalIndex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
14.6 Float64Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
iv
20.7 Up- and downsampling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
20.8 Time Span Representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
20.9 Converting between Representations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
20.10 Representing out-of-bounds spans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
20.11 Time Zone Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
23 Plotting 633
23.1 Basic Plotting: plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
23.2 Other Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
23.3 Plotting with Missing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
23.4 Plotting Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
23.5 Plot Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
23.6 Plotting directly with matplotlib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
23.7 Trellis plotting interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700
v
25.4 FRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
25.5 Fama/French . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
25.6 World Bank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
25.7 Google Analytics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
vi
32.3 GROUP BY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868
32.4 JOIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
32.5 UNION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871
32.6 UPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
32.7 DELETE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
34 Internals 1575
34.1 Indexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1575
34.2 Subclassing pandas Data Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1576
vii
35.30 pandas 0.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676
viii
pandas: powerful Python data analysis toolkit, Release 0.16.2
PDF Version
Zipped HTML Date: June 13, 2015 Version: 0.16.2
Binary Installers: http://pypi.python.org/pypi/pandas
Source Repository: http://github.com/pydata/pandas
Issues & Ideas: https://github.com/pydata/pandas/issues
Q&A Support: http://stackoverflow.com/questions/tagged/pandas
Developer Mailing List: http://groups.google.com/group/pydata
pandas is a Python package providing fast, flexible, and expressive data structures designed to make working with
relational or labeled data both easy and intuitive. It aims to be the fundamental high-level building block for doing
practical, real world data analysis in Python. Additionally, it has the broader goal of becoming the most powerful
and flexible open source data analysis / manipulation tool available in any language. It is already well on its way
toward this goal.
pandas is well suited for many different kinds of data:
Tabular data with heterogeneously-typed columns, as in an SQL table or Excel spreadsheet
Ordered and unordered (not necessarily fixed-frequency) time series data.
Arbitrary matrix data (homogeneously typed or heterogeneous) with row and column labels
Any other form of observational / statistical data sets. The data actually need not be labeled at all to be placed
into a pandas data structure
The two primary data structures of pandas, Series (1-dimensional) and DataFrame (2-dimensional), handle the
vast majority of typical use cases in finance, statistics, social science, and many areas of engineering. For R users,
DataFrame provides everything that Rs data.frame provides and much more. pandas is built on top of NumPy
and is intended to integrate well within a scientific computing environment with many other 3rd party libraries.
Here are just a few of the things that pandas does well:
Easy handling of missing data (represented as NaN) in floating point as well as non-floating point data
Size mutability: columns can be inserted and deleted from DataFrame and higher dimensional objects
Automatic and explicit data alignment: objects can be explicitly aligned to a set of labels, or the user can
simply ignore the labels and let Series, DataFrame, etc. automatically align the data for you in computations
Powerful, flexible group by functionality to perform split-apply-combine operations on data sets, for both ag-
gregating and transforming data
Make it easy to convert ragged, differently-indexed data in other Python and NumPy data structures into
DataFrame objects
Intelligent label-based slicing, fancy indexing, and subsetting of large data sets
Intuitive merging and joining data sets
Flexible reshaping and pivoting of data sets
Hierarchical labeling of axes (possible to have multiple labels per tick)
Robust IO tools for loading data from flat files (CSV and delimited), Excel files, databases, and saving / loading
data from the ultrafast HDF5 format
Time series-specific functionality: date range generation and frequency conversion, moving window statistics,
moving window linear regressions, date shifting and lagging, etc.
CONTENTS 1
pandas: powerful Python data analysis toolkit, Release 0.16.2
Many of these principles are here to address the shortcomings frequently experienced using other languages / scientific
research environments. For data scientists, working with data is typically divided into multiple stages: munging and
cleaning data, analyzing / modeling it, then organizing the results of the analysis into a form suitable for plotting or
tabular display. pandas is the ideal tool for all of these tasks.
Some other notes
pandas is fast. Many of the low-level algorithmic bits have been extensively tweaked in Cython code. However,
as with anything else generalization usually sacrifices performance. So if you focus on one feature for your
application you may be able to create a faster specialized tool.
pandas is a dependency of statsmodels, making it an important part of the statistical computing ecosystem in
Python.
pandas has been used extensively in production in financial applications.
Note: This documentation assumes general familiarity with NumPy. If you havent used NumPy much or at all, do
invest some time in learning about NumPy first.
See the package overview for more detail about whats in the library.
2 CONTENTS
CHAPTER
ONE
WHATS NEW
This is a minor bug-fix release from 0.16.1 and includes a a large number of bug fixes along some new features
(pipe() method), enhancements, and performance improvements.
We recommend that all users upgrade to this version.
Highlights include:
A new pipe method, see here
Documentation on how to use numba with pandas, see here
Pipe
Weve introduced a new method DataFrame.pipe(). As suggested by the name, pipe should be used to pipe
data through a chain of function calls. The goal is to avoid confusing nested function calls like
# df is a DataFrame
# f, g, and h are functions that take and return DataFrames
f(g(h(df), arg1=1), arg2=2, arg3=3)
The logic flows from inside out, and function names are separated from their keyword arguments. This can be rewritten
as
3
pandas: powerful Python data analysis toolkit, Release 0.16.2
(df.pipe(h)
.pipe(g, arg1=1)
.pipe(f, arg2=2, arg3=3)
)
Now both the code and the logic flow from top to bottom. Keyword arguments are next to their functions. Overall the
code is much more readable.
In the example above, the functions f, g, and h each expected the DataFrame as the first positional argument. When
the function you wish to apply takes its data anywhere other than the first argument, pass a tuple of (function,
keyword) indicating where the DataFrame should flow. For example:
In [1]: import statsmodels.formula.api as sm
The pipe method is inspired by unix pipes, which stream text through processes. More recently dplyr and magrittr
have introduced the popular (%>%) pipe operator for R.
See the documentation for more. (GH10129)
Other Enhancements
Removed the hard-coded size limits on the DataFrame HTML representation in the IPython notebook, and
leave this to IPython itself (only for IPython v3.0 or greater). This eliminates the duplicate scroll bars that
appeared in the notebook with large frames (GH10231).
Note that the notebook has a toggle output scrolling feature to limit the display of very large frames
(by clicking left of the output). You can also configure the way DataFrames are displayed using the pandas
options, see here here.
axis parameter of DataFrame.quantile now accepts also index and column. (GH9543)
Holiday now raises NotImplementedError if both offset and observance are used in the construc-
tor instead of returning an incorrect result (GH10217).
Bug in Series.hist raises an error when a one row Series was given (GH10214)
Bug where HDFStore.select modifies the passed columns list (GH7212)
Bug in Categorical repr with display.width of None in Python 3 (GH10087)
Bug in to_json with certain orients and a CategoricalIndex would segfault (GH10317)
Bug where some of the nan funcs do not have consistent return dtypes (GH10251)
Bug in DataFrame.quantile on checking that a valid axis was passed (GH9543)
Bug in groupby.apply aggregation for Categorical not preserving categories (GH10138)
Bug in to_csv where date_format is ignored if the datetime is fractional (GH10209)
Bug in DataFrame.to_json with mixed data types (GH10289)
Bug in cache updating when consolidating (GH10264)
Bug in mean() where integer dtypes can overflow (GH10172)
Bug where Panel.from_dict does not set dtype when specified (GH10058)
Bug in Index.union raises AttributeError when passing array-likes. (GH10149)
Bug in Timestamps microsecond, quarter, dayofyear, week and daysinmonth properties re-
turn np.int type, not built-in int. (GH10050)
Bug in NaT raises AttributeError when accessing to daysinmonth, dayofweek properties.
(GH10096)
Bug in Index repr when using the max_seq_items=None setting (GH10182).
Bug in getting timezone data with dateutil on various platforms ( GH9059, GH8639, GH9663, GH10121)
Bug in displaying datetimes with mixed frequencies; display ms datetimes to the proper precision. (GH10170)
Bug in setitem where type promotion is applied to the entire block (GH10280)
This is a minor bug-fix release from 0.16.0 and includes a a large number of bug fixes along several new features,
enhancements, and performance improvements. We recommend that all users upgrade to this version.
Highlights include:
Support for a CategoricalIndex, a category based index, see here
New section on how-to-contribute to pandas, see here
Revised Merge, join, and concatenate documentation, including graphical examples to make it easier to un-
derstand each operations, see here
New method sample for drawing random samples from Series, DataFrames and Panels. See here
The default Index printing has changed to a more uniform format, see here
BusinessHour datetime-offset is now supported, see here
Further enhancement to the .str accessor to make string operations easier, see here
Warning: In pandas 0.17.0, the sub-package pandas.io.data will be removed in favor of a separately
installable package. See here for details (GH8961)
1.2.1 Enhancements
CategoricalIndex
We introduce a CategoricalIndex, a new type of index object that is useful for supporting indexing with dupli-
cates. This is a container around a Categorical (introduced in v0.15.0) and allows efficient indexing and storage
of an index with a large number of duplicated elements. Prior to 0.16.1, setting the index of a DataFrame/Series
with a category dtype would convert this to regular object-based Index.
In [1]: df = DataFrame({'A' : np.arange(6),
...: 'B' : Series(list('aabbca')).astype('category',
...: categories=list('cab'))
...: })
...:
In [2]: df
Out[2]:
A B
0 0 a
1 1 a
2 2 b
3 3 b
4 4 c
5 5 a
In [3]: df.dtypes
Out[3]:
A int32
B category
dtype: object
In [4]: df.B.cat.categories
Out[4]: Index([u'c', u'a', u'b'], dtype='object')
In [6]: df2.index
Out[6]: CategoricalIndex([u'a', u'a', u'b', u'b', u'c', u'a'], categories=[u'c', u'a', u'b'], ordered
indexing with __getitem__/.iloc/.loc/.ix works similarly to an Index with duplicates. The indexers
MUST be in the category or the operation will raise.
In [7]: df2.loc['a']
Out[7]:
A
B
a 0
a 1
a 5
groupby operations on the index will preserve the index nature as well
In [10]: df2.groupby(level=0).sum()
Out[10]:
A
B
c 4
a 6
b 5
In [11]: df2.groupby(level=0).sum().index
Out[11]: CategoricalIndex([u'c', u'a', u'b'], categories=[u'c', u'a', u'b'], ordered=False, name=u'B'
reindexing operations, will return a resulting index based on the type of the passed indexer, meaning that passing a
list will return a plain-old-Index; indexing with a Categorical will return a CategoricalIndex, indexed
according to the categories of the PASSED Categorical dtype. This allows one to arbitrarly index these even with
values NOT in the categories, similarly to how you can reindex ANY pandas index.
In [12]: df2.reindex(['a','e'])
Out[12]:
A
B
a 0
a 1
a 5
e NaN
In [13]: df2.reindex(['a','e']).index
Out[13]: Index([u'a', u'a', u'a', u'e'], dtype='object', name=u'B')
In [14]: df2.reindex(pd.Categorical(['a','e'],categories=list('abcde')))
Out[14]:
A
B
a 0
a 1
a 5
e NaN
In [15]: df2.reindex(pd.Categorical(['a','e'],categories=list('abcde'))).index
Out[15]: CategoricalIndex([u'a', u'a', u'a', u'e'], categories=[u'a', u'b', u'c', u'd', u'e'], ordere
Sample
Series, DataFrames, and Panels now have a new method: sample(). The method accepts a specific number of rows
or columns to return, or a fraction of the total number or rows or columns. It also has options for sampling with or
without replacement, for passing in a column for weights for non-uniform sampling, and for setting seed values to
facilitate replication. (GH2419)
In [16]: example_series = Series([0,1,2,3,4,5])
When applied to a DataFrame, one may pass the name of a column to specify sampling weights when sampling from
rows.
In [24]: df = DataFrame({'col1':[9,8,7,6], 'weight_column':[0.5, 0.4, 0.1, 0]})
Continuing from v0.16.0, the following enhancements make string operations easier and more consistent with standard
python string operations.
Added StringMethods (.str accessor) to Index (GH9068)
The .str accessor is now available for both Series and Index.
In [26]: idx = Index([' jack', 'jill ', ' jesse ', 'frank'])
In [27]: idx.str.strip()
Out[27]: Index([u'jack', u'jill', u'jesse', u'frank'], dtype='object')
One special case for the .str accessor on Index is that if a string method returns bool, the .str accessor
will return a np.array instead of a boolean Index (GH8875). This enables the following expression to work
naturally:
In [28]: idx = Index(['a1', 'a2', 'b1', 'b2'])
In [30]: s
Out[30]:
a1 0
a2 1
b1 2
b2 3
dtype: int64
In [31]: idx.str.startswith('a')
Out[31]: array([ True, True, False, False], dtype=bool)
In [32]: s[s.index.str.startswith('a')]
Out[32]:
a1 0
a2 1
dtype: int64
The following new methods are accesible via .str accessor to apply the function to each values. (GH9766,
GH9773, GH10031, GH10045, GH10052)
Methods
capitalize() swapcase() normalize() partition() rpartition()
index() rindex() translate()
split now takes expand keyword to specify whether to expand dimensionality. return_type is depre-
cated. (GH9847)
In [33]: s = Series(['a,b', 'a,c', 'b,c'])
# return Series
In [34]: s.str.split(',')
Out[34]:
0 [a, b]
1 [a, c]
2 [b, c]
dtype: object
# return DataFrame
In [35]: s.str.split(',', expand=True)
Out[35]:
0 1
0 a b
1 a c
2 b c
# return Index
In [37]: idx.str.split(',')
Out[37]: Index([[u'a', u'b'], [u'a', u'c'], [u'b', u'c']], dtype='object')
# return MultiIndex
In [38]: idx.str.split(',', expand=True)
Out[38]:
MultiIndex(levels=[[u'a', u'b'], [u'b', u'c']],
labels=[[0, 0, 1], [0, 1, 1]])
Other Enhancements
BusinessHour offset is now supported, which represents business hours starting from 09:00 - 17:00 on
BusinessDay by default. See Here for details. (GH7905)
DataFrame.diff now takes an axis parameter that determines the direction of differencing (GH9727)
Allow clip, clip_lower, and clip_upper to accept array-like arguments as thresholds (This is a regres-
sion from 0.11.0). These methods now have an axis parameter which determines how the Series or DataFrame
will be aligned with the threshold(s). (GH6966)
DataFrame.mask() and Series.mask() now support same keywords as where (GH8801)
drop function can now accept errors keyword to suppress ValueError raised when any of label does not
exist in the target data. (GH6736)
In [43]: df = DataFrame(np.random.randn(3, 3), columns=['A', 'B', 'C'])
Add support for separating years and quarters using dashes, for example 2014-Q1. (GH9688)
Allow conversion of values with dtype datetime64 or timedelta64 to strings using astype(str)
(GH9757)
get_dummies function now accepts sparse keyword. If set to True, the return DataFrame is sparse, e.g.
SparseDataFrame. (GH8823)
Period now accepts datetime64 as value input. (GH9054)
Allow timedelta string conversion when leading zero is missing from time definition, ie 0:00:00 vs 00:00:00.
(GH9570)
Allow Panel.shift with axis=items (GH9890)
Trying to write an excel file now raises NotImplementedError if the DataFrame has a MultiIndex
instead of writing a broken Excel file. (GH9794)
Allow Categorical.add_categories to accept Series or np.array. (GH9927)
Add/delete str/dt/cat accessors dynamically from __dir__. (GH9910)
Add normalize as a dt accessor method. (GH10047)
DataFrame and Series now have _constructor_expanddim property as overridable constructor for
one higher dimensionality data. This should be used only when it is really needed, see here
pd.lib.infer_dtype now returns bytes in Python 3 where appropriate. (GH10032)
When passing in an ax to df.plot( ..., ax=ax), the sharex kwarg will now default to False. The result
is that the visibility of xlabels and xticklabels will not anymore be changed. You have to do that by yourself
for the right axes in your figure or set sharex=True explicitly (but this changes the visible for all axes in the
figure, not only the one which is passed in!). If pandas creates the subplots itself (e.g. no passed in ax kwarg),
then the default is still sharex=True and the visibility changes are applied.
assign() now inserts new columns in alphabetical order. Previously the order was arbitrary. (GH9777)
By default, read_csv and read_table will now try to infer the compression type based on the file exten-
sion. Set compression=None to restore the previous behavior (no decompression). (GH9770)
Deprecations
The string representation of Index and its sub-classes have now been unified. These will show a single-line display
if there are few values; a wrapped multi-line display for a lot of values (but less than display.max_seq_items;
if lots of items (> display.max_seq_items) will show a truncated display (the head and tail of the data). The
formatting for MultiIndex is unchanges (a multi-line wrapped display). The display width responds to the option
display.max_seq_items, which is defaulted to 100. (GH6482)
Previous Behavior
In [2]: pd.Index(range(4),name='foo')
Out[2]: Int64Index([0, 1, 2, 3], dtype='int64')
In [3]: pd.Index(range(104),name='foo')
Out[3]: Int64Index([0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22,
In [4]: pd.date_range('20130101',periods=4,name='foo',tz='US/Eastern')
Out[4]:
<class 'pandas.tseries.index.DatetimeIndex'>
[2013-01-01 00:00:00-05:00, ..., 2013-01-04 00:00:00-05:00]
Length: 4, Freq: D, Timezone: US/Eastern
In [5]: pd.date_range('20130101',periods=104,name='foo',tz='US/Eastern')
Out[5]:
<class 'pandas.tseries.index.DatetimeIndex'>
[2013-01-01 00:00:00-05:00, ..., 2013-04-14 00:00:00-04:00]
Length: 104, Freq: D, Timezone: US/Eastern
New Behavior
In [45]: pd.set_option('display.width', 80)
Improved csv write performance with mixed dtypes, including datetimes by up to 5x (GH9940)
Improved csv write performance generally by 2x (GH9940)
Improved the performance of pd.lib.max_len_string_array by 5-7x (GH10024)
Bug where labels did not appear properly in the legend of DataFrame.plot(), passing label= arguments
works, and Series indices are no longer mutated. (GH9542)
Bug in json serialization causing a segfault when a frame had zero length. (GH9805)
Bug in read_csv where missing trailing delimiters would cause segfault. (GH5664)
Bug in retaining index name on appending (GH9862)
Bug in scatter_matrix draws unexpected axis ticklabels (GH5662)
Fixed bug in StataWriter resulting in changes to input DataFrame upon save (GH9795).
Bug in transform causing length mismatch when null entries were present and a fast aggregator was being
used (GH9697)
Bug in equals causing false negatives when block order differed (GH9330)
Bug in grouping with multiple pd.Grouper where one is non-time based (GH10063)
Bug in read_sql_table error when reading postgres table with timezone (GH7139)
Bug in DataFrame slicing may not retain metadata (GH9776)
Bug where TimdeltaIndex were not properly serialized in fixed HDFStore (GH9635)
Bug with TimedeltaIndex constructor ignoring name when given another TimedeltaIndex as data
(GH10025).
Bug in DataFrameFormatter._get_formatted_index with not applying max_colwidth to the
DataFrame index (GH7856)
Bug in .loc with a read-only ndarray data source (GH10043)
Bug in groupby.apply() that would raise if a passed user defined function either returned only None (for
all input). (GH9685)
Always use temporary files in pytables tests (GH9992)
Bug in plotting continuously using secondary_y may not show legend properly. (GH9610, GH9779)
Bug in DataFrame.plot(kind="hist") results in TypeError when DataFrame contains non-
numeric columns (GH9853)
Bug where repeated plotting of DataFrame with a DatetimeIndex may raise TypeError (GH9852)
Bug in setup.py that would allow an incompat cython version to build (GH9827)
Bug in plotting secondary_y incorrectly attaches right_ax property to secondary axes specifying itself
recursively. (GH9861)
Bug in Series.quantile on empty Series of type Datetime or Timedelta (GH9675)
Bug in where causing incorrect results when upcasting was required (GH9731)
Bug in FloatArrayFormatter where decision boundary for displaying small floats in decimal format is
off by one order of magnitude for a given display.precision (GH9764)
Fixed bug where DataFrame.plot() raised an error when both color and style keywords were passed
and there was no color symbol in the style strings (GH9671)
Not showing a DeprecationWarning on combining list-likes with an Index (GH10083)
Bug in read_csv and read_table when using skip_rows parameter if blank lines are present. (GH9832)
Bug in read_csv() interprets index_col=True as 1 (GH9798)
Bug in index equality comparisons using == failing on Index/MultiIndex type incompatibility (GH9785)
Bug in which SparseDataFrame could not take nan as a column name (GH8822)
Bug in to_msgpack and read_msgpack zlib and blosc compression support (GH9783)
Bug GroupBy.size doesnt attach index name properly if grouped by TimeGrouper (GH9925)
Bug causing an exception in slice assignments because length_of_indexer returns wrong results
(GH9995)
Bug in csv parser causing lines with initial whitespace plus one non-space character to be skipped. (GH9710)
Bug in C csv parser causing spurious NaNs when data started with newline followed by whitespace. (GH10022)
Bug causing elements with a null group to spill into the final group when grouping by a Categorical
(GH9603)
Bug where .iloc and .loc behavior is not consistent on empty dataframes (GH9964)
Bug in invalid attribute access on a TimedeltaIndex incorrectly raised ValueError instead of
AttributeError (GH9680)
Bug in unequal comparisons between categorical data and a scalar, which was not in the categories (e.g.
Series(Categorical(list("abc"), ordered=True)) > "d". This returned False for all el-
ements, but now raises a TypeError. Equality comparisons also now return False for == and True for !=.
(GH9848)
Bug in DataFrame __setitem__ when right hand side is a dictionary (GH9874)
Bug in where when dtype is datetime64/timedelta64, but dtype of other is not (GH9804)
Bug in MultiIndex.sortlevel() results in unicode level name breaks (GH9856)
Bug in which groupby.transform incorrectly enforced output dtypes to match input dtypes. (GH9807)
Bug in DataFrame constructor when columns parameter is set, and data is an empty list (GH9939)
Bug in bar plot with log=True raises TypeError if all values are less than 1 (GH9905)
Bug in horizontal bar plot ignores log=True (GH9905)
Bug in PyTables queries that did not return proper results using the index (GH8265, GH9676)
Bug where dividing a dataframe containing values of type Decimal by another Decimal would raise.
(GH9787)
Bug where using DataFrames asfreq would remove the name of the index. (GH9885)
Bug causing extra index point when resample BM/BQ (GH9756)
Changed caching in AbstractHolidayCalendar to be at the instance level rather than at the class level as
the latter can result in unexpected behaviour. (GH9552)
This is a major release from 0.15.2 and includes a small number of API changes, several new features, enhancements,
and performance improvements along with a large number of bug fixes. We recommend that all users upgrade to this
version.
Highlights include:
DataFrame.assign method, see here
Series.to_coo/from_coo methods to interact with scipy.sparse, see here
Backwards incompatible change to Timedelta to conform the .seconds attribute with
datetime.timedelta, see here
Changes to the .loc slicing API to conform with the behavior of .ix see here
Changes to the default for ordering in the Categorical constructor, see here
Enhancement to the .str accessor to make string operations easier, see here
The pandas.tools.rplot, pandas.sandbox.qtpandas and pandas.rpy modules are deprecated.
We refer users to external packages like seaborn, pandas-qt and rpy2 for similar or equivalent functionality, see
here
Check the API Changes and deprecations before updating.
DataFrame Assign
Inspired by dplyrs mutate verb, DataFrame has a new assign() method. The function signature for assign is
simply **kwargs. The keys are the column names for the new fields, and the values are either a value to be inserted
(for example, a Series or NumPy array), or a function of one argument to be called on the DataFrame. The new
values are inserted, and the entire DataFrame (with all original and new columns) is returned.
In [1]: iris = read_csv('data/iris.data')
In [2]: iris.head()
Out[2]:
SepalLength SepalWidth PetalLength PetalWidth Name
0 5.1 3.5 1.4 0.2 Iris-setosa
1 4.9 3.0 1.4 0.2 Iris-setosa
2 4.7 3.2 1.3 0.2 Iris-setosa
3 4.6 3.1 1.5 0.2 Iris-setosa
4 5.0 3.6 1.4 0.2 Iris-setosa
Above was an example of inserting a precomputed value. We can also pass in a function to be evalutated.
In [4]: iris.assign(sepal_ratio = lambda x: (x['SepalWidth'] /
...: x['SepalLength'])).head()
...:
Out[4]:
SepalLength SepalWidth PetalLength PetalWidth Name sepal_ratio
0 5.1 3.5 1.4 0.2 Iris-setosa 0.686275
1 4.9 3.0 1.4 0.2 Iris-setosa 0.612245
The power of assign comes when used in chains of operations. For example, we can limit the DataFrame to just
those with a Sepal Length greater than 5, calculate the ratio, and plot
In [5]: (iris.query('SepalLength > 5')
...: .assign(SepalRatio = lambda x: x.SepalWidth / x.SepalLength,
...: PetalRatio = lambda x: x.PetalWidth / x.PetalLength)
...: .plot(kind='scatter', x='SepalRatio', y='PetalRatio'))
...:
Out[5]: <matplotlib.axes._subplots.AxesSubplot at 0xa2b4d98c>
In [9]: s
Out[9]:
A B C D
1 2 a 0 3
1 NaN
1 b 0 1
1 3
2 1 b
0 NaN
1 NaN
dtype: float64
# SparseSeries
In [10]: ss = s.to_sparse()
In [11]: ss
Out[11]:
A B C D
1 2 a 0 3
1 NaN
1 b 0 1
1 3
2 1 b 0 NaN
1 NaN
dtype: float64
BlockIndex
Block locations: array([0, 2])
Block lengths: array([1, 2])
In [13]: A
Out[13]:
<3x4 sparse matrix of type '<type 'numpy.float64'>'
with 3 stored elements in COOrdinate format>
In [14]: A.todense()
Out[14]:
matrix([[ 3., 0., 0., 0.],
[ 0., 0., 1., 3.],
[ 0., 0., 0., 0.]])
In [15]: rows
Out[15]: [(1L, 2L), (1L, 1L), (2L, 1L)]
In [16]: columns
Out[16]: [('a', 0L), ('a', 1L), ('b', 0L), ('b', 1L)]
In [19]: A
Out[19]:
<3x4 sparse matrix of type '<type 'numpy.float64'>'
with 3 stored elements in COOrdinate format>
In [20]: A.todense()
Out[20]:
matrix([[ 0., 0., 1., 2.],
[ 3., 0., 0., 0.],
[ 0., 0., 0., 0.]])
In [21]: ss = SparseSeries.from_coo(A)
In [22]: ss
Out[22]:
0 2 1
3 2
1 0 3
dtype: float64
BlockIndex
Block locations: array([0])
Block lengths: array([3])
Following new methods are accesible via .str accessor to apply the function to each values. This is intended
to make it more consistent with standard methods on strings. (GH9282, GH9352, GH9386, GH9387, GH9439)
Methods
isalnum() isalpha() isdigit() isdigit() isspace()
islower() isupper() istitle() isnumeric() isdecimal()
find() rfind() ljust() rjust() zfill()
In [23]: s = Series(['abcd', '3456', 'EFGH'])
In [24]: s.str.isalpha()
Out[24]:
0 True
1 False
2 True
dtype: bool
In [25]: s.str.find('ab')
Out[25]:
0 0
1 -1
2 -1
dtype: int64
Series.str.pad() and Series.str.center() now accept fillchar option to specify filling char-
acter (GH9352)
In [26]: s = Series(['12', '300', '25'])
Other enhancements
Reindex now supports method=nearest for frames or series with a monotonic increasing or decreasing
index (GH9258):
In [31]: df = pd.DataFrame({'x': range(5)})
This method is also exposed by the lower level Index.get_indexer and Index.get_loc methods.
The read_excel() functions sheetname argument now accepts a list and None, to get multiple or all sheets
respectively. If more than one sheet is specified, a dictionary is returned. (GH9450)
# Returns the 1st and 4th sheet, as a dictionary of DataFrames.
pd.read_excel('path_to_file.xls',sheetname=['Sheet1',3])
Allow Stata files to be read incrementally with an iterator; support for long strings in Stata files. See the docs
here (GH9493:).
Paths beginning with ~ will now be expanded to begin with the users home directory (GH9066)
Added time interval selection in get_data_yahoo (GH9071)
Added Timestamp.to_datetime64() to complement Timedelta.to_timedelta64() (GH9255)
tseries.frequencies.to_offset() now accepts Timedelta as input (GH9064)
Lag parameter was added to the autocorrelation method of Series, defaults to lag-1 autocorrelation (GH9192)
Timedelta will now accept nanoseconds keyword in constructor (GH9273)
SQL code now safely escapes table and column names (GH8986)
Added auto-complete for Series.str.<tab>, Series.dt.<tab> and Series.cat.<tab>
(GH9322)
Index.get_indexer now supports method=pad and method=backfill even for any target ar-
ray, not just monotonic targets. These methods also work for monotonic decreasing as well as monotonic
increasing indexes (GH9258).
Index.asof now works on all index types (GH9258).
A verbose argument has been augmented in io.read_excel(), defaults to False. Set to True to print
sheet names as they are parsed. (GH9450)
Added days_in_month (compatibility alias daysinmonth) property to Timestamp, DatetimeIndex,
Period, PeriodIndex, and Series.dt (GH9572)
Added decimal option in to_csv to provide formatting for non-. decimal separators (GH781)
Added normalize option for Timestamp to normalized to midnight (GH8794)
Added example for DataFrame import to R using HDF5 file and rhdf5 library. See the documentation for
more (GH9636).
Changes in Timedelta
In v0.15.0 a new scalar type Timedelta was introduced, that is a sub-class of datetime.timedelta. Mentioned
here was a notice of an API change w.r.t. the .seconds accessor. The intent was to provide a user-friendly set of
accessors that give the natural value for that unit, e.g. if you had a Timedelta(1 day, 10:11:12), then
.seconds would return 12. However, this is at odds with the definition of datetime.timedelta, which defines
.seconds as 10 * 3600 + 11 * 60 + 12 == 36672.
So in v0.16.0, we are restoring the API to match that of datetime.timedelta. Further, the component values are
still available through the .components accessor. This affects the .seconds and .microseconds accessors,
and removes the .hours, .minutes, .milliseconds accessors. These changes affect TimedeltaIndex and
the Series .dt accessor as well. (GH9185, GH9139)
Previous Behavior
In [2]: t = pd.Timedelta('1 day, 10:11:12.100123')
In [3]: t.days
Out[3]: 1
In [4]: t.seconds
Out[4]: 12
In [5]: t.microseconds
Out[5]: 123
New Behavior
In [33]: t = pd.Timedelta('1 day, 10:11:12.100123')
In [34]: t.days
Out[34]: 1L
In [35]: t.seconds
Out[35]: 36672L
In [36]: t.microseconds
Out[36]: 100123L
In [38]: t.components.seconds
Out[38]: 12L
Indexing Changes
The behavior of a small sub-set of edge cases for using .loc have changed (GH8613). Furthermore we have improved
the content of the error messages that are raised:
Slicing with .loc where the start and/or stop bound is not found in the index is now allowed; this previously
would raise a KeyError. This makes the behavior the same as .ix in this case. This change is only for
slicing, not when indexing with a single label.
In [39]: df = DataFrame(np.random.randn(5,4),
....: columns=list('ABCD'),
....: index=date_range('20130101',periods=5))
....:
In [40]: df
Out[40]:
A B C D
2013-01-01 -0.744471 0.758527 1.729689 -0.964980
2013-01-02 -0.845696 -1.340896 1.846883 -1.328865
2013-01-03 1.682706 -1.717693 0.888782 0.228440
2013-01-04 0.901805 1.171216 0.520260 -1.197071
2013-01-05 -1.066969 -0.303421 -0.858447 0.306996
In [41]: s = Series(range(5),[-2,-1,1,2,3])
In [42]: s
Out[42]:
-2 0
-1 1
1 2
2 3
3 4
dtype: int64
Previous Behavior
In [4]: df.loc['2013-01-02':'2013-01-10']
KeyError: 'stop bound [2013-01-10] is not in the [index]'
In [6]: s.loc[-10:3]
KeyError: 'start bound [-10] is not the [index]'
New Behavior
In [43]: df.loc['2013-01-02':'2013-01-10']
Out[43]:
A B C D
2013-01-02 -0.845696 -1.340896 1.846883 -1.328865
2013-01-03 1.682706 -1.717693 0.888782 0.228440
2013-01-04 0.901805 1.171216 0.520260 -1.197071
In [44]: s.loc[-10:3]
Out[44]:
-2 0
-1 1
1 2
2 3
3 4
dtype: int64
Allow slicing with float-like values on an integer index for .ix. Previously this was only enabled for .loc:
Previous Behavior
In [8]: s.ix[-1.0:2]
TypeError: the slice start value [-1.0] is not a proper indexer for this index type (Int64Index)
New Behavior
In [45]: s.ix[-1.0:2]
Out[45]:
-1 1
1 2
2 3
dtype: int64
Provide a useful exception for indexing with an invalid type for that index when using .loc. For example
trying to use .loc on an index of type DatetimeIndex or PeriodIndex or TimedeltaIndex, with an
integer (or a float).
Previous Behavior
In [4]: df.loc[2:3]
KeyError: 'start bound [2] is not the [index]'
New Behavior
In [4]: df.loc[2:3]
TypeError: Cannot do slice indexing on <class 'pandas.tseries.index.DatetimeIndex'> with <type '
Categorical Changes
In prior versions, Categoricals that had an unspecified ordering (meaning no ordered keyword was passed)
were defaulted as ordered Categoricals. Going forward, the ordered keyword in the Categorical constructor
will default to False. Ordering must now be explicit.
Furthermore, previously you could change the ordered attribute of a Categorical by just setting the at-
tribute, e.g. cat.ordered=True; This is now deprecated and you should use cat.as_ordered() or
cat.as_unordered(). These will by default return a new object and not modify the existing object. (GH9347,
GH9190)
Previous Behavior
In [3]: s = Series([0,1,2], dtype='category')
In [4]: s
Out[4]:
0 0
1 1
2 2
dtype: category
Categories (3, int64): [0 < 1 < 2]
In [5]: s.cat.ordered
Out[5]: True
In [7]: s
Out[7]:
0 0
1 1
2 2
dtype: category
Categories (3, int64): [0, 1, 2]
New Behavior
In [46]: s = Series([0,1,2], dtype='category')
In [47]: s
Out[47]:
0 0
1 1
2 2
dtype: category
Categories (3, int64): [0, 1, 2]
In [48]: s.cat.ordered
Out[48]: False
In [49]: s = s.cat.as_ordered()
In [50]: s
Out[50]:
0 0
1 1
2 2
dtype: category
Categories (3, int64): [0 < 1 < 2]
In [51]: s.cat.ordered
Out[51]: True
In [53]: s
Out[53]:
0 0
1 1
2 2
dtype: category
Categories (3, int64): [0 < 1 < 2]
In [54]: s.cat.ordered
Out[54]: True
For ease of creation of series of categorical data, we have added the ability to pass keywords when calling
.astype(). These are passed directly to the constructor.
In [55]: s = Series(["a","b","c","a"]).astype('category',ordered=True)
In [56]: s
Out[56]:
0 a
1 b
2 c
3 a
dtype: category
Categories (3, object): [a < b < c]
In [57]: s = Series(["a","b","c","a"]).astype('category',categories=list('abcdef'),ordered=False)
In [58]: s
Out[58]:
0 a
1 b
2 c
3 a
dtype: category
Categories (6, object): [a, b, c, d, e, f]
Series now supports bitwise operation for integral types (GH9016). Previously even if the input dtypes were
integral, the output dtype was coerced to bool.
Previous Behavior
In [2]: pd.Series([0,1,2,3], list('abcd')) | pd.Series([4,4,4,4], list('abcd'))
Out[2]:
a True
b True
c True
d True
dtype: bool
New Behavior. If the input dtypes are integral, the output dtype is also integral and the output values are the
result of the bitwise operation.
In [2]: pd.Series([0,1,2,3], list('abcd')) | pd.Series([4,4,4,4], list('abcd'))
Out[2]:
a 4
b 5
c 6
d 7
dtype: int64
During division involving a Series or DataFrame, 0/0 and 0//0 now give np.nan instead of np.inf.
(GH9144, GH8445)
Previous Behavior
In [2]: p = pd.Series([0, 1])
In [3]: p / 0
Out[3]:
0 inf
1 inf
dtype: float64
In [4]: p // 0
Out[4]:
0 inf
1 inf
dtype: float64
New Behavior
In [59]: p = pd.Series([0, 1])
In [60]: p / 0
Out[60]:
0 NaN
1 inf
dtype: float64
In [61]: p // 0
Out[61]:
0 NaN
1 inf
dtype: float64
Series.values_counts and Series.describe for categorical data will now put NaN entries at the
end. (GH9443)
Series.describe for categorical data will now give counts and frequencies of 0, not NaN, for unused
categories (GH9443)
Due to a bug fix, looking up a partial string label with DatetimeIndex.asof now includes values that
match the string, even if they are after the start of the partial string label (GH9258).
Old behavior:
In [4]: pd.to_datetime(['2000-01-31', '2000-02-28']).asof('2000-02')
Out[4]: Timestamp('2000-01-31 00:00:00')
Fixed behavior:
In [62]: pd.to_datetime(['2000-01-31', '2000-02-28']).asof('2000-02')
Out[62]: Timestamp('2000-02-28 00:00:00')
To reproduce the old behavior, simply add more precision to the label (e.g., use 2000-02-01 instead of
2000-02).
Deprecations
The rplot trellis plotting interface is deprecated and will be removed in a future version. We refer to external
packages like seaborn for similar but more refined functionality (GH3445). The documentation includes some
examples how to convert your existing code using rplot to seaborn: rplot docs.
The pandas.sandbox.qtpandas interface is deprecated and will be removed in a future version. We refer
users to the external package pandas-qt. (GH9615)
The pandas.rpy interface is deprecated and will be removed in a future version. Similar functionaility can
be accessed thru the rpy2 project (GH9602)
Adding DatetimeIndex/PeriodIndex to another DatetimeIndex/PeriodIndex is being depre-
cated as a set-operation. This will be changed to a TypeError in a future version. .union() should be used
for the union set operation. (GH9094)
Subtracting DatetimeIndex/PeriodIndex from another DatetimeIndex/PeriodIndex is be-
ing deprecated as a set-operation. This will be changed to an actual numeric subtraction yielding a
TimeDeltaIndex in a future version. .difference() should be used for the differencing set operation.
(GH9094)
DataFrame.pivot_table and crosstabs rows and cols keyword arguments were removed in favor
of index and columns (GH6581)
DataFrame.to_excel and DataFrame.to_csv cols keyword argument was removed in favor of
columns (GH6581)
Removed convert_dummies in favor of get_dummies (GH6581)
Removed value_range in favor of describe (GH6581)
Fixed a performance regression for .loc indexing with an array or list-like (GH9126:).
DataFrame.to_json 30x performance improvement for mixed dtype frames. (GH9037)
Fix bug in DataFrame.Groupby where sort=False is ignored in the case of Categorical columns.
(GH8868)
Fixed bug with reading CSV files from Amazon S3 on python 3 raising a TypeError (GH9452)
Bug in the Google BigQuery reader where the jobComplete key may be present but False in the query results
(GH8728)
Bug in Series.values_counts with excluding NaN for categorical type Series with dropna=True
(GH9443)
Fixed mising numeric_only option for DataFrame.std/var/sem (GH9201)
Support constructing Panel or Panel4D with scalar data (GH8285)
Series text representation disconnected from max_rows/max_columns (GH7508).
Series number formatting inconsistent when truncated (GH8532).
Previous Behavior
In [2]: pd.options.display.max_rows = 10
In [3]: s = pd.Series([1,1,1,1,1,1,1,1,1,1,0.9999,1,1]*10)
In [4]: s
Out[4]:
0 1
1 1
2 1
...
127 0.9999
128 1.0000
129 1.0000
Length: 130, dtype: float64
New Behavior
0 1.0000
1 1.0000
2 1.0000
3 1.0000
4 1.0000
...
125 1.0000
126 1.0000
127 0.9999
128 1.0000
129 1.0000
dtype: float64
A Spurious SettingWithCopy Warning was generated when setting a new item in a frame in some cases
(GH8730)
The following would previously report a SettingWithCopy Warning.
In [1]: df1 = DataFrame({'x': Series(['a','b','c']), 'y': Series(['d','e','f'])})
This is a minor release from 0.15.1 and includes a large number of bug fixes along with several new features, enhance-
ments, and performance improvements. A small number of API changes were necessary to fix existing bugs. We
recommend that all users upgrade to this version.
Enhancements
API Changes
Performance Improvements
Bug Fixes
Indexing in MultiIndex beyond lex-sort depth is now supported, though a lexically sorted index will have a
better performance. (GH2646)
In [1]: df = pd.DataFrame({'jim':[0, 0, 1, 1],
...: 'joe':['x', 'x', 'z', 'y'],
...: 'jolie':np.random.rand(4)}).set_index(['jim', 'joe'])
...:
In [2]: df
Out[2]:
jolie
jim joe
0 x 0.751953
x 0.561512
1 z 0.572214
y 0.740693
In [3]: df.index.lexsort_depth
Out[3]: 1
# lexically sorting
In [5]: df2 = df.sortlevel()
In [6]: df2
Out[6]:
jolie
jim joe
0 x 0.751953
x 0.561512
1 y 0.740693
z 0.572214
In [7]: df2.index.lexsort_depth
Out[7]: 2
In [8]: df2.loc[(1,'z')]
Out[8]:
jolie
jim joe
1 z 0.572214
Bug in unique of Series with category dtype, which returned all categories regardless whether they were
used or not (see GH8559 for the discussion). Previous behaviour was to return all categories:
In [3]: cat = pd.Categorical(['a', 'b', 'a'], categories=['a', 'b', 'c'])
In [4]: cat
Out[4]:
[a, b, a]
Categories (3, object): [a < b < c]
In [5]: cat.unique()
Out[5]: array(['a', 'b', 'c'], dtype=object)
Now, only the categories that do effectively occur in the array are returned:
In [9]: cat = pd.Categorical(['a', 'b', 'a'], categories=['a', 'b', 'c'])
In [10]: cat.unique()
Out[10]: array(['a', 'b'], dtype=object)
Series.all and Series.any now support the level and skipna parameters. Series.all,
Series.any, Index.all, and Index.any no longer support the out and keepdims parameters, which
existed for compatibility with ndarray. Various index types no longer support the all and any aggregation
functions and will now raise TypeError. (GH8302).
Allow equality comparisons of Series with a categorical dtype and object dtype; previously these would raise
TypeError (GH8938)
Bug in NDFrame: conflicting attribute/column names now behave consistently between getting and setting.
Previously, when both a column and attribute named y existed, data.y would return the attribute, while
data.y = z would update the column (GH8994)
In [11]: data = pd.DataFrame({'x':[1, 2, 3]})
In [12]: data.y = 2
In [14]: data
Out[14]:
x y
0 1 2
1 2 4
2 3 6
Old behavior:
In [6]: data.y
Out[6]: 2
In [7]: data['y'].values
Out[7]: array([5, 5, 5])
New behavior:
In [16]: data.y
Out[16]: 5
In [17]: data['y'].values
Out[17]: array([2, 4, 6], dtype=int64)
Timestamp(now) is now equivalent to Timestamp.now() in that it returns the local time rather than
UTC. Also, Timestamp(today) is now equivalent to Timestamp.today() and both have tz as a
possible argument. (GH9000)
Fix negative step support for label-based slices (GH8753)
Old behavior:
In [1]: s = pd.Series(np.arange(3), ['a', 'b', 'c'])
Out[1]:
a 0
b 1
c 2
dtype: int64
In [2]: s.loc['c':'a':-1]
Out[2]:
c 2
dtype: int64
New behavior:
In [18]: s = pd.Series(np.arange(3), ['a', 'b', 'c'])
In [19]: s.loc['c':'a':-1]
Out[19]:
c 2
b 1
a 0
dtype: int32
1.4.2 Enhancements
Categorical enhancements:
Added ability to export Categorical data to Stata (GH8633). See here for limitations of categorical variables
exported to Stata data files.
Added flag order_categoricals to StataReader and read_stata to select whether to order im-
ported categorical data (GH8836). See here for more information on importing categorical variables from Stata
data files.
Added ability to export Categorical data to to/from HDF5 (GH7621). Queries work the same as if it was an
object array. However, the category dtyped data is stored in a more efficient manner. See here for an
example and caveats w.r.t. prior versions of pandas.
Added support for searchsorted() on Categorical class (GH8420).
Other enhancements:
Added the ability to specify the SQL type of columns when writing a DataFrame to a database (GH8778). For
example, specifying to use the sqlalchemy String type instead of the default Text type for string columns:
from sqlalchemy.types import String
data.to_sql('data_dtype', engine, dtype={'Col_1': String})
Series.all and Series.any now support the level and skipna parameters (GH8302):
In [20]: s = pd.Series([False, True, False], index=[0, 0, 1])
In [21]: s.any(level=0)
Out[21]:
0 True
1 False
dtype: bool
Panel now supports the all and any aggregation functions. (GH8302):
In [22]: p = pd.Panel(np.random.rand(2, 5, 4) > 0.1)
In [23]: p.all()
Out[23]:
0 1
0 True False
1 True False
2 False False
3 True True
1.4.3 Performance
Performance boost for to_datetime conversions with a passed format=, and the exact=False
(GH8904)
Bug in concat of Series with category dtype which were coercing to object. (GH8641)
Bug in Timestamp-Timestamp not returning a Timedelta type and datelike-datelike ops with timezones
(GH8865)
Made consistent a timezone mismatch exception (either tz operated with None or incompatible timezone), will
now return TypeError rather than ValueError (a couple of edge cases only), (GH8865)
Bug in using a pd.Grouper(key=...) with no level/axis or level only (GH8795, GH8866)
Report a TypeError when invalid/no paramaters are passed in a groupby (GH8015)
Bug in packaging pandas with py2app/cx_Freeze (GH8602, GH8831)
Bug in groupby signatures that didnt include *args or **kwargs (GH8733).
io.data.Options now raises RemoteDataError when no expiry dates are available from Yahoo and
when it receives no data from Yahoo (GH8761), (GH8783).
Unclear error message in csv parsing when passing dtype and names and the parsed data is a different data type
(GH8833)
Bug in slicing a multi-index with an empty list and at least one boolean indexer (GH8781)
io.data.Options now raises RemoteDataError when no expiry dates are available from Yahoo
(GH8761).
Timedelta kwargs may now be numpy ints and floats (GH8757).
Fixed several outstanding bugs for Timedelta arithmetic and comparisons (GH8813, GH5963, GH5436).
sql_schema now generates dialect appropriate CREATE TABLE statements (GH8697)
slice string method now takes step into account (GH8754)
Bug in BlockManager where setting values with different type would break block integrity (GH8850)
Bug in DatetimeIndex when using time object as key (GH8667)
Bug in merge where how=left and sort=False would not preserve left frame order (GH7331)
Bug in MultiIndex.reindex where reindexing at level would not reorder labels (GH4088)
Bug in certain operations with dateutil timezones, manifesting with dateutil 2.3 (GH8639)
Regression in DatetimeIndex iteration with a Fixed/Local offset timezone (GH8890)
Bug in to_datetime when parsing a nanoseconds using the %f format (GH8989)
io.data.Options now raises RemoteDataError when no expiry dates are available from Yahoo and
when it receives no data from Yahoo (GH8761), (GH8783).
Fix: The font size was only set on x axis if vertical or the y axis if horizontal. (GH8765)
Fixed division by 0 when reading big csv files in python 3 (GH8621)
Bug in outputing a Multindex with to_html,index=False which would add an extra column (GH8452)
Imported categorical variables from Stata files retain the ordinal information in the underlying data (GH8836).
Defined .size attribute across NDFrame objects to provide compat with numpy >= 1.9.1; buggy with
np.array_split (GH8846)
This is a minor bug-fix release from 0.15.0 and includes a small number of API changes, several new features, en-
hancements, and performance improvements along with a large number of bug fixes. We recommend that all users
upgrade to this version.
Enhancements
API Changes
Bug Fixes
s.dt.hour and other .dt accessors will now return np.nan for missing values (rather than previously -1),
(GH8689)
In [1]: s = Series(date_range('20130101',periods=5,freq='D'))
In [3]: s
Out[3]:
0 2013-01-01
1 2013-01-02
2 NaT
3 2013-01-04
4 2013-01-05
dtype: datetime64[ns]
previous behavior:
In [6]: s.dt.hour
Out[6]:
0 0
1 0
2 -1
3 0
4 0
dtype: int64
current behavior:
In [4]: s.dt.hour
Out[4]:
0 0
1 0
2 NaN
3 0
4 0
dtype: float64
groupby with as_index=False will not add erroneous extra columns to result (GH8582):
In [5]: np.random.seed(2718281)
In [7]: df.head()
Out[7]:
jim joe
0 61 81
1 96 49
2 55 65
3 72 51
4 77 12
previous behavior:
In [4]: df.groupby(ts, as_index=False).max()
Out[4]:
NaN jim joe
0 0 72 83
1 5 77 84
2 10 96 65
current behavior:
In [9]: df.groupby(ts, as_index=False).max()
Out[9]:
jim joe
0 72 83
1 77 84
2 96 65
groupby will not erroneously exclude columns if the column name conflics with the grouper name (GH8112):
In [10]: df = pd.DataFrame({'jim': range(5), 'joe': range(5, 10)})
In [11]: df
Out[11]:
jim joe
0 0 5
1 1 6
2 2 7
3 3 8
4 4 9
current behavior:
In [13]: gr.apply(sum)
Out[13]:
jim joe
jim
False 9 24
True 1 11
Support for slicing with monotonic decreasing indexes, even if start or stop is not found in the index
(GH7860):
In [14]: s = pd.Series(['a', 'b', 'c', 'd'], [4, 3, 2, 1])
In [15]: s
Out[15]:
4 a
3 b
2 c
1 d
dtype: object
previous behavior:
In [8]: s.loc[3.5:1.5]
KeyError: 3.5
current behavior:
In [16]: s.loc[3.5:1.5]
Out[16]:
3 b
2 c
dtype: object
io.data.Options has been fixed for a change in the format of the Yahoo Options page (GH8612),
(GH8741)
Note: As a result of a change in Yahoos option page layout, when an expiry date is given, Options methods
now return data for a single expiry date. Previously, methods returned all data for the selected month.
The month and year parameters have been undeprecated and can be used to get all options data for a given
month.
If an expiry date that is not valid is given, data for the next expiry after the given date is returned.
Option data frames are now saved on the instance as callsYYMMDD or putsYYMMDD. Previously they were
saved as callsMMYY and putsMMYY. The next expiry is saved as calls and puts.
New features:
The expiry parameter can now be a single date or a list-like object containing dates.
A new property expiry_dates was added, which returns all available expiry dates.
Current behavior:
In [17]: from pandas.io.data import Options
In [19]: aapl.get_call_data().iloc[0:5,0:1]
Out[19]:
Last
Strike Expiry Type Symbol
65 2015-06-19 call AAPL150619C00065000 64.25
70 2015-06-19 call AAPL150619C00070000 60.72
75 2015-06-19 call AAPL150619C00075000 57.21
80 2015-06-19 call AAPL150619C00080000 47.50
85 2015-06-19 call AAPL150619C00085000 42.50
In [20]: aapl.expiry_dates
Out[20]:
[datetime.date(2015, 6, 19),
datetime.date(2015, 6, 26),
datetime.date(2015, 7, 2),
datetime.date(2015, 7, 10),
datetime.date(2015, 7, 17),
datetime.date(2015, 7, 24),
datetime.date(2015, 7, 31),
datetime.date(2015, 8, 21),
datetime.date(2015, 10, 16),
datetime.date(2015, 12, 18),
datetime.date(2016, 1, 15),
datetime.date(2016, 6, 17),
datetime.date(2017, 1, 20)]
In [21]: aapl.get_near_stock_price(expiry=aapl.expiry_dates[0:3]).iloc[0:5,0:1]
Out[21]:
Last
Strike Expiry Type Symbol
127 2015-06-26 call AAPL150626C00127000 2.00
2015-07-02 call AAPL150702C00127000 2.36
128 2015-06-19 call AAPL150619C00128000 0.88
2015-06-26 call AAPL150626C00128000 1.48
2015-07-02 call AAPL150702C00128000 1.88
1.5.2 Enhancements
concat permits a wider variety of iterables of pandas objects to be passed as the first parameter (GH8645):
In [22]: from collections import deque
previous behavior:
In [7]: pd.concat(deque((df1, df2)))
TypeError: first argument must be a list-like of pandas objects, you passed an object of type "d
current behavior:
In [25]: pd.concat(deque((df1, df2)))
Out[25]:
0
0 1
1 2
2 3
0 4
1 5
2 6
Represent MultiIndex labels with a dtype that utilizes memory based on the level size. In prior versions,
the memory usage was a constant 8 bytes per element in each level. In addition, in prior versions, the reported
memory usage was incorrect as it didnt show the usage for the memory occupied by the underling data array.
(GH8456)
In [26]: dfi = DataFrame(1,index=pd.MultiIndex.from_product([['a'],range(1000)]),columns=['A'])
previous behavior:
# this was underreported in prior versions
In [1]: dfi.memory_usage(index=True)
Out[1]:
Index 8000 # took about 24008 bytes in < 0.15.1
A 8000
dtype: int64
current behavior:
In [27]: dfi.memory_usage(index=True)
Out[27]:
Index 11020
A 8000
dtype: int64
Bug in read_csv, dialect parameter would not take a string (:issue: 8703)
Bug in slicing a multi-index level with an empty-list (GH8737)
Bug in numeric index operations of add/sub with Float/Index Index with numpy arrays (GH8608)
Bug in setitem with empty indexer and unwanted coercion of dtypes (GH8669)
Bug in ix/loc block splitting on setitem (manifests with integer-like dtypes, e.g. datetime64) (GH8607)
Bug when doing label based indexing with integers not found in the index for non-unique but monotonic indexes
(GH8680).
Bug when indexing a Float64Index with np.nan on numpy 1.7 (GH8980).
Fix shape attribute for MultiIndex (GH8609)
Bug in GroupBy where a name conflict between the grouper and columns would break groupby operations
(GH7115, GH8112)
Fixed a bug where plotting a column y and specifying a label would mutate the index name of the original
DataFrame (GH8494)
Fix regression in plotting of a DatetimeIndex directly with matplotlib (GH8614).
Bug in date_range where partially-specified dates would incorporate current date (GH6961)
Bug in Setting by indexer to a scalar value with a mixed-dtype Panel4d was failing (GH8702)
Bug where DataReaders would fail if one of the symbols passed was invalid. Now returns data for valid
symbols and np.nan for invalid (GH8494)
Bug in get_quote_yahoo that wouldnt allow non-float return values (GH5229).
This is a major release from 0.14.1 and includes a small number of API changes, several new features, enhancements,
and performance improvements along with a large number of bug fixes. We recommend that all users upgrade to this
version.
Warning: pandas >= 0.15.0 will no longer support compatibility with NumPy versions < 1.7.0. If you want to
use the latest versions of pandas, please upgrade to NumPy >= 1.7.0 (GH7711)
Highlights include:
The Categorical type was integrated as a first-class pandas type, see here
New scalar type Timedelta, and a new index type TimedeltaIndex, see here
New datetimelike properties accessor .dt for Series, see Datetimelike Properties
New DataFrame default display for df.info() to include memory usage, see Memory Usage
read_csv will now by default ignore blank lines when parsing, see here
API change in using Indexes in set operations, see here
Enhancements in the handling of timezones, see here
A lot of improvements to the rolling and expanding moment funtions, see here
Internal refactoring of the Index class to no longer sub-class ndarray, see Internal Refactoring
dropping support for PyTables less than version 3.0.0, and numexpr less than version 2.1 (GH7990)
Split indexing documentation into Indexing and Selecting Data and MultiIndex / Advanced Indexing
Split out string methods documentation into Working with Text Data
Check the API Changes and deprecations before updating
Other Enhancements
Performance Improvements
Bug Fixes
Warning: In 0.15.0 Index has internally been refactored to no longer sub-class ndarray but instead subclass
PandasObject, similarly to the rest of the pandas objects. This change allows very easy sub-classing and
creation of new index types. This should be a transparent change with only very limited API implications (See the
Internal Refactoring)
Warning: The refactorings in Categorical changed the two argument constructor from codes/labels and
levels to values and levels (now called categories). This can lead to subtle bugs. If you use Categorical
directly, please audit your code before updating to this pandas version and change it to use the from_codes()
constructor. See more on Categorical here
Categoricals in Series/DataFrame
Categorical can now be included in Series and DataFrames and gained new methods to manipulate. Thanks to Jan
Schulz for much of this API/implementation. (GH3943, GH5313, GH5314, GH7444, GH7839, GH7848, GH7864,
GH7914, GH7768, GH8006, GH3678, GH8075, GH8076, GH8143, GH8453, GH8518).
For full docs, see the categorical introduction and the API documentation.
In [1]: df = DataFrame({"id":[1,2,3,4,5,6], "raw_grade":['a', 'b', 'b', 'a', 'a', 'e']})
In [3]: df["grade"]
Out[3]:
0 a
1 b
2 b
3 a
4 a
5 e
Name: grade, dtype: category
Categories (3, object): [a, b, e]
In [6]: df["grade"]
Out[6]:
0 very good
1 good
2 good
3 very good
4 very good
5 very bad
Name: grade, dtype: category
Categories (5, object): [very bad, bad, medium, good, very good]
In [7]: df.sort("grade")
Out[7]:
id raw_grade grade
5 6 e very bad
1 2 b good
2 3 b good
0 1 a very good
3 4 a very good
4 5 a very good
In [8]: df.groupby("grade").size()
Out[8]:
grade
very bad 1
bad NaN
medium NaN
good 2
very good 3
dtype: float64
TimedeltaIndex/Scalar
We introduce a new scalar type Timedelta, which is a subclass of datetime.timedelta, and behaves in a
similar manner, but allows compatibility with np.timedelta64 types as well as a host of custom representation,
parsing, and attributes. This type is very similar to how Timestamp works for datetimes. It is a nice-API box for
the type. See the docs. (GH3009, GH4533, GH8209, GH8187, GH8190, GH7869, GH7661, GH8345, GH8471)
Warning: Timedelta scalars (and TimedeltaIndex) component fields are not the same as the component
fields on a datetime.timedelta object. For example, .seconds on a datetime.timedelta object
returns the total number of seconds combined between hours, minutes and seconds. In contrast, the pandas
Timedelta breaks out hours, minutes, microseconds and nanoseconds separately.
# Timedelta accessor
In [9]: tds = Timedelta('31 days 5 min 3 sec')
In [10]: tds.minutes
Out[10]: 5L
In [11]: tds.seconds
Out[11]: 3L
# datetime.timedelta accessor
# this is 5 minutes * 60 + 3 seconds
In [12]: tds.to_pytimedelta().seconds
Out[12]: 303
Note: this is no longer true starting from v0.16.0, where full compatibility with datetime.timedelta is
introduced. See the 0.16.0 whatsnew entry
Warning: Prior to 0.15.0 pd.to_timedelta would return a Series for list-like/Series input, and a
np.timedelta64 for scalar input. It will now return a TimedeltaIndex for list-like input, Series for
Series input, and Timedelta for scalar input.
The arguments to pd.to_timedelta are now (arg,unit=ns,box=True,coerce=False), previ-
ously were (arg,box=True,unit=ns) as these are more logical.
Consruct a scalar
In [9]: Timedelta('1 days 06:05:01.00003')
Out[9]: Timedelta('1 days 06:05:01.000030')
In [10]: Timedelta('15.5us')
Out[10]: Timedelta('0 days 00:00:00.000015')
# a NaT
In [13]: Timedelta('nan')
Out[13]: NaT
In [15]: td.seconds
Out[15]: 3780L
In [16]: td.microseconds
Out[16]: 15L
In [17]: td.nanoseconds
Out[17]: 500L
Construct a TimedeltaIndex
In [18]: TimedeltaIndex(['1 days','1 days, 00:00:05',
....: np.timedelta64(2,'D'),timedelta(days=2,seconds=2)])
....:
Out[18]:
TimedeltaIndex(['1 days 00:00:00', '1 days 00:00:05', '2 days 00:00:00',
'2 days 00:00:02'],
dtype='timedelta64[ns]', freq=None)
In [22]: s
Out[22]:
1 days 00:00:00 0
1 days 00:00:01 1
1 days 00:00:02 2
1 days 00:00:03 3
1 days 00:00:04 4
Freq: S, dtype: int32
Finally, the combination of TimedeltaIndex with DatetimeIndex allow certain combination operations that
are NaT preserving:
In [25]: tdi = TimedeltaIndex(['1 days',pd.NaT,'2 days'])
In [26]: tdi.tolist()
Out[26]: [Timedelta('1 days 00:00:00'), NaT, Timedelta('2 days 00:00:00')]
In [28]: dti.tolist()
Out[28]:
[Timestamp('2013-01-01 00:00:00', offset='D'),
Timestamp('2013-01-02 00:00:00', offset='D'),
Timestamp('2013-01-03 00:00:00', offset='D')]
Memory Usage
Implemented methods to find memory usage of a DataFrame. See the FAQ for more. (GH6852).
A new display option display.memory_usage (see Options and Settings) sets the default behavior of the
memory_usage argument in the df.info() method. By default display.memory_usage is True.
In [31]: dtypes = ['int64', 'float64', 'datetime64[ns]', 'timedelta64[ns]',
....: 'complex128', 'object', 'bool']
....:
In [32]: n = 5000
In [34]: df = DataFrame(data)
In [36]: df.info()
<class 'pandas.core.frame.DataFrame'>
Int64Index: 5000 entries, 0 to 4999
Data columns (total 8 columns):
bool 5000 non-null bool
Additionally memory_usage() is an available method for a dataframe object which returns the memory usage of
each column.
In [37]: df.memory_usage(index=True)
Out[37]:
Index 40000
bool 5000
complex128 80000
datetime64[ns] 40000
float64 40000
int64 40000
object 20000
timedelta64[ns] 40000
categorical 5800
dtype: int64
.dt accessor
Series has gained an accessor to succinctly return datetime like properties for the values of the Series, if its a
datetime/period like Series. (GH7207) This will return a Series, indexed like the existing Series. See the docs
# datetime
In [38]: s = Series(date_range('20130101 09:10:12',periods=4))
In [39]: s
Out[39]:
0 2013-01-01 09:10:12
1 2013-01-02 09:10:12
2 2013-01-03 09:10:12
3 2013-01-04 09:10:12
dtype: datetime64[ns]
In [40]: s.dt.hour
Out[40]:
0 9
1 9
2 9
3 9
dtype: int64
In [41]: s.dt.second
Out[41]:
0 12
1 12
2 12
3 12
dtype: int64
In [42]: s.dt.day
Out[42]:
0 1
1 2
2 3
3 4
dtype: int64
In [43]: s.dt.freq
Out[43]: <Day>
In [46]: stz
Out[46]:
0 2013-01-01 09:10:12-05:00
1 2013-01-02 09:10:12-05:00
2 2013-01-03 09:10:12-05:00
3 2013-01-04 09:10:12-05:00
dtype: object
In [47]: stz.dt.tz
Out[47]: <DstTzInfo 'US/Eastern' LMT-1 day, 19:04:00 STD>
In [50]: s
Out[50]:
0 2013-01-01
1 2013-01-02
2 2013-01-03
3 2013-01-04
dtype: object
In [51]: s.dt.year
Out[51]:
0 2013
1 2013
2 2013
3 2013
dtype: int64
In [52]: s.dt.day
Out[52]:
0 1
1 2
2 3
3 4
dtype: int64
# timedelta
In [53]: s = Series(timedelta_range('1 day 00:00:05',periods=4,freq='s'))
In [54]: s
Out[54]:
0 1 days 00:00:05
1 1 days 00:00:06
2 1 days 00:00:07
3 1 days 00:00:08
dtype: timedelta64[ns]
In [55]: s.dt.days
Out[55]:
0 1
1 1
2 1
3 1
dtype: int64
In [56]: s.dt.seconds
Out[56]:
0 5
1 6
2 7
3 8
dtype: int64
In [57]: s.dt.components
Out[57]:
days hours minutes seconds milliseconds microseconds nanoseconds
0 1 0 0 5 0 0 0
1 1 0 0 6 0 0 0
2 1 0 0 7 0 0 0
3 1 0 0 8 0 0 0
tz_localize(None) for tz-aware Timestamp and DatetimeIndex now removes timezone holding
local time, previously this resulted in Exception or TypeError (GH7812)
In [58]: ts = Timestamp('2014-08-01 09:00', tz='US/Eastern')
In [59]: ts
Out[59]: Timestamp('2014-08-01 09:00:00-0400', tz='US/Eastern')
In [60]: ts.tz_localize(None)
Out[60]: Timestamp('2014-08-01 09:00:00')
In [62]: didx
Out[62]:
DatetimeIndex(['2014-08-01 09:00:00-04:00', '2014-08-01 10:00:00-04:00',
'2014-08-01 11:00:00-04:00', '2014-08-01 12:00:00-04:00',
'2014-08-01 13:00:00-04:00', '2014-08-01 14:00:00-04:00',
'2014-08-01 15:00:00-04:00', '2014-08-01 16:00:00-04:00',
'2014-08-01 17:00:00-04:00', '2014-08-01 18:00:00-04:00'],
dtype='datetime64[ns]', freq='H', tz='US/Eastern')
In [63]: didx.tz_localize(None)
Out[63]:
DatetimeIndex(['2014-08-01 09:00:00', '2014-08-01 10:00:00',
'2014-08-01 11:00:00', '2014-08-01 12:00:00',
'2014-08-01 13:00:00', '2014-08-01 14:00:00',
'2014-08-01 15:00:00', '2014-08-01 16:00:00',
'2014-08-01 17:00:00', '2014-08-01 18:00:00'],
dtype='datetime64[ns]', freq='H', tz=None)
tz_localize now accepts the ambiguous keyword which allows for passing an array of bools indicating
whether the date belongs in DST or not, NaT for setting transition times to NaT, infer for inferring DST/non-
DST, and raise (default) for an AmbiguousTimeError to be raised. See the docs for more details (GH7943)
DataFrame.tz_localize and DataFrame.tz_convert now accepts an optional level argument
for localizing a specific level of a MultiIndex (GH7846)
Timestamp.tz_localize and Timestamp.tz_convert now raise TypeError in error cases, rather
than Exception (GH8025)
a timeseries/index localized to UTC when inserted into a Series/DataFrame will preserve the UTC timezone
(rather than being a naive datetime64[ns]) as object dtype (GH8411)
Timestamp.__repr__ displays dateutil.tz.tzoffset info (GH7907)
New behavior
In [65]: rolling_min(s, window=10, min_periods=5)
Out[65]:
0 NaN
1 NaN
2 NaN
3 NaN
dtype: float64
rolling_window() now normalizes the weights properly in rolling mean mode (mean=True) so that the
calculated weighted means (e.g. triang, gaussian) are distributed about the same means as those calculated
without weighting (i.e. boxcar). See the note on normalization for further details. (GH7618)
In [67]: s = Series([10.5, 8.8, 11.4, 9.7, 9.3])
New behavior
In [68]: rolling_window(s, window=3, win_type='triang', center=True)
Out[68]:
0 NaN
1 9.875
2 10.325
3 10.025
4 NaN
dtype: float64
Removed center argument from all expanding_ functions (see list), as the results produced when
center=True did not make much sense. (GH7925)
Added optional ddof argument to expanding_cov() and rolling_cov(). The default value of 1 is
backwards-compatible. (GH8279)
Documented the ddof argument to expanding_var(), expanding_std(), rolling_var(), and
rolling_std(). These functions support of a ddof argument (with a default value of 1) was previously
undocumented. (GH8064)
ewma(), ewmstd(), ewmvol(), ewmvar(), ewmcov(), and ewmcorr() now interpret min_periods
in the same manner that the rolling_*() and expanding_*() functions do: a given result entry will be
NaN if the (expanding, in this case) window does not contain at least min_periods values. The previous
behavior was to set to NaN the min_periods entries starting with the first non- NaN value. (GH7977)
Prior behavior (note values start at index 2, which is min_periods after index 0 (the index of the first non-
empty value)):
In [69]: s = Series([1, None, None, None, 2, 3])
New behavior (note values start at index 4, the location of the 2nd (since min_periods=2) non-empty value):
In [70]: ewma(s, com=3., min_periods=2)
Out[70]:
0 NaN
1 NaN
2 NaN
3 NaN
4 1.759644
5 2.383784
dtype: float64
ewmstd(), ewmvol(), ewmvar(), ewmcov(), and ewmcorr() now have an optional adjust argu-
ment, just like ewma() does, affecting how the weights are calculated. The default value of adjust is True,
which is backwards-compatible. See Exponentially weighted moment functions for details. (GH7911)
ewma(), ewmstd(), ewmvol(), ewmvar(), ewmcov(), and ewmcorr() now have an optional
ignore_na argument. When ignore_na=False (the default), missing values are taken into account in
the weights calculation. When ignore_na=True (which reproduces the pre-0.15.0 behavior), missing values
are ignored in the weights calculation. (GH7543)
In [71]: ewma(Series([None, 1., 8.]), com=2.)
Out[71]:
0 NaN
1 1.0
2 5.2
dtype: float64
0 1.0
1 1.0
2 5.2
dtype: float64
Warning: By default (ignore_na=False) the ewm*() functions weights calculation in the presence
of missing values is different than in pre-0.15.0 versions. To reproduce the pre-0.15.0 calculation of weights
in the presence of missing values one must specify explicitly ignore_na=True.
Note that entry 0 is approximately 0, and the debiasing factors are a constant 1.25. By comparison, the following
0.15.0 results have a NaN for entry 0, and the debiasing factors are decreasing (towards 1.25):
In [75]: ewmvar(s, com=2., bias=False)
Out[75]:
0 NaN
1 0.500000
2 1.210526
3 4.089069
dtype: float64
Added support for a chunksize parameter to to_sql function. This allows DataFrame to be written in
chunks and avoid packet-size overflow errors (GH8062).
Added support for a chunksize parameter to read_sql function. Specifying this argument will return an
iterator through chunks of the query result (GH2908).
Added support for writing datetime.date and datetime.time object columns with to_sql (GH6932).
Added support for specifying a schema to read from/write to with read_sql_table and to_sql
(GH7441, GH7952). For example:
df.to_sql('table', engine, schema='other_schema')
pd.read_sql_table('table', engine, schema='other_schema')
Breaking changes
API changes related to the introduction of the Timedelta scalar (see above for more details):
Prior to 0.15.0 to_timedelta() would return a Series for list-like/Series input, and a
np.timedelta64 for scalar input. It will now return a TimedeltaIndex for list-like input, Series
for Series input, and Timedelta for scalar input.
For API changes related to the rolling and expanding functions, see detailed overview above.
Other notable API changes:
Consistency when indexing with .loc and a list-like indexer when no values are found.
In [77]: df = DataFrame([['a'],['b']],index=[1,2])
In [78]: df
Out[78]:
0
1 a
2 b
In [80]: df.loc[[1,3],:]
Out[80]:
0
1 a
3 NaN
In [82]: p
Out[82]:
<class 'pandas.core.panel.Panel'>
Dimensions: 2 (items) x 3 (major_axis) x 4 (minor_axis)
Items axis: ItemA to ItemB
Major_axis axis: 1 to 3
Minor_axis axis: A to D
Furthermore, .loc will raise If no values are found in a multi-index with a list-like indexer:
In [84]: s = Series(np.arange(3,dtype='int64'),
....: index=MultiIndex.from_product([['A'],['foo','bar','baz']],
....: names=['one','two'])
....: ).sortlevel()
....:
In [85]: s
Out[85]:
one two
A bar 1
baz 2
foo 0
dtype: int64
In [86]: try:
....: s.loc[['D']]
....: except KeyError as e:
....: print("KeyError: " + str(e))
....:
KeyError: 'cannot index a multi-index axis with these keys'
Assigning values to None now considers the dtype when choosing an empty value (GH7941).
Previously, assigning to None in numeric containers changed the dtype to object (or errored, depending on the
call). It now uses NaN:
In [87]: s = Series([1, 2, 3])
In [89]: s
Out[89]:
0 NaN
1 2
2 3
dtype: float64
In [92]: s
Out[92]:
0 None
1 b
2 c
dtype: object
To insert a NaN, you must explicitly use np.nan. See the docs.
In prior versions, updating a pandas object inplace would not reflect in other python references to this object.
(GH8511, GH5104)
In [93]: s = Series([1, 2, 3])
In [94]: s2 = s
In [95]: s += 1.5
Made both the C-based and Python engines for read_csv and read_table ignore empty lines in input as well as
whitespace-filled lines, as long as sep is not whitespace. This is an API change that can be controlled by the
keyword parameter skip_blank_lines. See the docs (GH4466)
A timeseries/index localized to UTC when inserted into a Series/DataFrame will preserve the UTC timezone
and inserted as object dtype rather than being converted to a naive datetime64[ns] (GH8411).
Bug in passing a DatetimeIndex with a timezone that was not being retained in DataFrame construction
from a dict (GH7822)
In prior versions this would drop the timezone, now it retains the timezone, but gives a column of object
dtype:
In [98]: i = date_range('1/1/2011', periods=3, freq='10s', tz = 'US/Eastern')
In [99]: i
Out[99]:
DatetimeIndex(['2011-01-01 00:00:00-05:00', '2011-01-01 00:00:10-05:00',
'2011-01-01 00:00:20-05:00'],
dtype='datetime64[ns]', freq='10S', tz='US/Eastern')
In [101]: df
Out[101]:
a
0 2011-01-01 00:00:00-05:00
1 2011-01-01 00:00:10-05:00
2 2011-01-01 00:00:20-05:00
In [102]: df.dtypes
Out[102]:
a object
dtype: object
Previously this would have yielded a column of datetime64 dtype, but without timezone info.
The behaviour of assigning a column to an existing dataframe as df[a] = i remains unchanged (this already
returned an object column with a timezone).
When passing multiple levels to stack(), it will now raise a ValueError when the levels arent all level
names or all level numbers (GH7660). See Reshaping by stacking and unstacking.
Raise a ValueError in df.to_hdf with fixed format, if df has non-unique columns as the resulting file
will be broken (GH7761)
SettingWithCopy raise/warnings (according to the option mode.chained_assignment) will now be
issued when setting a value on a sliced mixed-dtype DataFrame using chained-assignment. (GH7845, GH7950)
In [1]: df = DataFrame(np.arange(0,9), columns=['count'])
merge, DataFrame.merge, and ordered_merge now return the same type as the left argument
(GH7737).
Previously an enlargement with a mixed-dtype frame would act unlike .append which will preserve dtypes
(related GH2578, GH8176):
In [103]: df = DataFrame([[True, 1],[False, 2]],
.....: columns=["female","fitness"])
.....:
In [104]: df
Out[104]:
female fitness
0 True 1
1 False 2
In [105]: df.dtypes
Out[105]:
female bool
fitness int64
dtype: object
In [107]: df
Out[107]:
female fitness
0 True 1
1 False 2
2 False 2
In [108]: df.dtypes
Out[108]:
female bool
fitness int64
dtype: object
Internal Refactoring
In 0.15.0 Index has internally been refactored to no longer sub-class ndarray but instead subclass
PandasObject, similarly to the rest of the pandas objects. This change allows very easy sub-classing and cre-
ation of new index types. This should be a transparent change with only very limited API implications (GH5080,
GH7439, GH7796, GH8024, GH8367, GH7997, GH8522):
you may need to unpickle pandas version < 0.15.0 pickles using pd.read_pickle rather than
pickle.load. See pickle docs
when plotting with a PeriodIndex, the matplotlib internal axes will now be arrays of Period rather than a
PeriodIndex (this is similar to how a DatetimeIndex passes arrays of datetimes now)
MultiIndexes will now raise similary to other pandas objects w.r.t. truth testing, see here (GH7897).
When plotting a DatetimeIndex directly with matplotlibs plot function, the axis labels will no longer be format-
ted as dates but as integers (the internal representation of a datetime64). UPDATE This is fixed in 0.15.1,
see here.
Deprecations
The attributes Categorical labels and levels attributes are deprecated and renamed to codes and
categories.
The outtype argument to pd.DataFrame.to_dict has been deprecated in favor of orient. (GH7840)
The convert_dummies method has been deprecated in favor of get_dummies (GH8140)
The infer_dst argument in tz_localize will be deprecated in favor of ambiguous to allow for more
flexibility in dealing with DST transitions. Replace infer_dst=True with ambiguous=infer for the
same behavior (GH7943). See the docs for more details.
The top-level pd.value_range has been deprecated and can be replaced by .describe() (GH8481)
The Index set operations + and - were deprecated in order to provide these for numeric type operations on
certain index types. + can be replaced by .union() or |, and - by .difference(). Further the method
name Index.diff() is deprecated and can be replaced by Index.difference() (GH8226)
# +
Index(['a','b','c']) + Index(['b','c','d'])
# should be replaced by
Index(['a','b','c']).union(Index(['b','c','d']))
# -
Index(['a','b','c']) - Index(['b','c','d'])
# should be replaced by
Index(['a','b','c']).difference(Index(['b','c','d']))
The infer_types argument to read_html() now has no effect and is deprecated (GH7762, GH7032).
1.6.3 Enhancements
read_stata and StataReader can import missing data information into a DataFrame by setting
the argument convert_missing to True. When using this options, missing values are returned as
StataMissingValue objects and columns containing missing values have object data type. (GH8045)
Enhancements in the plotting functions:
Added layout keyword to DataFrame.plot. You can pass a tuple of (rows, columns), one of which
can be -1 to automatically infer (GH6667, GH8071).
Allow to pass multiple axes to DataFrame.plot, hist and boxplot (GH5353, GH6970, GH7069)
Added support for c, colormap and colorbar arguments for DataFrame.plot with
kind=scatter (GH7780)
Histogram from DataFrame.plot with kind=hist (GH7809), See the docs.
Boxplot from DataFrame.plot with kind=box (GH7998), See the docs.
Other:
read_csv now has a keyword parameter float_precision which specifies which floating-point converter
the C engine should use during parsing, see here (GH8002, GH8044)
Added searchsorted method to Series objects (GH7447)
describe() on mixed-types DataFrames is more flexible. Type-based column filtering is now possible via
the include/exclude arguments. See the docs (GH8164).
In [109]: df = DataFrame({'catA': ['foo', 'foo', 'bar'] * 8,
.....: 'catB': ['a', 'b', 'c', 'd'] * 6,
.....: 'numC': np.arange(24),
.....: 'numD': np.arange(24.) + .5})
.....:
In [110]: df.describe(include=["object"])
Out[110]:
catA catB
count 24 24
unique 2 4
top foo d
freq 16 6
Without those arguments, describe will behave as before, including only numerical columns or, if none are,
only categorical columns. See also the docs
Added split as an option to the orient argument in pd.DataFrame.to_dict. (GH7840)
The get_dummies method can now be used on DataFrames. By default only catagorical columns are encoded
as 0s and 1s, while other columns are left untouched.
In [113]: df = DataFrame({'A': ['a', 'b', 'a'], 'B': ['c', 'c', 'b'],
.....: 'C': [1, 2, 3]})
.....:
In [114]: pd.get_dummies(df)
Out[114]:
C A_a A_b B_b B_c
0 1 1 0 0 1
1 2 0 1 0 1
2 3 1 0 1 0
# get the first, 4th, and last date index for each month
In [117]: df.groupby((df.index.year, df.index.month)).nth([0, 3, -1])
Out[117]:
a b
2014-04-01 1 1
2014-04-04 1 1
2014-04-30 1 1
2014-05-01 1 1
2014-05-06 1 1
2014-05-30 1 1
2014-06-02 1 1
2014-06-05 1 1
2014-06-30 1 1
If Period freq is D, H, T, S, L, U, N, Timedelta-like can be added if the result can have same freq. Otherwise,
only the same offsets can be added.
In [118]: idx = pd.period_range('2014-07-01 09:00', periods=5, freq='H')
In [119]: idx
Out[119]:
PeriodIndex(['2014-07-01 09:00', '2014-07-01 10:00', '2014-07-01 11:00',
'2014-07-01 12:00', '2014-07-01 13:00'],
dtype='int64', freq='H')
In [123]: idx
Out[123]: PeriodIndex(['2014-07', '2014-08', '2014-09', '2014-10', '2014-11'], dtype='int64', fr
Added experimental compatibility with openpyxl for versions >= 2.0. The DataFrame.to_excel method
engine keyword now recognizes openpyxl1 and openpyxl2 which will explicitly require openpyxl v1
and v2 respectively, failing if the requested version is not available. The openpyxl engine is a now a meta-
engine that automatically uses whichever version of openpyxl is installed. (GH7177)
DataFrame.fillna can now accept a DataFrame as a fill value (GH8377)
Passing multiple levels to stack() will now work when multiple level numbers are passed (GH7660). See
Reshaping by stacking and unstacking.
set_names(), set_labels(), and set_levels() methods now take an optional level keyword ar-
gument to all modification of specific level(s) of a MultiIndex. Additionally set_names() now accepts a
scalar string value when operating on an Index or on a specific level of a MultiIndex (GH7792)
In [125]: idx = MultiIndex.from_product([['a'], range(3), list("pqr")], names=['foo', 'bar', 'ba
Out[128]:
MultiIndex(levels=[[u'a'], [u'a', u'b', u'c'], [u'p', u'q', u'r']],
labels=[[0, 0, 0, 0, 0, 0, 0, 0, 0], [0, 0, 0, 1, 1, 1, 2, 2, 2], [0, 1, 2, 0, 1, 2,
names=[u'foo', u'bar', u'baz'])
Index.isin now supports a level argument to specify which index level to use for membership tests
(GH7892, GH7890)
In [1]: idx = MultiIndex.from_product([[0, 1], ['a', 'b', 'c']])
In [2]: idx.values
Out[2]: array([(0, 'a'), (0, 'b'), (0, 'c'), (1, 'a'), (1, 'b'), (1, 'c')], dtype=object)
In [131]: idx
Out[131]: Int64Index([1, 2, 3, 4, 1, 2], dtype='int64')
In [132]: idx.duplicated()
Out[132]: array([False, False, False, False, True, True], dtype=bool)
In [133]: idx.drop_duplicates()
Out[133]: Int64Index([1, 2, 3, 4], dtype='int64')
add copy=True argument to pd.concat to enable pass thru of complete blocks (GH8252)
Added support for numpy 1.8+ data types (bool_, int_, float_, string_) for conversion to R dataframe
(GH8400)
1.6.4 Performance
Bug in get where an IndexError would not cause the default value to be returned (GH7725)
Bug in offsets.apply, rollforward and rollback may reset nanosecond (GH7697)
Bug in offsets.apply, rollforward and rollback may raise AttributeError if Timestamp
has dateutil tzinfo (GH7697)
Bug in sorting a multi-index frame with a Float64Index (GH8017)
Bug in inconsistent panel setitem with a rhs of a DataFrame for alignment (GH7763)
Bug in is_superperiod and is_subperiod cannot handle higher frequencies than S (GH7760, GH7772,
GH7803)
Bug in 32-bit platforms with Series.shift (GH8129)
Bug in PeriodIndex.unique returns int64 np.ndarray (GH7540)
Bug in groupby.apply with a non-affecting mutation in the function (GH8467)
Bug in DataFrame.reset_index which has MultiIndex contains PeriodIndex or
DatetimeIndex with tz raises ValueError (GH7746, GH7793)
Bug in DataFrame.plot with subplots=True may draw unnecessary minor xticks and yticks (GH7801)
Bug in StataReader which did not read variable labels in 117 files due to difference between Stata docu-
mentation and implementation (GH7816)
Bug in StataReader where strings were always converted to 244 characters-fixed width irrespective of un-
derlying string size (GH7858)
Bug in DataFrame.plot and Series.plot may ignore rot and fontsize keywords (GH7844)
Bug in DatetimeIndex.value_counts doesnt preserve tz (GH7735)
Bug in PeriodIndex.value_counts results in Int64Index (GH7735)
Bug in DataFrame.join when doing left join on index and there are multiple matches (GH5391)
Bug in GroupBy.transform() where int groups with a transform that didnt preserve the index were in-
correctly truncated (GH7972).
Bug in groupby where callable objects without name attributes would take the wrong path, and produce a
DataFrame instead of a Series (GH7929)
Bug in groupby error message when a DataFrame grouping column is duplicated (GH7511)
Bug in read_html where the infer_types argument forced coercion of date-likes incorrectly (GH7762,
GH7032).
Bug in Series.str.cat with an index which was filtered as to not include the first item (GH7857)
Bug in Timestamp cannot parse nanosecond from string (GH7878)
Bug in Timestamp with string offset and tz results incorrect (GH7833)
Bug in tslib.tz_convert and tslib.tz_convert_single may return different results (GH7798)
Bug in DatetimeIndex.intersection of non-overlapping timestamps with tz raises IndexError
(GH7880)
Bug in alignment with TimeOps and non-unique indexes (GH8363)
Bug in GroupBy.filter() where fast path vs. slow path made the filter return a non scalar value that
appeared valid but wasnt (GH7870).
Bug in date_range()/DatetimeIndex() when the timezone was inferred from input dates yet incorrect
times were returned when crossing DST boundaries (GH7835, GH7901).
Bug in to_excel() where a negative sign was being prepended to positive infinity and was absent for negative
infinity (GH7949)
Bug in area plot draws legend with incorrect alpha when stacked=True (GH8027)
Period and PeriodIndex addition/subtraction with np.timedelta64 results in incorrect internal rep-
resentations (GH7740)
Bug in Holiday with no offset or observance (GH7987)
Bug in DataFrame.to_latex formatting when columns or index is a MultiIndex (GH7982).
Bug in DateOffset around Daylight Savings Time produces unexpected results (GH5175).
Bug in DataFrame.shift where empty columns would throw ZeroDivisionError on numpy 1.7
(GH8019)
Bug in installation where html_encoding/*.html wasnt installed and therefore some tests were not run-
ning correctly (GH7927).
Bug in read_html where bytes objects were not tested for in _read (GH7927).
Bug in DataFrame.stack() when one of the column levels was a datelike (GH8039)
Bug in broadcasting numpy scalars with DataFrame (GH8116)
Bug in pivot_table performed with nameless index and columns raises KeyError (GH8103)
Bug in DataFrame.plot(kind=scatter) draws points and errorbars with different colors when the
color is specified by c keyword (GH8081)
Bug in Float64Index where iat and at were not testing and were failing (GH8092).
Bug in DataFrame.boxplot() where y-limits were not set correctly when producing multiple axes
(GH7528, GH5517).
Bug in read_csv where line comments were not handled correctly given a custom line terminator or
delim_whitespace=True (GH8122).
Bug in read_html where empty tables caused a StopIteration (GH7575)
Bug in casting when setting a column in a same-dtype block (GH7704)
Bug in accessing groups from a GroupBy when the original grouper was a tuple (GH8121).
Bug in .at that would accept integer indexers on a non-integer index and do fallback (GH7814)
Bug with kde plot and NaNs (GH8182)
Bug in GroupBy.count with float32 data type were nan values were not excluded (GH8169).
Bug with stacked barplots and NaNs (GH8175).
Bug in resample with non evenly divisible offsets (e.g. 7s) (GH8371)
Bug in interpolation methods with the limit keyword when no values needed interpolating (GH7173).
Bug where col_space was ignored in DataFrame.to_string() when header=False (GH8230).
Bug with DatetimeIndex.asof incorrectly matching partial strings and returning the wrong date
(GH8245).
Bug in plotting methods modifying the global matplotlib rcParams (GH8242).
Bug in DataFrame.__setitem__ that caused errors when setting a dataframe column to a sparse array
(GH8131)
Bug where Dataframe.boxplot() failed when entire column was empty (GH8181).
This is a minor release from 0.14.0 and includes a small number of API changes, several new features, enhancements,
and performance improvements along with a large number of bug fixes. We recommend that all users upgrade to this
version.
Highlights include:
New methods select_dtypes() to select columns based on the dtype and sem() to calculate the
standard error of the mean.
Support for dateutil timezones (see docs).
Support for ignoring full line comments in the read_csv() text parser.
New documentation section on Options and Settings.
Lots of bug fixes.
Enhancements
API Changes
Performance Improvements
Experimental Changes
Bug Fixes
Openpyxl now raises a ValueError on construction of the openpyxl writer instead of warning on pandas import
(GH7284).
For StringMethods.extract, when no match is found, the result - only containing NaN values - now also
has dtype=object instead of float (GH7242)
Period objects no longer raise a TypeError when compared using == with another object that isnt a
Period. Instead when comparing a Period with another object using == if the other object isnt a Period
False is returned. (GH7376)
Previously, the behaviour on resetting the time or not in offsets.apply, rollforward and rollback
operations differed between offsets. With the support of the normalize keyword for all offsets(see be-
low) with a default value of False (preserve time), the behaviour changed for certain offsets (BusinessMon-
thBegin, MonthEnd, BusinessMonthEnd, CustomBusinessMonthEnd, BusinessYearBegin, LastWeekOfMonth,
FY5253Quarter, LastWeekOfMonth, Easter):
In [6]: from pandas.tseries import offsets
Starting from 0.14.1 all offsets preserve time by default. The old behaviour can be obtained with
normalize=True
# new behaviour
In [1]: d + offsets.MonthEnd()
Out[1]: Timestamp('2014-01-31 09:00:00')
In [2]: d + offsets.MonthEnd(normalize=True)
Out[2]: Timestamp('2014-01-31 00:00:00')
Note that for the other offsets the default behaviour did not change.
Add back #N/A N/A as a default NA value in text parsing, (regresion from 0.12) (GH5521)
Raise a TypeError on inplace-setting with a .where and a non np.nan value as this is inconsistent with a
set-item expression like df[mask] = None (GH7656)
1.7.2 Enhancements
In [9]: rng.tz
Out[9]: tzfile('/usr/share/zoneinfo/Europe/London')
1.7.3 Performance
Improvements in dtype inference for numeric operations involving yielding performance gains for dtypes:
int64, timedelta64, datetime64 (GH7223)
Improvements in Series.transform for significant performance gains (GH6496)
Improvements in DataFrame.transform with ufuncs and built-in grouper functions for signifcant performance
gains (GH7383)
Regression in groupby aggregation of datetime64 dtypes (GH7555)
Improvements in MultiIndex.from_product for large iterables (GH7627)
1.7.4 Experimental
pandas.io.data.Options has a new method, get_all_data method, and now consistently returns a
multi-indexed DataFrame, see the docs. (GH5602)
io.gbq.read_gbq and io.gbq.to_gbq were refactored to remove the dependency on the Google
bq.py command line client. This submodule now uses httplib2 and the Google apiclient and
oauth2client API client libraries which should be more stable and, therefore, reliable than bq.py. See the
docs. (GH6937).
Bug in DataFrame.where with a symmetric shaped frame and a passed other of a DataFrame (GH7506)
Bug in Panel indexing with a multi-index axis (GH7516)
Regression in datetimelike slice indexing with a duplicated index and non-exact end-points (GH7523)
Bug in setitem with list-of-lists and single vs mixed types (GH7551:)
Bug in timeops with non-aligned Series (GH7500)
Bug in timedelta inference when assigning an incomplete Series (GH7592)
Bug in groupby .nth with a Series and integer-like column name (GH7559)
Bug in Series.get with a boolean accessor (GH7407)
Bug in value_counts where NaT did not qualify as missing (NaN) (GH7423)
Bug in to_timedelta that accepted invalid units and misinterpreted m/h (GH7611, GH6423)
Bug in line plot doesnt set correct xlim if secondary_y=True (GH7459)
Bug in grouped hist and scatter plots use old figsize default (GH7394)
Bug in plotting subplots with DataFrame.plot, hist clears passed ax even if the number of subplots is
one (GH7391).
Bug in plotting subplots with DataFrame.boxplot with by kw raises ValueError if the number of
subplots exceeds 1 (GH7391).
Bug in subplots displays ticklabels and labels in different rule (GH5897)
Bug in Panel.apply with a multi-index as an axis (GH7469)
Bug in DatetimeIndex.insert doesnt preserve name and tz (GH7299)
Bug in DatetimeIndex.asobject doesnt preserve name (GH7299)
Bug in multi-index slicing with datetimelike ranges (strings and Timestamps), (GH7429)
Bug in Index.min and max doesnt handle nan and NaT properly (GH7261)
Bug in PeriodIndex.min/max results in int (GH7609)
Bug in resample where fill_method was ignored if you passed how (GH2073)
Bug in StataReader when reading Stata 13 (117) files containing fixed width strings (GH7360)
Bug in StataWriter where encoding was ignored (GH7286)
Bug in DatetimeIndex comparison doesnt handle NaT properly (GH7529)
Bug in passing input with tzinfo to some offsets apply, rollforward or rollback resets tzinfo or
raises ValueError (GH7465)
Bug in DatetimeIndex.to_period, PeriodIndex.asobject, PeriodIndex.to_timestamp
doesnt preserve name (GH7485)
Bug in DatetimeIndex.to_period and PeriodIndex.to_timestanp handle NaT incorrectly
(GH7228)
Bug in offsets.apply, rollforward and rollback may return normal datetime (GH7502)
Bug in resample raises ValueError when target contains NaT (GH7227)
Bug in Timestamp.tz_localize resets nanosecond info (GH7534)
Bug in DatetimeIndex.asobject raises ValueError when it contains NaT (GH7539)
Bug in Timestamp.__new__ doesnt preserve nanosecond properly (GH7610)
Bug in Index.astype(float) where it would return an object dtype Index (GH7464).
Bug in DataFrame.reset_index loses tz (GH3950)
Bug in DatetimeIndex.freqstr raises AttributeError when freq is None (GH7606)
Bug in GroupBy.size created by TimeGrouper raises AttributeError (GH7453)
Bug in single column bar plot is misaligned (GH7498).
Bug in area plot with tz-aware time series raises ValueError (GH7471)
Bug in non-monotonic Index.union may preserve name incorrectly (GH7458)
Bug in DatetimeIndex.intersection doesnt preserve timezone (GH4690)
Bug in rolling_var where a window larger than the array would raise an error(GH7297)
Bug with last plotted timeseries dictating xlim (GH2960)
Bug with secondary_y axis not being considered for timeseries xlim (GH3490)
Bug in Float64Index assignment with a non scalar indexer (GH7586)
Bug in pandas.core.strings.str_contains does not properly match in a case insensitive fashion
when regex=False and case=False (GH7505)
Bug in expanding_cov, expanding_corr, rolling_cov, and rolling_corr for two arguments
with mismatched index (GH7512)
Bug in to_sql taking the boolean column as text column (GH7678)
Bug in grouped hist doesnt handle rot kw and sharex kw properly (GH7234)
Bug in .loc performing fallback integer indexing with object dtype indices (GH7496)
Bug (regression) in PeriodIndex constructor when passed Series objects (GH7701).
This is a major release from 0.13.1 and includes a small number of API changes, several new features, enhancements,
and performance improvements along with a large number of bug fixes. We recommend that all users upgrade to this
version.
Highlights include:
Officially support Python 3.4
SQL interfaces updated to use sqlalchemy, See Here.
Display interface changes, See Here
MultiIndexing Using Slicers, See Here.
Ability to join a singly-indexed DataFrame with a multi-indexed DataFrame, see Here
More consistency in groupby results and more flexible groupby specifications, See Here
Holiday calendars are now supported in CustomBusinessDay, see Here
Several improvements in plotting functions, including: hexbin, area and pie plots, see Here.
Performance doc section on I/O operations, See Here
Other Enhancements
API Changes
Text Parsing API Changes
Groupby API Changes
Performance Improvements
Prior Deprecations
Deprecations
Known Issues
Bug Fixes
Warning: In 0.14.0 all NDFrame based containers have undergone significant internal refactoring. Before that
each block of homogeneous data had its own labels and extra care was necessary to keep those in sync with the
parent containers labels. This should not have any visible user/API behavior changes (GH6745)
In [2]: dfl
Out[2]:
A B
0 1.583584 -0.438313
1 -0.402537 -0.780572
2 -0.141685 0.542241
3 0.370966 -0.251642
4 0.787484 1.666563
In [3]: dfl.iloc[:,2:3]
Out[3]:
Empty DataFrame
Columns: []
Index: [0, 1, 2, 3, 4]
In [4]: dfl.iloc[:,1:3]
Out[4]:
B
0 -0.438313
1 -0.780572
2 0.542241
3 -0.251642
4 1.666563
In [5]: dfl.iloc[4:6]
Out[5]:
A B
4 0.787484 1.666563
dfl.iloc[:,4]
IndexError: single positional indexer is out-of-bounds
Slicing with negative start, stop & step values handles corner cases better (GH6531):
df.iloc[:-len(df)] is now empty
df.iloc[len(df)::-1] now enumerates all elements in reverse
The DataFrame.interpolate() keyword downcast default has been changed from infer to None.
This is to preseve the original dtype unless explicitly requested otherwise (GH6290).
When converting a dataframe to HTML it used to return Empty DataFrame. This special case has been removed,
instead a header with the column names is returned (GH6062).
Series and Index now internall share more common operations, e.g.
factorize(),nunique(),value_counts() are now supported on Index types as well.
The Series.weekday property from is removed from Series for API consistency. Using a
DatetimeIndex/PeriodIndex method on a Series will now raise a TypeError. (GH4551, GH4056,
GH5519, GH6380, GH7206).
Add is_month_start, is_month_end, is_quarter_start, is_quarter_end,
is_year_start, is_year_end accessors for DateTimeIndex / Timestamp which return a
boolean array of whether the timestamp(s) are at the start/end of the month/quarter/year defined by the
frequency of the DateTimeIndex / Timestamp (GH4565, GH6998)
Local variable usage has changed in pandas.eval()/DataFrame.eval()/DataFrame.query()
(GH5987). For the DataFrame methods, two things have changed
In [7]: i[[0,1,2]]
Out[7]: Index([1, 2, 3], dtype='object')
Previously, the above operation would return Int64Index. If youd like to do this manually, use
Index.astype()
In [9]: i[[0,1,2]].astype(np.int_)
Out[9]: Int64Index([1, 2, 3], dtype='int32')
set_index no longer converts MultiIndexes to an Index of tuples. For example, the old behavior returned an
Index in this case (GH6459):
# Old behavior, casted MultiIndex to an Index
In [10]: tuple_ind
Out[10]: Index([(u'a', u'c'), (u'a', u'd'), (u'b', u'c'), (u'b', u'd')], dtype='object')
In [11]: df_multi.set_index(tuple_ind)
Out[11]:
0 1
(a, c) 0.471435 -1.190976
(a, d) 1.432707 -0.312652
(b, c) -0.720589 0.887163
(b, d) 0.859588 -0.636524
# New behavior
In [12]: mi
Out[12]:
MultiIndex(levels=[[u'a', u'b'], [u'c', u'd']],
labels=[[0, 0, 1, 1], [0, 1, 0, 1]])
In [13]: df_multi.set_index(mi)
Out[13]:
0 1
a c 0.471435 -1.190976
d 1.432707 -0.312652
b c -0.720589 0.887163
d 0.859588 -0.636524
pairwise keyword was added to the statistical moment functions rolling_cov, rolling_corr,
ewmcov, ewmcorr, expanding_cov, expanding_corr to allow the calculation of moving window
covariance and correlation matrices (GH4950). See Computing rolling pairwise covariances and correlations
in the docs.
In [16]: df = DataFrame(np.random.randn(10,4),columns=list('ABCD'))
In [18]: covs[df.index[-1]]
Out[18]:
B C D
A 0.128104 0.183628 -0.047358
B 0.856265 0.058945 0.145447
C 0.058945 0.335350 0.390637
Series.iteritems() is now lazy (returns an iterator rather than a list). This was the documented behavior
prior to 0.14. (GH6760)
Added nunique and value_counts functions to Index for counting unique elements. (GH6734)
stack and unstack now raise a ValueError when the level keyword refers to a non-unique item in the
Index (previously raised a KeyError). (GH6738)
drop unused order argument from Series.sort; args now are in the same order as Series.order; add
na_position arg to conform to Series.order (GH6847)
default sorting algorithm for Series.order is now quicksort, to conform with Series.sort (and
numpy defaults)
add inplace keyword to Series.order/sort to make them inverses (GH6859)
DataFrame.sort now places NaNs at the beginning or end of the sort according to the na_position
parameter. (GH3917)
accept TextFileReader in concat, which was affecting a common user idiom (GH6583), this was a
regression from 0.13.1
Added factorize functions to Index and Series to get indexer and unique values (GH7090)
describe on a DataFrame with a mix of Timestamp and string like objects returns a different Index (GH7088).
Previously the index was unintentionally sorted.
Arithmetic operations with only bool dtypes now give a warning indicating that they are evaluated in Python
space for +, -, and * operations and raise for all others (GH7011, GH6762, GH7015, GH7210)
x = pd.Series(np.random.rand(10) > 0.5)
y = True
x + y # warning generated: should do x | y instead
x / y # this raises because it doesn't make sense
In HDFStore, select_as_multiple will always raise a KeyError, when a key or the selector is not
found (GH6177)
df[col] = value and df.loc[:,col] = value are now completely equivalent; previously the
.loc would not necessarily coerce the dtype of the resultant series (GH6149)
dtypes and ftypes now return a series with dtype=object on empty containers (GH5740)
df.to_csv will now return a string of the CSV data if neither a target path nor a buffer is provided (GH6061)
pd.infer_freq() will now raise a TypeError if given an invalid Series/Index type (GH6407,
GH6463)
A tuple passed to DataFame.sort_index will be interpreted as the levels of the index, rather than requiring
a list of tuple (GH4370)
all offset operations now return Timestamp types (rather than datetime), Business/Week frequencies were
incorrect (GH4069)
to_excel now converts np.inf into a string representation, customizable by the inf_rep keyword argu-
ment (Excel has no native inf representation) (GH6782)
Replace pandas.compat.scipy.scoreatpercentile with numpy.percentile (GH6810)
.quantile on a datetime[ns] series now returns Timestamp instead of np.datetime64 objects
(GH6810)
change AssertionError to TypeError for invalid types passed to concat (GH6583)
Raise a TypeError when DataFrame is passed an iterator as the data argument (GH5357)
The default way of printing large DataFrames has changed. DataFrames exceeding max_rows and/or
max_columns are now displayed in a centrally truncated view, consistent with the printing of a
pandas.Series (GH5603).
In previous versions, a DataFrame was truncated once the dimension constraints were reached and an ellipse
(...) signaled that part of the data was cut off.
In the current version, large DataFrames are centrally truncated, showing a preview of head and tail in both
dimensions.
allow option truncate for display.show_dimensions to only show the dimensions if the frame is
truncated (GH6547).
The default for display.show_dimensions will now be truncate. This is consistent with how Series
display length.
In [19]: dfd = pd.DataFrame(np.arange(25).reshape(-1,5), index=[0,1,2,3,4], columns=[0,1,2,3,4])
.. .. ... ..
4 20 ... 24
[5 rows x 5 columns]
Regression in the display of a MultiIndexed Series with display.max_rows is less than the length of the
series (GH7101)
Fixed a bug in the HTML repr of a truncated Series or DataFrame not showing the class name with the large_repr
set to info (GH7105)
The verbose keyword in DataFrame.info(), which controls whether to shorten the info representation,
is now None by default. This will follow the global setting in display.max_info_columns. The global
setting can be overriden with verbose=True or verbose=False.
Fixed a bug with the info repr not honoring the display.max_info_columns setting (GH6939)
Offset/freq info now in Timestamp __repr__ (GH4553)
read_csv()/read_table() will now be noiser w.r.t invalid options rather than falling back to the
PythonParser.
Raise ValueError when sep specified with delim_whitespace=True in
read_csv()/read_table() (GH6607)
Raise ValueError when engine=c specified with unsupported options in
read_csv()/read_table() (GH6607)
Raise ValueError when fallback to python parser causes options to be ignored (GH6607)
Produce ParserWarning on fallback to python parser when no options are ignored (GH6607)
Translate sep=\s+ to delim_whitespace=True in read_csv()/read_table() if no other C-
unsupported options specified (GH6607)
In [23]: g = df.groupby('A')
groupby nth now reduces by default; filtering can be achieved by passing as_index=False. With an
optional dropna argument to ignore NaN. See the docs.
Reducing
In [27]: df = DataFrame([[1, np.nan], [1, 4], [5, 6]], columns=['A', 'B'])
In [28]: g = df.groupby('A')
In [29]: g.nth(0)
Out[29]:
B
A
1 NaN
5 6
Filtering
In [32]: gf = df.groupby('A',as_index=False)
In [33]: gf.nth(0)
Out[33]:
A B
0 1 NaN
2 5 6
groupby will now not return the grouped column for non-cython functions (GH5610, GH5614, GH6732), as its
already the index
In [35]: df = DataFrame([[1, np.nan], [1, 4], [5, 6], [5, 8]], columns=['A', 'B'])
In [36]: g = df.groupby('A')
In [37]: g.count()
Out[37]:
B
A
1 1
5 2
In [38]: g.describe()
Out[38]:
B
A
1 count 1.000000
mean 4.000000
std NaN
min 4.000000
25% 4.000000
50% 4.000000
75% 4.000000
... ...
5 mean 7.000000
std 1.414214
min 6.000000
25% 6.500000
50% 7.000000
75% 7.500000
max 8.000000
passing as_index will leave the grouped column in-place (this is not change in 0.14.0)
In [39]: df = DataFrame([[1, np.nan], [1, 4], [5, 6], [5, 8]], columns=['A', 'B'])
In [40]: g = df.groupby('A',as_index=False)
In [41]: g.count()
Out[41]:
A B
0 1 1
1 5 2
In [42]: g.describe()
Out[42]:
A B
0 count 2 1.000000
mean 1 4.000000
std 0 NaN
min 1 4.000000
25% 1 4.000000
50% 1 4.000000
75% 1 4.000000
... .. ...
1 mean 5 7.000000
std 0 1.414214
min 5 6.000000
25% 5 6.500000
50% 5 7.000000
75% 5 7.500000
max 5 8.000000
Allow specification of a more complex groupby via pd.Grouper, such as grouping by a Time and a string
field simultaneously. See the docs. (GH3794)
Better propagation/preservation of Series names when performing groupby operations:
SeriesGroupBy.agg will ensure that the name attribute of the original series is propagated to the
result (GH6265).
If the function provided to GroupBy.apply returns a named series, the name of the series will be kept as
the name of the column index of the DataFrame returned by GroupBy.apply (GH6124). This facilitates
DataFrame.stack operations where the name of the column index is used as the name of the inserted
column containing the pivoted data.
1.8.5 SQL
The SQL reading and writing functions now support more database flavors through SQLAlchemy (GH2717, GH4163,
GH5950, GH6292). All databases supported by SQLAlchemy can be used, such as PostgreSQL, MySQL, Oracle,
Microsoft SQL server (see documentation of SQLAlchemy on included dialects).
The functionality of providing DBAPI connection objects will only be supported for sqlite3 in the future. The
mysql flavor is deprecated.
The new functions read_sql_query() and read_sql_table() are introduced. The function read_sql()
is kept as a convenience wrapper around the other two and will delegate to specific function depending on the provided
input (database table name or sql query).
In practice, you have to provide a SQLAlchemy engine to the sql functions. To connect with SQLAlchemy you use
the create_engine() function to create an engine object from database URI. You only need to create the engine
once per database you are connecting to. For an in-memory sqlite database:
In [43]: from sqlalchemy import create_engine
This engine can then be used to write or read data to/from this database:
You can read data from a database by specifying the table name:
In [47]: pd.read_sql_table('db_table', engine)
Out[47]:
A B
0 1 a
1 2 b
2 3 c
Warning: Some of the existing functions or function aliases have been deprecated and will be removed in future
versions. This includes: tquery, uquery, read_frame, frame_query, write_frame.
Warning: The support for the mysql flavor when using DBAPI connection objects has been deprecated. MySQL
will be further supported with SQLAlchemy engines (GH6900).
In 0.14.0 we added a new way to slice multi-indexed objects. You can slice a multi-index by providing multiple
indexers.
You can provide any of the selectors as if you are indexing by label, see Selection by Label, including slices, lists of
labels, labels, and boolean indexers.
You can use slice(None) to select all the contents of that level. You do not need to specify all the deeper levels,
they will be implied as slice(None).
As usual, both sides of the slicers are included as this is label indexing.
See the docs See also issues (GH6134, GH4036, GH3057, GH2598, GH5641, GH7106)
Warning: You should specify all axes in the .loc specifier, meaning the indexer for the index and for the
columns. Their are some ambiguous cases where the passed indexer could be mis-interpreted as indexing both
axes, rather than into say the MuliIndex for the rows.
You should do this:
df.loc[(slice('A1','A3'),.....),:]
df.loc[(slice('A1','A3'),.....)]
Warning: You will need to make sure that the selection axes are fully lexsorted!
In [52]: df = DataFrame(np.arange(len(index)*len(columns)).reshape((len(index),len(columns))),
....: index=index,
....: columns=columns).sortlevel().sortlevel(axis=1)
....:
In [53]: df
Out[53]:
lvl0 a b
lvl1 bar foo bah foo
A0 B0 C0 D0 1 0 3 2
D1 5 4 7 6
C1 D0 9 8 11 10
D1 13 12 15 14
C2 D0 17 16 19 18
D1 21 20 23 22
C3 D0 25 24 27 26
... ... ... ... ...
A3 B1 C0 D1 229 228 231 230
C1 D0 233 232 235 234
D1 237 236 239 238
C2 D0 241 240 243 242
D1 245 244 247 246
C3 D0 249 248 251 250
D1 253 252 255 254
In [56]: df.loc[idx[:,:,['C1','C3']],idx[:,'foo']]
Out[56]:
lvl0 a b
lvl1 foo foo
A0 B0 C1 D0 8 10
D1 12 14
C3 D0 24 26
D1 28 30
B1 C1 D0 40 42
D1 44 46
C3 D0 56 58
... ... ...
A3 B0 C1 D1 204 206
C3 D0 216 218
D1 220 222
B1 C1 D0 232 234
D1 236 238
C3 D0 248 250
D1 252 254
It is possible to perform quite complicated selections using this method on multiple axes at the same time.
In [57]: df.loc['A1',(slice(None),'foo')]
Out[57]:
lvl0 a b
lvl1 foo foo
B0 C0 D0 64 66
D1 68 70
C1 D0 72 74
D1 76 78
C2 D0 80 82
D1 84 86
C3 D0 88 90
... ... ...
B1 C0 D1 100 102
C1 D0 104 106
D1 108 110
C2 D0 112 114
D1 116 118
C3 D0 120 122
D1 124 126
In [58]: df.loc[idx[:,:,['C1','C3']],idx[:,'foo']]
Out[58]:
lvl0 a b
lvl1 foo foo
A0 B0 C1 D0 8 10
D1 12 14
C3 D0 24 26
D1 28 30
B1 C1 D0 40 42
D1 44 46
C3 D0 56 58
... ... ...
A3 B0 C1 D1 204 206
C3 D0 216 218
D1 220 222
B1 C1 D0 232 234
D1 236 238
C3 D0 248 250
D1 252 254
Using a boolean indexer you can provide selection related to the values.
In [59]: mask = df[('a','foo')]>200
In [60]: df.loc[idx[mask,:,['C1','C3']],idx[:,'foo']]
Out[60]:
lvl0 a b
lvl1 foo foo
A3 B0 C1 D1 204 206
C3 D0 216 218
D1 220 222
B1 C1 D0 232 234
D1 236 238
C3 D0 248 250
D1 252 254
You can also specify the axis argument to .loc to interpret the passed slicers on a single axis.
In [61]: df.loc(axis=0)[:,:,['C1','C3']]
Out[61]:
lvl0 a b
lvl1 bar foo bah foo
A0 B0 C1 D0 9 8 11 10
D1 13 12 15 14
C3 D0 25 24 27 26
D1 29 28 31 30
B1 C1 D0 41 40 43 42
D1 45 44 47 46
C3 D0 57 56 59 58
... ... ... ... ...
A3 B0 C1 D1 205 204 207 206
C3 D0 217 216 219 218
D1 221 220 223 222
B1 C1 D0 233 232 235 234
D1 237 236 239 238
C3 D0 249 248 251 250
D1 253 252 255 254
In [64]: df2
Out[64]:
lvl0 a b
lvl1 bar foo bah foo
A0 B0 C0 D0 1 0 3 2
D1 5 4 7 6
C1 D0 -10 -10 -10 -10
D1 -10 -10 -10 -10
C2 D0 17 16 19 18
D1 21 20 23 22
C3 D0 -10 -10 -10 -10
... ... ... ... ...
A3 B1 C0 D1 229 228 231 230
C1 D0 -10 -10 -10 -10
D1 -10 -10 -10 -10
C2 D0 241 240 243 242
D1 245 244 247 246
C3 D0 -10 -10 -10 -10
D1 -10 -10 -10 -10
In [67]: df2
Out[67]:
lvl0 a b
lvl1 bar foo bah foo
A0 B0 C0 D0 1 0 3 2
D1 5 4 7 6
C1 D0 9000 8000 11000 10000
D1 13000 12000 15000 14000
C2 D0 17 16 19 18
D1 21 20 23 22
C3 D0 25000 24000 27000 26000
... ... ... ... ...
A3 B1 C0 D1 229 228 231 230
C1 D0 233000 232000 235000 234000
D1 237000 236000 239000 238000
C2 D0 241 240 243 242
D1 245 244 247 246
C3 D0 249000 248000 251000 250000
D1 253000 252000 255000 254000
1.8.7 Plotting
Hexagonal bin plots from DataFrame.plot with kind=hexbin (GH5478), See the docs.
DataFrame.plot and Series.plot now supports area plot with specifying kind=area (GH6656),
See the docs
Pie plots from Series.plot and DataFrame.plot with kind=pie (GH6976), See the docs.
Plotting with Error Bars is now supported in the .plot method of DataFrame and Series objects (GH3796,
GH6834), See the docs.
DataFrame.plot and Series.plot now support a table keyword for plotting matplotlib.Table,
See the docs. The table keyword can receive the following values.
False: Do nothing (default).
True: Draw a table using the DataFrame or Series called plot method. Data will be transposed to
meet matplotlibs default layout.
DataFrame or Series: Draw matplotlib.table using the passed data. The data will be
drawn as displayed in print method (not transposed automatically). Also, helper function
pandas.tools.plotting.table is added to create a table from DataFrame and Series, and
add it to an matplotlib.Axes.
plot(legend=reverse) will now reverse the order of legend labels for most plot kinds. (GH6014)
Line plot and area plot can be stacked by stacked=True (GH6656)
Following keywords are now acceptable for DataFrame.plot() with kind=bar and kind=barh:
width: Specify the bar width. In previous versions, static value 0.5 was passed to matplotlib and it cannot
be overwritten. (GH6604)
align: Specify the bar alignment. Default is center (different from matplotlib). In previous versions,
pandas passes align=edge to matplotlib and adjust the location to center by itself, and it results align
keyword is not applied as expected. (GH4525)
position: Specify relative alignments for bar plot layout. From 0 (left/bottom-end) to 1(right/top-end).
Default is 0.5 (center). (GH6604)
Because of the default align value changes, coordinates of bar plots are now located on integer values (0.0, 1.0,
2.0 ...). This is intended to make bar plot be located on the same coodinates as line plot. However, bar plot
may differs unexpectedly when you manually adjust the bar location or drawing area, such as using set_xlim,
set_ylim, etc. In this cases, please modify your script to meet with new coordinates.
There are prior version deprecations that are taking effect as of 0.14.0.
Remove DateRange in favor of DatetimeIndex (GH6816)
Remove column keyword from DataFrame.sort (GH4370)
Remove precision keyword from set_eng_float_format() (GH395)
Remove force_unicode keyword from DataFrame.to_string(), DataFrame.to_latex(), and
DataFrame.to_html(); these function encode in unicode by default (GH2224, GH2225)
Remove nanRep keyword from DataFrame.to_csv() and DataFrame.to_string() (GH275)
Remove unique keyword from HDFStore.select_column() (GH3256)
Remove inferTimeRule keyword from Timestamp.offset() (GH391)
Remove name keyword from get_data_yahoo() and get_data_google() ( commit b921d1a )
Remove offset keyword from DatetimeIndex constructor ( commit 3136390 )
Remove time_rule from several rolling-moment statistical functions, such as rolling_sum() (GH1042)
Removed neg - boolean operations on numpy arrays in favor of inv ~, as this is going to be deprecated in numpy
1.9 (GH6960)
1.8.9 Deprecations
In [2]: Series(1,np.arange(5)).iloc[3.0]
pandas/core/index.py:469: FutureWarning: scalar indexers for index type Int64Index shoul
Out[2]: 1
In [3]: Series(1,np.arange(5)).iloc[3.0:4]
pandas/core/index.py:527: FutureWarning: slice indexers when using iloc should be intege
Out[3]:
3 1
dtype: int64
In [5]: Series(1,np.arange(5.))[3.0]
Out[6]: 1
1.8.11 Enhancements
DataFrame and Series will create a MultiIndex object if passed a tuples dict, See the docs (GH3323)
In [71]: household
Out[71]:
male wealth
household_id
1 0 196087.3
2 1 316478.7
3 0 294750.0
....: ).set_index(['household_id','asset_id'])
....:
In [73]: portfolio
Out[73]:
name share
household_id asset_id
1 nl0000301109 ABN Amro 1.00
2 nl0000289783 Robeco 0.40
gb00b03mlx29 Royal Dutch Shell 0.60
3 gb00b03mlx29 Royal Dutch Shell 0.15
lu0197800237 AAB Eastern Europe Equity Fund 0.60
nl0000289965 Postbank BioTech Fonds 0.25
4 NaN NaN 1.00
share
household_id asset_id
1 nl0000301109 1.00
2 nl0000289783 0.40
gb00b03mlx29 0.60
3 gb00b03mlx29 0.15
lu0197800237 0.60
nl0000289965 0.25
quotechar, doublequote, and escapechar can now be specified when using DataFrame.to_csv
(GH5414, GH4528)
Partially sort by only the specified levels of a MultiIndex with the sort_remaining boolean kwarg.
(GH3984)
Added to_julian_date to TimeStamp and DatetimeIndex. The Julian Date is used primarily in
astronomy and represents the number of days from noon, January 1, 4713 BC. Because nanoseconds are used
to define the time in pandas the actual range of dates that you can use is 1678 AD to 2262 AD. (GH4041)
DataFrame.to_stata will now check data for compatibility with Stata data types and will upcast when
needed. When it is not possible to losslessly upcast, a warning is issued (GH6327)
DataFrame.to_stata and StataWriter will accept keyword arguments time_stamp and data_label
which allow the time stamp and dataset label to be set when creating a file. (GH6545)
pandas.io.gbq now handles reading unicode strings properly. (GH5940)
Holidays Calendars are now available and can be used with the CustomBusinessDay offset (GH6719)
Float64Index is now backed by a float64 dtype ndarray instead of an object dtype array (GH6471).
Implemented Panel.pct_change (GH6904)
Added how option to rolling-moment functions to dictate how to handle resampling; rolling_max() de-
faults to max, rolling_min() defaults to min, and all others default to mean (GH6297)
In [76]: df = DataFrame({
....: 'Branch' : 'A A A A A B'.split(),
....: 'Buyer': 'Carl Mark Carl Carl Joe Joe'.split(),
....: 'Quantity': [1, 3, 5, 1, 8, 1],
....: 'Date' : [datetime.datetime(2013,11,1,13,0), datetime.datetime(2013,9,1,13,5),
....: datetime.datetime(2013,10,1,20,0), datetime.datetime(2013,10,2,10,0),
....: datetime.datetime(2013,11,1,20,0), datetime.datetime(2013,10,2,10,0)],
....: 'PayDay' : [datetime.datetime(2013,10,4,0,0), datetime.datetime(2013,10,15,13,5),
....: datetime.datetime(2013,9,5,20,0), datetime.datetime(2013,11,2,10,0),
....: datetime.datetime(2013,10,7,20,0), datetime.datetime(2013,9,5,10,0)]})
....:
In [77]: df
Out[77]:
Branch Buyer Date PayDay Quantity
0 A Carl 2013-11-01 13:00:00 2013-10-04 00:00:00 1
1 A Mark 2013-09-01 13:05:00 2013-10-15 13:05:00 3
2 A Carl 2013-10-01 20:00:00 2013-09-05 20:00:00 5
3 A Carl 2013-10-02 10:00:00 2013-11-02 10:00:00 1
4 A Joe 2013-11-01 20:00:00 2013-10-07 20:00:00 8
5 B Joe 2013-10-02 10:00:00 2013-09-05 10:00:00 1
In [81]: ps
Out[81]:
2013-01-01 09:00 0.755414
2013-01-01 10:00 0.215269
2013-01-01 11:00 0.841009
2013-01-01 12:00 -1.445810
2013-01-01 13:00 -1.401973
2013-01-01 14:00 -0.100918
In [82]: ps['2013-01-02']
Out[82]:
2013-01-02 00:00 -0.208499
2013-01-02 01:00 1.033801
2013-01-02 02:00 -2.400454
2013-01-02 03:00 2.030604
2013-01-02 04:00 -1.142631
2013-01-02 05:00 0.211883
2013-01-02 06:00 0.704721
...
2013-01-02 17:00 0.464392
2013-01-02 18:00 -3.563517
2013-01-02 19:00 1.321106
2013-01-02 20:00 0.152631
2013-01-02 21:00 0.164530
2013-01-02 22:00 -0.430096
2013-01-02 23:00 0.767369
Freq: H, dtype: float64
read_excel can now read milliseconds in Excel dates and times with xlrd >= 0.9.3. (GH5945)
pd.stats.moments.rolling_var now uses Welfords method for increased numerical stability
(GH6817)
pd.expanding_apply and pd.rolling_apply now take args and kwargs that are passed on to the func (GH6289)
DataFrame.rank() now has a percentage rank option (GH5971)
Series.rank() now has a percentage rank option (GH5971)
Series.rank() and DataFrame.rank() now accept method=dense for ranks without gaps
(GH6514)
Support passing encoding with xlwt (GH3710)
Refactor Block classes removing Block.items attributes to avoid duplication in item handling (GH6745,
GH6988).
Testing statements updated to use specialized asserts (GH6175)
1.8.12 Performance
Improve performance of DataFrame construction with certain offsets, by removing faulty caching (e.g. Mon-
thEnd,BusinessMonthEnd), (GH6479)
Improve performance of CustomBusinessDay (GH6584)
improve performance of slice indexing on Series with string keys (GH6341, GH6372)
Performance improvement for DataFrame.from_records when reading a specified number of rows from
an iterable (GH6700)
Performance improvements in timedelta conversions for integer dtypes (GH6754)
Improved performance of compatible pickles (GH6899)
Improve performance in certain reindexing operations by optimizing take_2d (GH6749)
GroupBy.count() is now implemented in Cython and is much faster for large numbers of groups (GH7016).
1.8.13 Experimental
Bug in TimeGrouper/resample when presented with a non-monotonic DatetimeIndex that would return invalid
results. (GH4161)
Bug in index name propogation in TimeGrouper/resample (GH4161)
TimeGrouper has a more compatible API to the rest of the groupers (e.g. groups was missing) (GH3881)
Bug in multiple grouping with a TimeGrouper depending on target column order (GH6764)
Bug in pd.eval when parsing strings with possible tokens like & (GH6351)
Bug correctly handle placements of -inf in Panels when dividing by integer 0 (GH6178)
DataFrame.shift with axis=1 was raising (GH6371)
Disabled clipboard tests until release time (run locally with nosetests -A disabled) (GH6048).
Bug in DataFrame.replace() when passing a nested dict that contained keys not in the values to be
replaced (GH6342)
str.match ignored the na flag (GH6609).
Bug in take with duplicate columns that were not consolidated (GH6240)
Bug in interpolate changing dtypes (GH6290)
Bug in Series.get, was using a buggy access method (GH6383)
Bug in hdfstore queries of the form where=[(date, >=, datetime(2013,1,1)),
(date, <=, datetime(2014,1,1))] (GH6313)
Bug in DataFrame.dropna with duplicate indices (GH6355)
Regression in chained getitem indexing with embedded list-like from 0.12 (GH6394)
Float64Index with nans not comparing correctly (GH6401)
eval/query expressions with strings containing the @ character will now work (GH6366).
Bug in Series.reindex when specifying a method with some nan values was inconsistent (noted on a
resample) (GH6418)
Bug in DataFrame.replace() where nested dicts were erroneously depending on the order of dictionary
keys and values (GH5338).
Perf issue in concatting with empty objects (GH3259)
Clarify sorting of sym_diff on Index objects with NaN values (GH6444)
Regression in MultiIndex.from_product with a DatetimeIndex as input (GH6439)
Bug in str.extract when passed a non-default index (GH6348)
Bug in str.split when passed pat=None and n=1 (GH6466)
Bug in io.data.DataReader when passed "F-F_Momentum_Factor" and
data_source="famafrench" (GH6460)
Bug in sum of a timedelta64[ns] series (GH6462)
Bug in resample with a timezone and certain offsets (GH6397)
Bug in iat/iloc with duplicate indices on a Series (GH6493)
Bug in read_html where nans were incorrectly being used to indicate missing values in text. Should use the
empty string for consistency with the rest of pandas (GH5129).
Bug in read_html tests where redirected invalid URLs would make one test fail (GH6445).
Bug in Makefile where it didnt remove Cython generated C files with make clean (GH6768)
Bug with numpy < 1.7.2 when reading long strings from HDFStore (GH6166)
Bug in DataFrame._reduce where non bool-like (0/1) integers were being coverted into bools. (GH6806)
Regression from 0.13 with fillna and a Series on datetime-like (GH6344)
Bug in adding np.timedelta64 to DatetimeIndex with timezone outputs incorrect results (GH6818)
Bug in DataFrame.replace() where changing a dtype through replacement would only replace the first
occurrence of a value (GH6689)
Better error message when passing a frequency of MS in Period construction (GH5332)
Bug in Series.__unicode__ when max_rows=None and the Series has more than 1000 rows. (GH6863)
Bug in groupby.get_group where a datetlike wasnt always accepted (GH5267)
Bug in groupBy.get_group created by TimeGrouper raises AttributeError (GH6914)
Bug in DatetimeIndex.tz_localize and DatetimeIndex.tz_convert converting NaT incor-
rectly (GH5546)
Bug in arithmetic operations affecting NaT (GH6873)
Bug in Series.str.extract where the resulting Series from a single group match wasnt renamed to
the group name
Bug in DataFrame.to_csv where setting index=False ignored the header kwarg (GH6186)
Bug in DataFrame.plot and Series.plot, where the legend behave inconsistently when plotting to the
same axes repeatedly (GH6678)
Internal tests for patching __finalize__ / bug in merge not finalizing (GH6923, GH6927)
accept TextFileReader in concat, which was affecting a common user idiom (GH6583)
Bug in C parser with leading whitespace (GH3374)
Bug in C parser with delim_whitespace=True and \r-delimited lines
Bug in python parser with explicit multi-index in row following column header (GH6893)
Bug in Series.rank and DataFrame.rank that caused small floats (<1e-13) to all receive the same rank
(GH6886)
Bug in DataFrame.apply with functions that used *args or **kwargs and returned an empty result
(GH6952)
Bug in sum/mean on 32-bit platforms on overflows (GH6915)
Moved Panel.shift to NDFrame.slice_shift and fixed to respect multiple dtypes. (GH6959)
Bug in enabling subplots=True in DataFrame.plot only has single column raises TypeError, and
Series.plot raises AttributeError (GH6951)
Bug in DataFrame.plot draws unnecessary axes when enabling subplots and kind=scatter
(GH6951)
Bug in read_csv from a filesystem with non-utf-8 encoding (GH6807)
Bug in iloc when setting / aligning (GH6766)
Bug causing UnicodeEncodeError when get_dummies called with unicode values and a prefix (GH6885)
Bug in timeseries-with-frequency plot cursor display (GH5453)
Bug surfaced in groupby.plot when using a Float64Index (GH7025)
Stopped tests from failing if options data isnt able to be downloaded from Yahoo (GH7034)
Bug in parallel_coordinates and radviz where reordering of class column caused possible color/class
mismatch (GH6956)
Bug in radviz and andrews_curves where multiple values of color were being passed to plotting method
(GH6956)
Bug in Float64Index.isin() where containing nan s would make indices claim that they contained all
the things (GH7066).
Bug in DataFrame.boxplot where it failed to use the axis passed as the ax argument (GH3578)
Bug in the XlsxWriter and XlwtWriter implementations that resulted in datetime columns being format-
ted without the time (GH7075) were being passed to plotting method
read_fwf() treats None in colspec like regular python slices. It now reads from the beginning or until the
end of the line when colspec contains a None (previously raised a TypeError)
Bug in cache coherence with chained indexing and slicing; add _is_view property to NDFrame to correctly
predict views; mark is_copy on xs only if its an actual copy (and not a view) (GH7084)
Bug in DatetimeIndex creation from string ndarray with dayfirst=True (GH5917)
Bug in MultiIndex.from_arrays created from DatetimeIndex doesnt preserve freq and tz
(GH7090)
Bug in unstack raises ValueError when MultiIndex contains PeriodIndex (GH4342)
Bug in boxplot and hist draws unnecessary axes (GH6769)
Regression in groupby.nth() for out-of-bounds indexers (GH6621)
Bug in quantile with datetime values (GH6965)
Bug in Dataframe.set_index, reindex and pivot dont preserve DatetimeIndex and
PeriodIndex attributes (GH3950, GH5878, GH6631)
Bug in MultiIndex.get_level_values doesnt preserve DatetimeIndex and PeriodIndex at-
tributes (GH7092)
Bug in Groupby doesnt preserve tz (GH3950)
Bug in PeriodIndex partial string slicing (GH6716)
Bug in the HTML repr of a truncated Series or DataFrame not showing the class name with the large_repr set
to info (GH7105)
Bug in DatetimeIndex specifying freq raises ValueError when passed value is too short (GH7098)
Fixed a bug with the info repr not honoring the display.max_info_columns setting (GH6939)
Bug PeriodIndex string slicing with out of bounds values (GH5407)
Fixed a memory error in the hashtable implementation/factorizer on resizing of large tables (GH7157)
Bug in isnull when applied to 0-dimensional object arrays (GH7176)
Bug in query/eval where global constants were not looked up correctly (GH7178)
Bug in recognizing out-of-bounds positional list indexers with iloc and a multi-axis tuple indexer (GH7189)
Bug in setitem with a single value, multi-index and integer indices (GH7190, GH7218)
Bug in expressions evaluation with reversed ops, showing in series-dataframe ops (GH7198, GH7192)
Bug in multi-axis indexing with > 2 ndim and a multi-index (GH7199)
Fix a bug where invalid eval/query operations would blow the stack (GH5198)
This is a minor release from 0.13.0 and includes a small number of API changes, several new features, enhancements,
and performance improvements along with a large number of bug fixes. We recommend that all users upgrade to this
version.
Highlights include:
Added infer_datetime_format keyword to read_csv/to_datetime to allow speedups for homo-
geneously formatted datetimes.
Will intelligently limit display precision for datetime/timedelta formats.
Enhanced Panel apply() method.
Suggested tutorials in new Tutorials section.
Our pandas ecosystem is growing, We now feature related projects in a new Pandas Ecosystem section.
Much work has been taking place on improving the docs, and a new Contributing section has been added.
Even though it may only be of interest to devs, we <3 our new CI status page: ScatterCI.
Warning: 0.13.1 fixes a bug that was caused by a combination of having numpy < 1.8, and doing chained
assignment on a string-like array. Please review the docs, chained indexing can have unexpected results and should
generally be avoided.
This would previously segfault:
In [3]: df
Out[3]:
A
0 NaN
1 bar
2 bah
3 foo
4 bar
In [6]: df
Out[6]:
A
0 NaN
1 bar
2 bah
3 foo
4 bar
In [11]: df.info()
<class 'pandas.core.frame.DataFrame'>
Int64Index: 10 entries, 0 to 9
Data columns (total 3 columns):
A float64
B float64
C datetime64[ns]
dtypes: datetime64[ns](1), float64(2)
memory usage: 320.0 bytes
In [13]: df.info()
<class 'pandas.core.frame.DataFrame'>
Int64Index: 10 entries, 0 to 9
Data columns (total 3 columns):
A 7 non-null float64
B 10 non-null float64
C 7 non-null datetime64[ns]
dtypes: datetime64[ns](1), float64(2)
memory usage: 320.0 bytes
Add show_dimensions display option for the new DataFrame repr to control whether the dimensions print.
In [14]: df = DataFrame([[1, 2], [3, 4]])
In [16]: df
Out[16]:
0 1
0 1 2
1 3 4
In [18]: df
Out[18]:
0 1
0 1 2
1 3 4
[2 rows x 2 columns]
The ArrayFormatter for datetime and timedelta64 now intelligently limit precision based on the
values in the array (GH3401)
Previously output might look like:
age today diff
0 2001-01-01 00:00:00 2013-04-19 00:00:00 4491 days, 00:00:00
1 2004-06-01 00:00:00 2013-04-19 00:00:00 3244 days, 00:00:00
In [22]: df
Out[22]:
age today diff
0 2001-01-01 2013-04-19 4491 days
1 2004-06-01 2013-04-19 3244 days
[2 rows x 3 columns]
Add -NaN and -nan to the default set of NA values (GH5952). See NA Values.
Added Series.str.get_dummies vectorized string method (GH6021), to extract dummy/indicator vari-
ables for separated string columns:
In [23]: s = Series(['a', 'a|b', np.nan, 'a|c'])
In [24]: s.str.get_dummies(sep='|')
Out[24]:
a b c
0 1 0 0
1 1 1 0
2 0 0 0
3 1 0 1
[4 rows x 3 columns]
Added the NDFrame.equals() method to compare if two NDFrames are equal have equal axes, dtypes, and
values. Added the array_equivalent function to compare if two ndarrays are equal. NaNs in identical
locations are treated as equal. (GH5283) See also the docs for a motivating example.
In [25]: df = DataFrame({'col':['foo', 0, np.nan]})
In [27]: df.equals(df2)
Out[27]: False
In [28]: df.equals(df2.sort())
Out[28]: True
DataFrame.apply will use the reduce argument to determine whether a Series or a DataFrame
should be returned when the DataFrame is empty (GH6007).
Previously, calling DataFrame.apply an empty DataFrame would return either a DataFrame if there
were no columns, or the function being applied would be called with an empty Series to guess whether a
Series or DataFrame should be returned:
In [32]: def applied_func(col):
....: print("Apply function being called with: ", col)
....: return col.sum()
....:
In [34]: empty.apply(applied_func)
('Apply function being called with: ', Series([], dtype: float64))
Out[34]:
a NaN
b NaN
dtype: float64
Now, when apply is called on an empty DataFrame: if the reduce argument is True a Series will
returned, if it is False a DataFrame will be returned, and if it is None (the default) the function being
applied will be called with an empty series to try and guess the return type.
In [35]: empty.apply(applied_func, reduce=True)
Out[35]:
a NaN
b NaN
dtype: float64
[0 rows x 2 columns]
There are no announced changes in 0.13 or prior that are taking effect as of 0.13.1
1.9.4 Deprecations
1.9.5 Enhancements
date_format and datetime_format keywords can now be specified when writing to excel files
(GH4133)
MultiIndex.from_product convenience function for creating a MultiIndex from the cartesian product of
a set of iterables (GH6055):
In [37]: shades = ['light', 'dark']
In [42]: panel
Out[42]:
<class 'pandas.core.panel.Panel'>
Dimensions: 3 (items) x 5 (major_axis) x 4 (minor_axis)
Items axis: ItemA to ItemC
Major_axis axis: 2000-01-03 00:00:00 to 2000-01-07 00:00:00
Minor_axis axis: A to D
In [43]: panel['ItemA']
Out[43]:
A B C D
2000-01-03 0.952478 -1.239072 -1.409432 -0.014752
2000-01-04 0.988138 0.139683 1.422986 1.272395
2000-01-05 -0.072608 -0.223019 -2.147855 -1.449567
2000-01-06 -0.550603 2.123692 -1.347533 -1.195524
2000-01-07 -0.938153 0.122273 0.363565 -0.591863
[5 rows x 4 columns]
[5 rows x 4 columns]
[4 rows x 3 columns]
This is equivalent to
In [46]: panel.sum('major_axis')
Out[46]:
ItemA ItemB ItemC
A 0.379252 -3.696907 3.709335
B 0.923558 0.504242 4.656781
C -3.118269 -1.545718 3.188329
D -1.979310 -0.758060 -1.436483
[4 rows x 3 columns]
A transformation operation that returns a Panel, but is computing the z-score across the major_axis
In [47]: result = panel.apply(
....: lambda x: (x-x.mean())/x.std(),
....: axis='major_axis')
....:
In [48]: result
Out[48]:
<class 'pandas.core.panel.Panel'>
Dimensions: 3 (items) x 5 (major_axis) x 4 (minor_axis)
Items axis: ItemA to ItemC
Major_axis axis: 2000-01-03 00:00:00 to 2000-01-07 00:00:00
Minor_axis axis: A to D
In [49]: result['ItemA']
Out[49]:
A B C D
2000-01-03 1.004994 -1.166509 -0.535027 0.350970
2000-01-04 1.045875 -0.036892 1.393532 1.536326
2000-01-05 -0.170198 -0.334055 -1.037810 -0.970374
2000-01-06 -0.718186 1.588611 -0.492880 -0.736422
2000-01-07 -1.162486 -0.051156 0.672185 -0.180500
[5 rows x 4 columns]
In [52]: result
Out[52]:
<class 'pandas.core.panel.Panel'>
Dimensions: 4 (items) x 5 (major_axis) x 3 (minor_axis)
Items axis: A to D
Major_axis axis: 2000-01-03 00:00:00 to 2000-01-07 00:00:00
Minor_axis axis: ItemA to ItemC
In [53]: result.loc[:,:,'ItemA']
Out[53]:
A B C D
2000-01-03 0.116579 -0.667845 -1.151538 -0.157547
2000-01-04 0.650448 -1.114910 0.841527 0.760706
2000-01-05 -0.987433 -0.438897 -1.154468 -0.015033
2000-01-06 0.494000 1.060450 -0.775993 -1.140165
2000-01-07 -0.363770 0.013169 0.392036 -1.123913
[5 rows x 4 columns]
In [55]: result
Out[55]:
<class 'pandas.core.panel.Panel'>
Dimensions: 4 (items) x 5 (major_axis) x 3 (minor_axis)
Items axis: A to D
Major_axis axis: 2000-01-03 00:00:00 to 2000-01-07 00:00:00
Minor_axis axis: ItemA to ItemC
In [56]: result.loc[:,:,'ItemA']
Out[56]:
A B C D
2000-01-03 0.116579 -0.667845 -1.151538 -0.157547
2000-01-04 0.650448 -1.114910 0.841527 0.760706
2000-01-05 -0.987433 -0.438897 -1.154468 -0.015033
2000-01-06 0.494000 1.060450 -0.775993 -1.140165
2000-01-07 -0.363770 0.013169 0.392036 -1.123913
[5 rows x 4 columns]
1.9.6 Performance
1.9.7 Experimental
See V0.13.1 Bug Fixes for an extensive list of bugs that have been fixed in 0.13.1.
See the full release notes or issue tracker on GitHub for a complete list of all API changes, Enhancements and Bug
Fixes.
This is a major release from 0.12.0 and includes a number of API changes, several new features and enhancements
along with a large number of bug fixes.
Highlights include:
support for a new index type Float64Index, and other Indexing enhancements
HDFStore has a new string based syntax for query specification
support for new methods of interpolation
updated timedelta operations
a new string manipulation method extract
Nanosecond support for Offsets
isin for DataFrames
Several experimental features are added, including:
new eval/query methods for expression evaluation
support for msgpack serialization
an i/o interface to Googles BigQuery
Their are several new or updated docs sections including:
Comparison with SQL, which should be useful for those familiar with SQL but still learning pandas.
Comparison with R, idiom translations from R to pandas.
Warning: In 0.13.0 Series has internally been refactored to no longer sub-class ndarray but instead subclass
NDFrame, similar to the rest of the pandas containers. This should be a transparent change with only very limited
API implications. See Internal Refactoring
read_excel now supports an integer in its sheetname argument giving the index of the sheet to read in
(GH4301).
Text parser now treats anything that reads like inf (inf, Inf, -Inf, iNf, etc.) as infinity. (GH4220,
GH4219), affecting read_table, read_csv, etc.
pandas now is Python 2/3 compatible without the need for 2to3 thanks to @jtratner. As a result, pandas now
uses iterators more extensively. This also led to the introduction of substantive parts of the Benjamin Petersons
six library into compat. (GH4384, GH4375, GH4372)
pandas.util.compat and pandas.util.py3compat have been merged into pandas.compat.
pandas.compat now includes many functions allowing 2/3 compatibility. It contains both list and itera-
tor versions of range, filter, map and zip, plus other necessary elements for Python 3 compatibility. lmap,
lzip, lrange and lfilter all produce lists instead of iterators, for compatibility with numpy, subscripting
and pandas constructors.(GH4384, GH4375, GH4372)
Series.get with negative indexers now returns the same as [] (GH4390)
Changes to how Index and MultiIndex handle metadata (levels, labels, and names) (GH4039):
# previously, you would have set levels or labels directly
index.levels = [[1, 2, 3, 4], [1, 2, 4, 4]]
All division with NDFrame objects is now truedivision, regardless of the future import. This means that operat-
ing on pandas objects will by default use floating point division, and return a floating point dtype. You can use
// and floordiv to do integer division.
Integer division
In [3]: arr = np.array([1, 2, 3, 4])
2 1
3 4
dtype: int64
True Division
In [7]: pd.Series(arr) / pd.Series(arr2) # no future import required
Out[7]:
0 0.200000
1 0.666667
2 1.500000
3 4.000000
dtype: float64
Added the .bool() method to NDFrame objects to facilitate evaluating of single-element boolean Series:
In [1]: Series([True]).bool()
Out[1]: True
In [2]: Series([False]).bool()
Out[2]: False
In [3]: DataFrame([[True]]).bool()
Out[3]: True
In [4]: DataFrame([[False]]).bool()
Out[4]: False
All non-Index NDFrames (Series, DataFrame, Panel, Panel4D, SparsePanel, etc.), now support the
entire set of arithmetic operators and arithmetic flex methods (add, sub, mul, etc.). SparsePanel does not
support pow or mod with non-scalars. (GH3765)
Series and DataFrame now have a mode() method to calculate the statistical mode(s) by axis/Series.
(GH5367)
Chained assignment will now by default warn if the user is assigning to a copy. This can be changed with the
option mode.chained_assignment, allowed options are raise/warn/None. See the docs.
In [5]: dfc = DataFrame({'A':['aaa','bbb','ccc'],'B':[1,2,3]})
In [6]: pd.set_option('chained_assignment','warn')
In [9]: dfc
Out[9]:
A B
0 11 1
1 bbb 2
2 ccc 3
[3 rows x 2 columns]
These were announced changes in 0.12 or prior that are taking effect as of 0.13.0
Remove deprecated Factor (GH3650)
Remove deprecated set_printoptions/reset_printoptions (GH3046)
Remove deprecated _verbose_info (GH3215)
Remove deprecated read_clipboard/to_clipboard/ExcelFile/ExcelWriter from
pandas.io.parsers (GH3717) These are available as functions in the main pandas namespace (e.g.
pd.read_clipboard)
default for tupleize_cols is now False for both to_csv and read_csv. Fair warning in 0.12
(GH3604)
default for display.max_seq_len is now 100 rather then None. This activates truncated display (...) of long
sequences in various places. (GH3391)
1.10.3 Deprecations
Deprecated in 0.13.0
deprecated iterkv, which will be removed in a future release (this was an alias of iteritems used to bypass
2to3s changes). (GH4384, GH4375, GH4372)
deprecated the string method match, whose role is now performed more idiomatically by extract. In a
future release, the default behavior of match will change to become analogous to contains, which returns
a boolean indexer. (Their distinction is strictness: match relies on re.match while contains relies on
re.search.) In this release, the deprecated behavior is the default, but the new behavior is available through
the keyword argument as_indexer=True.
Prior to 0.13, it was impossible to use a label indexer (.loc/.ix) to set a value that was not contained in the index
of a particular axis. (GH2578). See the docs
In the Series case this is effectively an appending operation
In [10]: s = Series([1,2,3])
In [11]: s
Out[11]:
0 1
1 2
2 3
dtype: int64
In [12]: s[5] = 5.
In [13]: s
Out[13]:
0 1
1 2
2 3
5 5
dtype: float64
In [15]: dfi
Out[15]:
A B
0 0 1
1 2 3
2 4 5
[3 rows x 2 columns]
In [17]: dfi
Out[17]:
A B C
0 0 1 0
1 2 3 2
2 4 5 4
[3 rows x 3 columns]
In [19]: dfi
Out[19]:
A B C
0 0 1 0
1 2 3 2
2 4 5 4
3 5 5 5
[4 rows x 3 columns]
A Panel setting operation on an arbitrary axis aligns the input to the Panel
In [20]: p = pd.Panel(np.arange(16).reshape(2,4,2),
....: items=['Item1','Item2'],
....: major_axis=pd.date_range('2001/1/12',periods=4),
....: minor_axis=['A','B'],dtype='float64')
....:
In [21]: p
Out[21]:
<class 'pandas.core.panel.Panel'>
Dimensions: 2 (items) x 4 (major_axis) x 2 (minor_axis)
Items axis: Item1 to Item2
Major_axis axis: 2001-01-12 00:00:00 to 2001-01-15 00:00:00
Minor_axis axis: A to B
In [23]: p
Out[23]:
<class 'pandas.core.panel.Panel'>
Dimensions: 2 (items) x 4 (major_axis) x 3 (minor_axis)
Items axis: Item1 to Item2
Major_axis axis: 2001-01-12 00:00:00 to 2001-01-15 00:00:00
Minor_axis axis: A to C
In [24]: p.loc[:,:,'C']
Out[24]:
Item1 Item2
2001-01-12 30 32
2001-01-13 30 32
2001-01-14 30 32
2001-01-15 30 32
[4 rows x 2 columns]
Added a new index type, Float64Index. This will be automatically created when passing floating values in
index creation. This enables a pure label-based slicing paradigm that makes [],ix,loc for scalar indexing
and slicing work exactly the same. See the docs, (GH263)
Construction is by default for floating type values.
In [25]: index = Index([1.5, 2, 3, 4.5, 5])
In [26]: index
Out[26]: Float64Index([1.5, 2.0, 3.0, 4.5, 5.0], dtype='float64')
In [27]: s = Series(range(5),index=index)
In [28]: s
Out[28]:
1.5 0
2.0 1
3.0 2
4.5 3
5.0 4
dtype: int64
Scalar selection for [],.ix,.loc will always be label based. An integer will match an equal float index (e.g.
3 is equivalent to 3.0)
In [29]: s[3]
Out[29]: 2
In [30]: s.ix[3]
Out[30]: 2
In [31]: s.loc[3]
Out[31]: 2
In [34]: s.ix[2:4]
Out[34]:
2 1
3 2
dtype: int64
In [35]: s.loc[2:4]
Out[35]:
2 1
3 2
dtype: int64
In [36]: s.iloc[2:4]
Out[36]:
3.0 2
4.5 3
dtype: int64
dtype: int64
In [38]: s.loc[2.1:4.6]
Out[38]:
3.0 2
4.5 3
dtype: int64
Indexing on other index types are preserved (and positional fallback for [],ix), with the exception, that floating
point slicing on indexes on non Float64Index will now raise a TypeError.
In [1]: Series(range(5))[3.5]
TypeError: the label [3.5] is not a proper indexer for this index type (Int64Index)
In [1]: Series(range(5))[3.5:4.5]
TypeError: the slice start [3.5] is not a proper indexer for this index type (Int64Index)
Using a scalar float indexer will be deprecated in a future version, but is allowed for now.
In [3]: Series(range(5))[3.0]
Out[3]: 3
Query Format Changes. A much more string-like query format is now supported. See the docs.
In [39]: path = 'test.h5'
In [41]: dfq.to_hdf(path,'dfq',format='table',data_columns=True)
[6 rows x 2 columns]
[8 rows x 4 columns]
the format keyword now replaces the table keyword; allowed values are fixed(f) or table(t) the
same defaults as prior < 0.13.0 remain, e.g. put implies fixed format and append implies table format.
This default format can be set as an option by setting io.hdf.default_format.
In [44]: path = 'test.h5'
In [45]: df = DataFrame(randn(10,2))
In [46]: df.to_hdf(path,'df_table',format='table')
In [47]: df.to_hdf(path,'df_table2',append=True)
In [48]: df.to_hdf(path,'df_fixed')
In [51]: df = DataFrame(randn(10,2))
In [54]: store1.append('df',df)
In [55]: store2.append('df2',df)
In [56]: store1
Out[56]:
<class 'pandas.io.pytables.HDFStore'>
File path: test.h5
/df frame_table (typ->appendable,nrows->10,ncols->2,indexers->[index])
In [57]: store2
Out[57]:
<class 'pandas.io.pytables.HDFStore'>
File path: test.h5
/df frame_table (typ->appendable,nrows->10,ncols->2,indexers->[index])
/df2 frame_table (typ->appendable,nrows->10,ncols->2,indexers->[index])
In [58]: store1.close()
In [59]: store2
Out[59]:
<class 'pandas.io.pytables.HDFStore'>
File path: test.h5
/df frame_table (typ->appendable,nrows->10,ncols->2,indexers->[index])
/df2 frame_table (typ->appendable,nrows->10,ncols->2,indexers->[index])
In [60]: store2.close()
In [61]: store2
Out[61]:
<class 'pandas.io.pytables.HDFStore'>
File path: test.h5
File is CLOSED
removed the _quiet attribute, replace by a DuplicateWarning if retrieving duplicate rows from a table
(GH4367)
removed the warn argument from open. Instead a PossibleDataLossError exception will be raised if
you try to use mode=w with an OPEN file handle (GH4367)
allow a passed locations array or mask as a where condition (GH4467). See the docs for an example.
add the keyword dropna=True to append to change whether ALL nan rows are not written to the store
(default is True, ALL nan rows are NOT written), also settable via the option io.hdf.dropna_table
(GH4625)
pass thru store creation arguments; can be used to support in-memory stores
The HTML and plain text representations of DataFrame now show a truncated view of the table once it exceeds
a certain size, rather than switching to the short info view (GH4886, GH5550). This makes the representation more
consistent as small DataFrames get larger.
To get the info view, call DataFrame.info(). If you prefer the info view as the repr for large DataFrames, you
can set this by running set_option(display.large_repr, info).
1.10.8 Enhancements
df.to_clipboard() learned a new excel keyword that lets you paste df data directly into excel (enabled
by default). (GH5070).
read_html now raises a URLError instead of catching and raising a ValueError (GH4303, GH4305)
Added a test for read_clipboard() and to_clipboard() (GH4282)
Clipboard functionality now works with PySide (GH4282)
Added a more informative error message when plot arguments contain overlapping color and style arguments
(GH4402)
to_dict now takes records as a possible outtype. Returns an array of column-keyed dictionaries. (GH4936)
NaN handing in get_dummies (GH4446) with dummy_na
# previously, nan was erroneously counted as 2 here
# now it is not counted at all
In [62]: get_dummies([1, 2, np.nan])
Out[62]:
1 2
0 1 0
1 0 1
2 0 0
[3 rows x 2 columns]
# unless requested
In [63]: get_dummies([1, 2, np.nan], dummy_na=True)
Out[63]:
1 2 NaN
0 1 0 0
1 0 1 0
2 0 0 1
[3 rows x 3 columns]
Using the new top-level to_timedelta, you can convert a scalar or array from the standard timedelta format
(produced by to_csv) into a timedelta type (np.timedelta64 in nanoseconds).
In [64]: to_timedelta('1 days 06:05:01.00003')
Out[64]: Timedelta('1 days 06:05:01.000030')
In [65]: to_timedelta('15.5us')
Out[65]: Timedelta('0 days 00:00:00.000015')
In [67]: to_timedelta(np.arange(5),unit='s')
Out[67]: TimedeltaIndex(['00:00:00', '00:00:01', '00:00:02', '00:00:03', '00:00:04'], dtype='tim
In [68]: to_timedelta(np.arange(5),unit='d')
Out[68]: TimedeltaIndex(['0 days', '1 days', '2 days', '3 days', '4 days'], dtype='timedelta64[n
In [70]: td = Series(date_range('20130101',periods=4))-Series(date_range('20121201',periods=4))
In [73]: td
Out[73]:
0 31 days 00:00:00
1 31 days 00:00:00
2 31 days 00:05:03
3 NaT
dtype: timedelta64[ns]
# to days
In [74]: td / np.timedelta64(1,'D')
Out[74]:
0 31.000000
1 31.000000
2 31.003507
3 NaN
dtype: float64
In [75]: td.astype('timedelta64[D]')
Out[75]:
0 31
1 31
2 31
3 NaN
dtype: float64
# to seconds
In [76]: td / np.timedelta64(1,'s')
Out[76]:
0 2678400
1 2678400
2 2678703
3 NaN
dtype: float64
In [77]: td.astype('timedelta64[s]')
Out[77]:
0 2678400
1 2678400
2 2678703
3 NaN
dtype: float64
In [79]: td * Series([1,2,3,4])
Out[79]:
0 31 days 00:00:00
1 62 days 00:00:00
2 93 days 00:15:09
3 NaT
dtype: timedelta64[ns]
In [83]: td.fillna(timedelta(days=1,seconds=5))
Out[83]:
0 31 days 00:00:00
1 31 days 00:00:00
2 31 days 00:05:03
3 1 days 00:00:05
dtype: timedelta64[ns]
In [85]: td.quantile(.1)
Out[85]: Timedelta('31 days 00:00:00')
plot(kind=kde) now accepts the optional parameters bw_method and ind, passed to
scipy.stats.gaussian_kde() (for scipy >= 0.11.0) to set the bandwidth, and to gkde.evaluate() to specify the in-
dices at which it is evaluated, respectively. See scipy docs. (GH4298)
DataFrame constructor now accepts a numpy masked record array (GH3478)
The new vectorized string method extract return regular expression matches more conveniently.
In [86]: Series(['a1', 'b2', 'c3']).str.extract('[ab](\d)')
Out[86]:
0 1
1 2
2 NaN
dtype: object
Elements that do not match return NaN. Extracting a regular expression with more than one group returns a
DataFrame with one column per group.
In [87]: Series(['a1', 'b2', 'c3']).str.extract('([ab])(\d)')
Out[87]:
0 1
0 a 1
1 b 2
2 NaN NaN
[3 rows x 2 columns]
Elements that do not match return a row of NaN. Thus, a Series of messy strings can be converted into a like-
indexed Series or DataFrame of cleaned-up or more useful strings, without necessitating get() to access tuples
or re.match objects.
Named groups like
In [88]: Series(['a1', 'b2', 'c3']).str.extract(
....: '(?P<letter>[ab])(?P<digit>\d)')
....:
Out[88]:
letter digit
0 a 1
1 b 2
2 NaN NaN
[3 rows x 2 columns]
2 NaN 3
[3 rows x 2 columns]
Period conversions in the range of seconds and below were reworked and extended up to nanoseconds. Periods
in the nanosecond range are now available.
In [90]: date_range('2013-01-01', periods=5, freq='5N')
Out[90]:
DatetimeIndex(['2013-01-01', '2013-01-01', '2013-01-01', '2013-01-01',
'2013-01-01'],
dtype='datetime64[ns]', freq='5N', tz=None)
In [93]: t + pd.datetools.Nano(123)
Out[93]: Timestamp('2013-01-01 09:01:02.000000123')
A new method, isin for DataFrames, which plays nicely with boolean indexing. The argument to isin, what
were comparing the DataFrame to, can be a DataFrame, Series, dict, or array of values. See the docs for more.
To get the rows where any of the conditions are met:
In [94]: dfi = DataFrame({'A': [1, 2, 3, 4], 'B': ['a', 'b', 'f', 'n']})
In [95]: dfi
Out[95]:
A B
0 1 a
1 2 b
2 3 f
3 4 n
[4 rows x 2 columns]
In [96]: other = DataFrame({'A': [1, 3, 3, 7], 'B': ['e', 'f', 'f', 'e']})
In [98]: mask
Out[98]:
A B
0 True False
1 False False
2 True True
3 False False
[4 rows x 2 columns]
In [99]: dfi[mask.any(1)]
Out[99]:
A B
0 1 a
2 3 f
[2 rows x 2 columns]
tz_localize can infer a fall daylight savings transition based on the structure of the unlocalized data
(GH4230), see the docs
DatetimeIndex is now in the API documentation, see the docs
json_normalize() is a new method to allow you to create a flat table from semi-structured JSON data. See
the docs (GH1067)
Added PySide support for the qtpandas DataFrameModel and DataFrameWidget.
Python csv parser now supports usecols (GH4335)
Frequencies gained several new offsets:
LastWeekOfMonth (GH4637)
FY5253, and FY5253Quarter (GH4511)
DataFrame has a new interpolate method, similar to Series (GH4434, GH1892)
In [100]: df = DataFrame({'A': [1, 2.1, np.nan, 4.7, 5.6, 6.8],
.....: 'B': [.25, np.nan, np.nan, 4, 12.2, 14.4]})
.....:
In [101]: df.interpolate()
Out[101]:
A B
0 1.0 0.25
1 2.1 1.50
2 3.4 2.75
3 4.7 4.00
4 5.6 12.20
5 6.8 14.40
[6 rows x 2 columns]
Additionally, the method argument to interpolate has been expanded to include nearest,
zero, slinear, quadratic, cubic, barycentric, krogh,
piecewise_polynomial, pchip, polynomial, spline The new methods re-
quire scipy. Consult the Scipy reference guide and documentation for more information about when the various
methods are appropriate. See the docs.
Interpolate now also accepts a limit keyword argument. This works similar to fillnas limit:
In [102]: ser = Series([1, 3, np.nan, np.nan, np.nan, 11])
In [103]: ser.interpolate(limit=2)
Out[103]:
0 1
1 3
2 5
3 7
4 NaN
5 11
dtype: float64
In [107]: df
Out[107]:
A1970 A1980 B1970 B1980 X id
0 a d 2.5 3.2 -1.085631 0
1 b e 1.2 1.3 0.997345 1
2 c f 0.7 0.1 0.282978 2
[3 rows x 6 columns]
[6 rows x 3 columns]
to_csv now takes a date_format keyword argument that specifies how output datetime objects should
be formatted. Datetimes encountered in the index, columns, and values will all have this formatting applied.
(GH4313)
1.10.9 Experimental
The new eval() function implements expression evaluation using numexpr behind the scenes. This results
in large speedups for complicated expressions involving large DataFrames/Series. For example,
In [109]: nrows, ncols = 20000, 100
query() method has been added that allows you to select elements of a DataFrame using a natural query
syntax nearly identical to Python syntax. For example,
In [115]: n = 20
[2 rows x 3 columns]
selects all the rows of df where a < b < c evaluates to True. For more details see the the docs.
pd.read_msgpack() and pd.to_msgpack() are now a supported method of serialization of arbitrary
pandas (and python objects) in a lightweight portable binary format. See the docs
Warning: Since this is an EXPERIMENTAL LIBRARY, the storage format may not be stable until a future
release.
In [118]: df = DataFrame(np.random.rand(5,2),columns=list('AB'))
In [119]: df.to_msgpack('foo.msg')
In [120]: pd.read_msgpack('foo.msg')
Out[120]:
A B
0 0.251082 0.017357
1 0.347915 0.929879
2 0.546233 0.203368
3 0.064942 0.031722
4 0.355309 0.524575
[5 rows x 2 columns]
In [121]: s = Series(np.random.rand(5),index=date_range('20130101',periods=5))
In [123]: pd.read_msgpack('foo.msg')
Out[123]:
[ A B
0 0.251082 0.017357
1 0.347915 0.929879
2 0.546233 0.203368
3 0.064942 0.031722
4 0.355309 0.524575
[5 rows x 2 columns]
2013-01-01 0.022321
2013-01-02 0.227025
2013-01-03 0.383282
2013-01-04 0.193225
2013-01-05 0.110977
Freq: D, dtype: float64
pandas.io.gbq provides a simple way to extract from, and load data into, Googles BigQuery Data Sets by
way of pandas DataFrames. BigQuery is a high performance SQL-like database service, useful for performing
ad-hoc queries against extremely large datasets. See the docs
from pandas.io import gbq
Warning: To use this module, you will need a BigQuery account. See
<https://cloud.google.com/products/big-query> for details.
As of 10/10/13, there is a bug in Googles API preventing result sets from being larger than 100,000 rows.
A patch is scheduled for the week of 10/14/13.
In 0.13.0 there is a major refactor primarily to subclass Series from NDFrame, which is the base class currently
for DataFrame and Panel, to unify methods and behaviors. Series formerly subclassed directly from ndarray.
(GH4080, GH3862, GH816)
In [125]: s = Series([1,2,3,4])
Numpy Usage
In [126]: np.ones_like(s)
Out[126]: array([1, 1, 1, 1], dtype=int64)
In [127]: np.diff(s)
Out[127]: array([1, 1, 1], dtype=int64)
In [128]: np.where(s>1,s,np.nan)
Out[128]: array([ nan, 2., 3., 4.])
Pandonic Usage
In [129]: Series(1,index=s.index)
Out[129]:
0 1
1 1
2 1
3 1
dtype: int64
In [130]: s.diff()
Out[130]:
0 NaN
1 1
2 1
3 1
dtype: float64
In [131]: s.where(s>1)
Out[131]:
0 NaN
1 2
2 3
3 4
dtype: float64
Passing a Series directly to a cython function expecting an ndarray type will no long work directly, you
must pass Series.values, See Enhancing Performance
Series(0.5) would previously return the scalar 0.5, instead this will return a 1-element Series
This change breaks rpy2<=2.3.8. an Issue has been opened against rpy2 and a workaround is detailed in
GH5698. Thanks @JanSchulz.
Pickle compatibility is preserved for pickles created prior to 0.13. These must be unpickled with
pd.read_pickle, see Pickling.
Refactor of series.py/frame.py/panel.py to move common code to generic.py
added _setup_axes to created generic NDFrame structures
moved methods
* from_axes,_wrap_array,axes,ix,loc,iloc,shape,empty,swapaxes,transpose,pop
* __iter__,keys,__contains__,__len__,__neg__,__invert__
* convert_objects,as_blocks,as_matrix,values
* __getstate__,__setstate__ (compat remains in frame/panel)
* __getattr__,__setattr__
* _indexed_same,reindex_like,align,where,mask
* fillna,replace (Series replace is now consistent with DataFrame)
* filter (also added axis argument to selectively filter on a different axis)
* reindex,reindex_axis,take
* truncate (moved to become part of NDFrame)
These are API changes which make Panel more consistent with DataFrame
swapaxes on a Panel with the same axes specified now return a copy
support attribute access for setting
filter supports the same API as the original DataFrame filter
Reindex called with no arguments will now return a copy of the input object
TimeSeries is now an alias for Series. the property is_time_series can be used to distinguish (if
desired)
Refactor of Sparse objects to use BlockManager
Created a new block type in internals, SparseBlock, which can hold multi-dtypes and is non-
consolidatable. SparseSeries and SparseDataFrame now inherit more methods from there hi-
erarchy (Series/DataFrame), and no longer inherit from SparseArray (which instead is the object of
the SparseBlock)
Sparse suite now supports integration with non-sparse data. Non-float sparse data is supportable (partially
implemented)
Operations on sparse structures within DataFrames should preserve sparseness, merging type operations
will convert to dense (and back to sparse), so might be somewhat inefficient
enable setitem on SparseSeries for boolean/integer/slices
SparsePanels implementation is unchanged (e.g. not using BlockManager, needs work)
added ftypes method to Series/DataFrame, similar to dtypes, but indicates if the underlying is sparse/dense
(as well as the dtype)
All NDFrame objects can now use __finalize__() to specify various values to propagate to new objects
from an existing one (e.g. name in Series will follow more automatically now)
Internal type checking is now done via a suite of generated classes, allowing isinstance(value, klass)
without having to directly import the klass, courtesy of @jtratner
Bug in Series update where the parent frame is not updating its cache based on changes (GH4080) or types
(GH3217), fillna (GH3386)
Indexing with dtype conversions fixed (GH4463, GH4204)
Refactor Series.reindex to core/generic.py (GH4604, GH4618), allow method= in reindexing on a Se-
ries to work
Series.copy no longer accepts the order parameter and is now consistent with NDFrame copy
Refactor rename methods to core/generic.py; fixes Series.rename for (GH4605), and adds rename with
the same signature for Panel
Refactor clip methods to core/generic.py (GH4798)
Refactor of _get_numeric_data/_get_bool_data to core/generic.py, allowing Series/Panel function-
ality
Series (for index) / Panel (for items) now allow attribute access to its elements (GH1903)
In [132]: s = Series([1,2,3],index=list('abc'))
In [133]: s.b
Out[133]: 2
In [134]: s.a = 5
In [135]: s
Out[135]:
a 5
b 2
c 3
dtype: int64
See V0.13.0 Bug Fixes for an extensive list of bugs that have been fixed in 0.13.0.
See the full release notes or issue tracker on GitHub for a complete list of all API changes, Enhancements and Bug
Fixes.
This is a major release from 0.11.0 and includes several new features and enhancements along with a large number of
bug fixes.
Highlights include a consistent I/O API naming scheme, routines to read html, write multi-indexes to csv files, read
& write STATA data files, read & write JSON format files, Python 3 support for HDFStore, filtering of groupby
expressions via filter, and a revamped replace routine that accepts regular expressions.
The I/O API is now much more consistent with a set of top level reader functions accessed like
pd.read_csv() that generally return a pandas object.
read_csv
read_excel
read_hdf
read_sql
read_json
read_html
read_stata
read_clipboard
The corresponding writer functions are object methods that are accessed like df.to_csv()
to_csv
to_excel
to_hdf
to_sql
to_json
to_html
to_stata
to_clipboard
Fix modulo and integer division on Series,DataFrames to act similary to float dtypes to return np.nan
or np.inf as appropriate (GH3590). This correct a numpy bug that treats integer and float dtypes
differently.
In [1]: p = DataFrame({ 'first' : [4,5,8], 'second' : [0,0,3] })
In [2]: p % 0
Out[2]:
first second
0 NaN NaN
1 NaN NaN
2 NaN NaN
[3 rows x 2 columns]
In [3]: p % p
Out[3]:
first second
0 0 NaN
1 0 NaN
2 0 0
[3 rows x 2 columns]
In [4]: p / p
Out[4]:
first second
0 1 NaN
1 1 NaN
2 1 1
[3 rows x 2 columns]
In [5]: p / 0
Out[5]:
first second
0 inf NaN
1 inf NaN
2 inf inf
[3 rows x 2 columns]
Add squeeze keyword to groupby to allow reduction from DataFrame -> Series if groups are unique. This
is a Regression from 0.10.1. We are reverting back to the prior behavior. This means groupby will return the
same shaped objects whether the groups are unique or not. Revert this issue (GH2893) with (GH3596).
In [6]: df2 = DataFrame([{"val1": 1, "val2" : 20}, {"val1":1, "val2": 19},
...: {"val1":1, "val2": 27}, {"val1":1, "val2": 12}])
...:
[1 rows x 4 columns]
Raise on iloc when boolean indexing with a label based indexer mask e.g. a boolean Series, even with integer
labels, will raise. Since iloc is purely positional based, the labels on the Series are not alignable (GH3631)
This case is rarely used, and there are plently of alternatives. This preserves the iloc API to be purely positional
based.
In [10]: df = DataFrame(lrange(5), list('ABCDE'), columns=['a'])
In [12]: mask
Out[12]:
A True
B False
C True
D False
E True
Name: a, dtype: bool
[3 rows x 1 columns]
[3 rows x 1 columns]
With
import pandas as pd
pd.read_excel('path_to_file.xls', 'Sheet1', index_col=None, na_values=['NA'])
DataFrame.to_html and DataFrame.to_latex now accept a path for their first argument (GH3702)
Do not allow astypes on datetime64[ns] except to object, and timedelta64[ns] to object/int
(GH3425)
The behavior of datetime64 dtypes has changed with respect to certain so-called reduction operations
(GH3726). The following operations now raise a TypeError when perfomed on a Series and return an
empty Series when performed on a DataFrame similar to performing these operations on, for example, a
DataFrame of slice objects:
sum, prod, mean, std, var, skew, kurt, corr, and cov
read_html now defaults to None when reading, and falls back on bs4 + html5lib when lxml fails to
parse. a list of parsers to try until success is also valid
The internal pandas class hierarchy has changed (slightly). The previous PandasObject now is called
PandasContainer and a new PandasObject has become the baseclass for PandasContainer as well
as Index, Categorical, GroupBy, SparseList, and SparseArray (+ their base classes). Currently,
PandasObject provides string methods (from StringMixin). (GH4090, GH4092)
New StringMixin that, given a __unicode__ method, gets python 2 and python 3 compatible string
methods (__str__, __bytes__, and __repr__). Plus string safety throughout. Now employed in many
places throughout the pandas library. (GH4090, GH4092)
pd.read_html() can now parse HTML strings, files or urls and return DataFrames, courtesy of @cpcloud.
(GH3477, GH3605, GH3606, GH3616). It works with a single parser backend: BeautifulSoup4 + html5lib See
the docs
You can use pd.read_html() to read the output from DataFrame.to_html() like so
In [15]: df = DataFrame({'a': range(3), 'b': list('abc')})
In [16]: print(df)
a b
0 0 a
1 1 b
2 2 c
[3 rows x 2 columns]
[3 rows x 2 columns]
Note that alist here is a Python list so pd.read_html() and DataFrame.to_html() are not in-
verses.
pd.read_html() no longer performs hard conversion of date strings (GH3656).
Warning: You may have to install an older version of BeautifulSoup4, See the installation docs
Added module for reading and writing Stata files: pandas.io.stata (GH1512) accessable via
read_stata top-level function for reading, and to_stata DataFrame method for writing, See the docs
Added module for reading and writing json format files: pandas.io.json accessable via read_json top-
level function for reading, and to_json DataFrame method for writing, See the docs various issues (GH1226,
GH3804, GH3876, GH3867, GH1305)
MultiIndex column support for reading and writing csv format files
The header option in read_csv now accepts a list of the rows from which to read the index.
The option, tupleize_cols can now be specified in both to_csv and read_csv, to provide com-
patiblity for the pre 0.12 behavior of writing and reading MultIndex columns via a list of tuples. The
default in 0.12 is to write lists of tuples and not interpret list of tuples as a MultiIndex column.
Note: The default behavior in 0.12 remains unchanged from prior versions, but starting with 0.13, the
default to write and read MultiIndex columns will be in the new format. (GH3571, GH1651, GH3141)
If an index_col is not specified (e.g. you dont have an index, or wrote it with df.to_csv(...,
index=False), then any names on the columns index will be lost.
In [20]: from pandas.util.testing import makeCustomDataframe as mkdf
In [21]: df = mkdf(5,3,r_idx_nlevels=2,c_idx_nlevels=4)
In [22]: df.to_csv('mi.csv',tupleize_cols=False)
In [23]: print(open('mi.csv').read())
C0,,C_l0_g0,C_l0_g1,C_l0_g2
C1,,C_l1_g0,C_l1_g1,C_l1_g2
C2,,C_l2_g0,C_l2_g1,C_l2_g2
C3,,C_l3_g0,C_l3_g1,C_l3_g2
R0,R1,,,
R_l0_g0,R_l1_g0,R0C0,R0C1,R0C2
R_l0_g1,R_l1_g1,R1C0,R1C1,R1C2
R_l0_g2,R_l1_g2,R2C0,R2C1,R2C2
R_l0_g3,R_l1_g3,R3C0,R3C1,R3C2
R_l0_g4,R_l1_g4,R4C0,R4C1,R4C2
In [24]: pd.read_csv('mi.csv',header=[0,1,2,3],index_col=[0,1],tupleize_cols=False)
Out[24]:
C0 C_l0_g0 C_l0_g1 C_l0_g2
C1 C_l1_g0 C_l1_g1 C_l1_g2
C2 C_l2_g0 C_l2_g1 C_l2_g2
C3 C_l3_g0 C_l3_g1 C_l3_g2
R0 R1
R_l0_g0 R_l1_g0 R0C0 R0C1 R0C2
R_l0_g1 R_l1_g1 R1C0 R1C1 R1C2
R_l0_g2 R_l1_g2 R2C0 R2C1 R2C2
R_l0_g3 R_l1_g3 R3C0 R3C1 R3C2
R_l0_g4 R_l1_g4 R4C0 R4C1 R4C2
[5 rows x 3 columns]
In [26]: DataFrame(randn(10,2)).to_hdf(path,'df',table=True)
1 -0.402761 -0.246604
2 -0.288433 -0.763434
[3 rows x 2 columns]
0 1
3 2.069526 -1.203569
4 0.591830 0.841159
5 -0.501083 -0.816561
[3 rows x 2 columns]
0 1
6 -0.207082 -0.664112
7 0.580411 -0.965628
8 -0.038605 -0.460478
[3 rows x 2 columns]
0 1
9 -0.310458 0.866493
[1 rows x 2 columns]
read_csv will now throw a more informative error message when a file contains no columns, e.g., all newline
characters
DataFrame.replace() now allows regular expressions on contained Series with object dtype. See the
examples section in the regular docs Replacing via String Expression
For example you can do
In [28]: df = DataFrame({'a': list('ab..'), 'b': [1, 2, 3, 4]})
[4 rows x 2 columns]
to replace all occurrences of the string . with zero or more instances of surrounding whitespace with NaN.
Regular string replacement still works as expected. For example, you can do
In [30]: df.replace('.', np.nan)
Out[30]:
a b
0 a 1
1 b 2
2 NaN 3
3 NaN 4
[4 rows x 2 columns]
pd.melt() now accepts the optional parameters var_name and value_name to specify custom column
names of the returned DataFrame.
pd.set_option() now allows N option, value pairs (GH3667).
Lets say that we had an option a.b and another option b.c. We can set them at the same
time:
In [31]: pd.get_option('a.b')
Out[31]: 2
In [32]: pd.get_option('b.c')
Out[32]: 3
In [34]: pd.get_option('a.b')
Out[34]: 1
In [35]: pd.get_option('b.c')
Out[35]: 4
The filter method for group objects returns a subset of the original object. Suppose we want to take only
elements that belong to groups with a group sum greater than 2.
In [36]: sf = Series([1, 1, 2, 3, 3, 3])
The argument of filter must a function that, applied to the group as a whole, returns True or False.
Another useful operation is filtering out elements that belong to groups with only a couple members.
In [38]: dff = DataFrame({'A': np.arange(8), 'B': list('aabbbbcc')})
[4 rows x 2 columns]
Alternatively, instead of dropping the offending groups, we can return a like-indexed objects where the groups
that do not pass the filter are filled with NaNs.
In [40]: dff.groupby('B').filter(lambda x: len(x) > 2, dropna=False)
Out[40]:
A B
0 NaN NaN
1 NaN NaN
2 2 b
3 3 b
4 4 b
5 5 b
6 NaN NaN
7 NaN NaN
[8 rows x 2 columns]
Series and DataFrame hist methods now take a figsize argument (GH3834)
DatetimeIndexes no longer try to convert mixed-integer indexes during join operations (GH3877)
Timestamp.min and Timestamp.max now represent valid Timestamp instances instead of the default date-
time.min and datetime.max (respectively), thanks @SleepingPills
read_html now raises when no tables are found and BeautifulSoup==4.2.0 is detected (GH4214)
Added experimental CustomBusinessDay class to support DateOffsets with custom holiday calendars
and custom weekmasks. (GH2301)
Note: This uses the numpy.busdaycalendar API introduced in Numpy 1.7 and therefore requires Numpy
1.7.0 or newer.
Plotting functions now raise a TypeError before trying to plot anything if the associated objects have have a
dtype of object (GH1818, GH3572, GH3911, GH3912), but they will try to convert object arrays to numeric
arrays if possible so that you can still plot, for example, an object array with floats. This happens before any
drawing takes place which elimnates any spurious plots from showing up.
fillna methods now raise a TypeError if the value parameter is a list or tuple.
Series.str now supports iteration (GH3638). You can iterate over the individual elements of each string in
the Series. Each iteration yields yields a Series with either a single character at each index of the original
Series or NaN. For example,
In [50]: strs = 'go', 'bow', 'joe', 'slow'
In [51]: ds = Series(strs)
In [53]: s
Out[53]:
0 NaN
1 NaN
2 NaN
3 w
dtype: object
The last element yielded by the iterator will be a Series containing the last element of the longest string in
the Series with all other elements being NaN. Here since slow is the longest string and there are no other
strings with the same length w is the only non-null string in the yielded Series.
HDFStore
will retain index attributes (freq,tz,name) on recreation (GH3499)
will warn with a AttributeConflictWarning if you are attempting to append an index with a
different frequency than the existing, or attempting to append an index with a different name than the
existing
support datelike columns with a timezone as data_columns (GH2852)
This is a major release from 0.10.1 and includes many new features and enhancements along with a large number of
bug fixes. The methods of Selecting Data have had quite a number of additions, and Dtype support is now full-fledged.
There are also a number of important API changes that long-time pandas users should pay close attention to.
There is a new section in the documentation, 10 Minutes to Pandas, primarily geared to new users.
There is a new section in the documentation, Cookbook, a collection of useful recipes in pandas (and that we want
contributions!).
There are several libraries that are now Recommended Dependencies
Starting in 0.11.0, object selection has had a number of user-requested additions in order to support more explicit
location based indexing. Pandas now supports three types of multi-axis indexing.
.loc is strictly label based, will raise KeyError when the items are not found, allowed inputs are:
A single label, e.g. 5 or a, (note that 5 is interpreted as a label of the index. This use is not an integer
position along the index)
A list or array of labels [a, b, c]
A slice object with labels a:f, (note that contrary to usual python slices, both the start and the stop
are included!)
A boolean array
See more at Selection by Label
.iloc is strictly integer position based (from 0 to length-1 of the axis), will raise IndexError when the
requested indicies are out of bounds. Allowed inputs are:
An integer e.g. 5
A list or array of integers [4, 3, 0]
A slice object with ints 1:7
A boolean array
See more at Selection by Position
.ix supports mixed integer and label based access. It is primarily label based, but will fallback to integer
positional access. .ix is the most general and will support any of the inputs to .loc and .iloc, as well as
support for floating point label schemes. .ix is especially useful when dealing with mixed positional and label
based hierarchial indexes.
As using integer slices with .ix have different behavior depending on whether the slice is interpreted as position
based or label based, its usually better to be explicit and use .iloc or .loc.
See more at Advanced Indexing and Advanced Hierarchical.
1.12.3 Dtypes
Numeric dtypes will propagate and can coexist in DataFrames. If a dtype is passed (either directly via the dtype
keyword, a passed ndarray, or a passed Series, then it will be preserved in DataFrame operations. Furthermore,
different numeric dtypes will NOT be combined. The following example will give you a taste.
In [1]: df1 = DataFrame(randn(8, 1), columns = ['A'], dtype = 'float32')
In [2]: df1
Out[2]:
A
0 0.245972
1 0.319442
2 1.378512
3 0.292502
4 0.329791
5 1.392047
6 0.769914
7 -2.472300
[8 rows x 1 columns]
In [3]: df1.dtypes
Out[3]:
A float32
dtype: object
In [5]: df2
Out[5]:
A B C
0 -0.611328 -0.270630 255
1 1.044922 -1.685677 0
2 1.503906 -0.440747 0
3 -1.328125 -0.115070 1
4 1.024414 -0.632102 0
5 0.660156 -0.585977 0
6 1.236328 -1.444787 0
7 -2.169922 -0.201135 0
[8 rows x 3 columns]
In [6]: df2.dtypes
Out[6]:
A float16
B float64
C uint8
dtype: object
In [8]: df3
Out[8]:
A B C
0 -0.365356 -0.270630 255
1 1.364364 -1.685677 0
2 2.882418 -0.440747 0
3 -1.035623 -0.115070 1
4 1.354205 -0.632102 0
5 2.052203 -0.585977 0
6 2.006243 -1.444787 0
7 -4.642221 -0.201135 0
[8 rows x 3 columns]
In [9]: df3.dtypes
Out[9]:
A float32
B float64
C float64
dtype: object
This is lower-common-denomicator upcasting, meaning you get the dtype which can accomodate all of the types
In [10]: df3.values.dtype
Out[10]: dtype('float64')
Conversion
In [11]: df3.astype('float32').dtypes
Out[11]:
A float32
B float32
C float32
dtype: object
Mixed Conversion
In [14]: df3.convert_objects(convert_numeric=True).dtypes
Out[14]:
A float32
B float64
C float64
D float64
E int64
dtype: object
In [17]: df3.dtypes
Out[17]:
A float32
B float64
C float64
D float16
E int32
dtype: object
In [20]: s.convert_objects(convert_dates='coerce')
Out[20]:
0 2001-01-01
1 NaT
2 NaT
3 NaT
4 2001-01-04
5 2001-01-05
dtype: datetime64[ns]
Platform Gotchas
Starting in 0.11.0, construction of DataFrame/Series will use default dtypes of int64 and float64, regardless
of platform. This is not an apparent change from earlier versions of pandas. If you specify dtypes, they WILL be
respected, however (GH2837)
The following will all result in int64 dtypes
In [21]: DataFrame([1,2],columns=['a']).dtypes
Out[21]:
a int64
dtype: object
In [26]: dfi
Out[26]:
A B C D E
0 0 0 255 1 1
1 1 -1 0 1 1
2 2 0 0 1 1
3 -1 0 1 1 1
4 1 0 0 1 1
5 2 0 0 1 1
6 2 -1 0 1 1
7 -4 0 0 1 1
[8 rows x 5 columns]
In [27]: dfi.dtypes
Out[27]:
A int32
B int32
C int32
D int64
E int32
dtype: object
In [29]: casted
Out[29]:
A B C D E
0 NaN NaN 255 1 1
1 1 NaN NaN 1 1
2 2 NaN NaN 1 1
3 NaN NaN 1 1 1
4 1 NaN NaN 1 1
5 2 NaN NaN 1 1
6 2 NaN NaN 1 1
7 NaN NaN NaN 1 1
[8 rows x 5 columns]
In [30]: casted.dtypes
Out[30]:
A float64
B float64
C float64
D int64
E int32
dtype: object
In [33]: df4.dtypes
Out[33]:
A float32
B float64
C float64
D float16
E int32
dtype: object
In [35]: casted
Out[35]:
A B C D E
0 NaN NaN 255 1 1
1 1.364364 NaN NaN 1 1
2 2.882418 NaN NaN 1 1
3 NaN NaN 1 1 1
4 1.354205 NaN NaN 1 1
5 2.052203 NaN NaN 1 1
6 2.006243 NaN NaN 1 1
7 NaN NaN NaN 1 1
[8 rows x 5 columns]
In [36]: casted.dtypes
Out[36]:
A float32
B float64
C float64
D float16
E int32
dtype: object
Datetime64[ns] columns in a DataFrame (or a Series) allow the use of np.nan to indicate a nan value, in ad-
dition to the traditional NaT, or not-a-time. This allows convenient nan setting in a generic way. Furthermore
datetime64[ns] columns are created by default, when passed datetimelike objects (this change was introduced in
In [39]: df
Out[39]:
A B timestamp
2001-01-02 -1.448835 0.153437 2001-01-03
2001-01-03 -1.123570 -0.791498 2001-01-03
2001-01-04 0.105400 1.262401 2001-01-03
2001-01-05 -0.721844 -0.647645 2001-01-03
2001-01-06 -0.830631 0.761823 2001-01-03
2001-01-07 0.597819 1.045558 2001-01-03
[6 rows x 3 columns]
In [42]: df
Out[42]:
A B timestamp
2001-01-02 -1.448835 0.153437 2001-01-03
2001-01-03 -1.123570 -0.791498 2001-01-03
2001-01-04 NaN 1.262401 NaT
2001-01-05 NaN -0.647645 NaT
2001-01-06 -0.830631 0.761823 2001-01-03
2001-01-07 0.597819 1.045558 2001-01-03
[6 rows x 3 columns]
In [45]: s.dtype
Out[45]: dtype('<M8[ns]')
In [47]: s
Out[47]:
0 2001-01-02
1 NaT
2 2001-01-02
dtype: datetime64[ns]
In [48]: s.dtype
Out[48]: dtype('<M8[ns]')
In [49]: s = s.astype('O')
In [50]: s
Out[50]:
0 2001-01-02 00:00:00
1 NaN
2 2001-01-02 00:00:00
dtype: object
In [51]: s.dtype
Out[51]: dtype('O')
1.12.8 Enhancements
In [53]: df.to_hdf('store.h5','table',append=True)
[2 rows x 2 columns]
provide dotted attribute access to get from stores, e.g. store.df == store[df]
new keywords iterator=boolean, and chunksize=number_in_a_chunk are provided to sup-
port iteration on select and select_as_multiple (GH3076)
You can now select timestamps from an unordered timeseries similarly to an ordered timeseries (GH2437)
You can now select with a string from a DataFrame with a datelike index, in a similar way to a Series (GH3070)
In [56]: ts = Series(np.random.rand(len(idx)),index=idx)
In [57]: ts['2001']
Out[57]:
2001-10-31 0.483450
2001-11-30 0.407530
2001-12-31 0.965096
Freq: M, dtype: float64
In [59]: df['2001']
Out[59]:
A
2001-10-31 0.483450
2001-11-30 0.407530
2001-12-31 0.965096
[3 rows x 1 columns]
In [61]: p
Out[61]:
<class 'pandas.core.panel.Panel'>
Dimensions: 3 (items) x 4 (major_axis) x 4 (minor_axis)
Items axis: ItemA to ItemC
Major_axis axis: 2001-01-02 00:00:00 to 2001-01-05 00:00:00
Minor_axis axis: A to D
In [62]: p.reindex(items=['ItemA']).squeeze()
Out[62]:
A B C D
2001-01-02 0.396537 0.534880 -0.488797 -1.539385
2001-01-03 -0.829037 0.306681 -0.331032 1.544977
2001-01-04 -0.621754 1.026208 -0.413106 -1.490869
2001-01-05 -1.253235 -0.538879 -1.487449 -1.426475
[4 rows x 4 columns]
In [63]: p.reindex(items=['ItemA'],minor=['B']).squeeze()
Out[63]:
2001-01-02 0.534880
2001-01-03 0.306681
2001-01-04 1.026208
2001-01-05 -0.538879
Freq: D, Name: B, dtype: float64
In pd.io.data.Options,
Fix bug when trying to fetch data for the current month when already past expiry.
Now using lxml to scrape html instead of BeautifulSoup (lxml was faster).
New instance variables for calls and puts are automatically created when a method that creates them is
called. This works for current month where the instance variables are simply calls and puts. Also
works for future expiry months and save the instance variable as callsMMYY or putsMMYY, where
MMYY are, respectively, the month and year of the options expiry.
Options.get_near_stock_price now allows the user to specify the month for which to get rele-
vant options data.
Options.get_forward_data now has optional kwargs near and above_below. This allows the
user to specify if they would like to only return forward looking data for options near the current stock
price. This just obtains the data from Options.get_near_stock_price instead of Options.get_xxx_data()
(GH2758).
Cursor coordinate information is now displayed in time-series plots.
added option display.max_seq_items to control the number of elements printed per sequence pprinting it.
(GH2979)
added option display.chop_threshold to control display of small numerical values. (GH2739)
added option display.max_info_rows to prevent verbose_info from being calculated for frames above 1M rows
(configurable). (GH2807, GH2918)
value_counts() now accepts a normalize argument, for normalized histograms. (GH2710).
DataFrame.from_records now accepts not only dicts but any instance of the collections.Mapping ABC.
added option display.mpl_style providing a sleeker visual style for plots. Based on
https://gist.github.com/huyng/816622 (GH3075).
Treat boolean values as integers (values 1 and 0) for numeric operations. (GH2641)
to_html() now accepts an optional escape argument to control reserved HTML character escaping (enabled
by default) and escapes &, in addition to < and >. (GH2919)
See the full release notes or issue tracker on GitHub for a complete list.
This is a minor release from 0.10.0 and includes new features, enhancements, and bug fixes. In particular, there is
substantial new HDFStore functionality contributed by Jeff Reback.
An undesired API breakage with functions taking the inplace option has been reverted and deprecation warnings
added.
Functions taking an inplace option return the calling object as before. A deprecation message has been added
Groupby aggregations Max/Min no longer exclude non-numeric data (GH2700)
Resampling an empty DataFrame now returns an empty DataFrame instead of raising an exception (GH2640)
The file reader will now raise an exception when NA values are found in an explicitly specified integer column
instead of converting the column to float (GH2631)
DatetimeIndex.unique now returns a DatetimeIndex with the same name and
timezone instead of an array (GH2563)
1.13.3 HDFStore
You may need to upgrade your existing data files. Please visit the compatibility section in the main docs.
You can designate (and index) certain columns that you want to be able to perform queries on a table, by passing a list
to data_columns
In [1]: store = HDFStore('store.h5')
In [7]: df
Out[7]:
A B C string string2
2000-01-01 -1.601262 -0.256718 0.239369 foo cool
2000-01-02 0.174122 -1.131794 -1.948006 foo cool
2000-01-03 0.980347 -0.674429 -0.361633 foo cool
2000-01-04 -0.761218 1.768215 0.152288 foo cool
2000-01-05 -0.862613 -0.210968 -0.859278 NaN cool
2000-01-06 1.498195 0.462413 -0.647604 NaN cool
2000-01-07 1.511487 -0.727189 -0.342928 foo cool
2000-01-08 -0.007364 1.427674 0.104020 bar cool
[8 rows x 5 columns]
# on-disk operations
In [8]: store.append('df', df, data_columns = ['B','C','string','string2'])
[1 rows x 5 columns]
[1 rows x 5 columns]
In [16]: df_mixed1
Out[16]:
A B C string string2 datetime64
2000-01-01 -1.601262 -0.256718 0.239369 foo cool 2001-01-02
2000-01-02 0.174122 -1.131794 -1.948006 foo cool 2001-01-02
2000-01-03 0.980347 -0.674429 -0.361633 foo cool 2001-01-02
2000-01-04 NaN NaN 0.152288 foo cool 2001-01-02
2000-01-05 -0.862613 -0.210968 -0.859278 NaN cool 2001-01-02
2000-01-06 1.498195 0.462413 -0.647604 NaN cool 2001-01-02
2000-01-07 1.511487 -0.727189 -0.342928 foo cool 2001-01-02
2000-01-08 -0.007364 1.427674 0.104020 bar cool 2001-01-02
[8 rows x 6 columns]
In [17]: df_mixed1.get_dtype_counts()
Out[17]:
datetime64[ns] 1
float64 3
object 2
dtype: int64
You can pass columns keyword to select to filter a list of the return columns, this is equivalent to passing a
Term(columns,list_of_columns_to_filter)
In [18]: store.select('df',columns = ['A','B'])
Out[18]:
A B
2000-01-01 -1.601262 -0.256718
2000-01-02 0.174122 -1.131794
2000-01-03 0.980347 -0.674429
2000-01-04 -0.761218 1.768215
2000-01-05 -0.862613 -0.210968
2000-01-06 1.498195 0.462413
2000-01-07 1.511487 -0.727189
2000-01-08 -0.007364 1.427674
[8 rows x 2 columns]
In [21]: df
Out[21]:
A B C
foo bar
foo one 2.052171 -1.230963 -0.019240
two -1.713238 0.838912 -0.637855
three 0.215109 -1.515362 1.586924
bar one -0.447974 -1.573998 0.630925
two -0.071659 -1.277640 -0.102206
baz two 0.870302 1.275280 -1.199212
three 1.060780 1.673018 1.249874
qux one 1.458210 -0.710542 0.825392
two 1.557329 1.993441 -0.616293
three 0.150468 0.132104 0.580923
In [22]: store.append('mi',df)
In [23]: store.select('mi')
Out[23]:
A B C
foo bar
foo one 2.052171 -1.230963 -0.019240
two -1.713238 0.838912 -0.637855
three 0.215109 -1.515362 1.586924
bar one -0.447974 -1.573998 0.630925
two -0.071659 -1.277640 -0.102206
baz two 0.870302 1.275280 -1.199212
three 1.060780 1.673018 1.249874
qux one 1.458210 -0.710542 0.825392
two 1.557329 1.993441 -0.616293
three 0.150468 0.132104 0.580923
[2 rows x 3 columns]
Multi-table creation via append_to_multiple and selection via select_as_multiple can create/select from
multiple tables and return a combined result, by using where on a selector table.
In [28]: store
Out[28]:
<class 'pandas.io.pytables.HDFStore'>
File path: store.h5
/df frame_table (typ->appendable,nrows->8,ncols->5,indexers->[index],dc->[B,C,strin
/df1_mt frame_table (typ->appendable,nrows->8,ncols->2,indexers->[index],dc->[A,B])
/df2_mt frame_table (typ->appendable,nrows->8,ncols->5,indexers->[index])
/df_mixed frame_table (typ->appendable,nrows->8,ncols->6,indexers->[index])
/mi frame_table (typ->appendable_multi,nrows->10,ncols->5,indexers->[index],dc->[ba
[8 rows x 2 columns]
In [30]: store.select('df2_mt')
Out[30]:
C D E F foo
2000-01-01 -0.431163 0.016640 0.904578 -1.645852 bar
2000-01-02 0.800353 -0.451572 0.831767 0.228760 bar
2000-01-03 1.239198 0.185437 -0.540770 -0.370038 bar
2000-01-04 -0.040863 0.290110 -0.096145 1.717830 bar
2000-01-05 -0.134024 -0.205969 1.348944 -1.198246 bar
2000-01-06 0.059493 -0.460111 -1.565401 -0.025706 bar
2000-01-07 -0.302741 0.261551 -0.066342 0.897097 bar
2000-01-08 0.582752 -1.490764 -0.639757 -0.952750 bar
[8 rows x 5 columns]
# as a multiple
In [31]: store.select_as_multiple(['df1_mt','df2_mt'], where = [ 'A>0','B>0' ], selector = 'df1_mt')
Out[31]:
A B C D E F foo
2000-01-04 1.298390 1.662964 -0.040863 0.290110 -0.096145 1.717830 bar
2000-01-07 0.942864 2.502156 -0.302741 0.261551 -0.066342 0.897097 bar
[2 rows x 7 columns]
Enhancements
Several bug fixed for Series operations when dtype is datetime64 (GH2689, GH2629, GH2626)
See the full release notes or issue tracker on GitHub for a complete list.
This is a major release from 0.9.1 and includes many new features and enhancements along with a large number of
bug fixes. There are also a number of important API changes that long-time pandas users should pay close attention
to.
The delimited file parsing engine (the guts of read_csv and read_table) has been rewritten from the ground up
and now uses a fraction the amount of memory while parsing, while being 40% or more faster in most use cases (in
some cases much faster).
There are also many new features:
Much-improved Unicode handling via the encoding option.
Column filtering (usecols)
Dtype specification (dtype argument)
Ability to specify strings to be recognized as True/False
Ability to yield NumPy record arrays (as_recarray)
High performance delim_whitespace option
Decimal format (e.g. European format) specification
Easier CSV dialect options: escapechar, lineterminator, quotechar, etc.
More robust handling of many exceptional kinds of files observed in the wild
In [3]: df
Out[3]:
0 1 2 3
2000-01-01 -0.892402 0.505987 -0.681624 0.850162
2000-01-02 0.586586 1.175843 -0.160391 0.481679
2000-01-03 0.408279 1.641246 0.383888 -1.495227
[6 rows x 4 columns]
# deprecated now
In [4]: df - df[0]
Out[4]:
0 1 2 3
2000-01-01 0 1.398389 0.210778 1.742564
2000-01-02 0 0.589256 -0.746978 -0.104908
2000-01-03 0 1.232968 -0.024391 -1.903505
2000-01-04 0 -1.968368 -1.441350 -0.648158
2000-01-05 0 1.967410 -0.159471 0.144338
2000-01-06 0 0.674682 0.341344 -1.404109
[6 rows x 4 columns]
[6 rows x 4 columns]
You will get a deprecation warning in the 0.10.x series, and the deprecated functionality will be removed in 0.11 or
later.
Altered resample default behavior
The default time series resample binning behavior of daily D and higher frequencies has been changed to
closed=left, label=left. Lower nfrequencies are unaffected. The prior defaults were causing a great
deal of confusion for users, especially resampling data to daily frequency (which labeled the aggregated group with
the end of the interval: the next day).
Note:
In [6]: dates = pd.date_range('1/1/2000', '1/5/2000', freq='4h')
In [8]: series
Out[8]:
2000-01-01 00:00:00 0
2000-01-01 04:00:00 1
2000-01-01 08:00:00 2
2000-01-01 12:00:00 3
2000-01-01 16:00:00 4
2000-01-01 20:00:00 5
2000-01-02 00:00:00 6
..
2000-01-04 00:00:00 18
2000-01-04 04:00:00 19
2000-01-04 08:00:00 20
2000-01-04 12:00:00 21
2000-01-04 16:00:00 22
2000-01-04 20:00:00 23
2000-01-05 00:00:00 24
Freq: 4H, dtype: int32
# old behavior
In [10]: series.resample('D', how='sum', closed='right', label='right')
Out[10]:
2000-01-01 0
2000-01-02 21
2000-01-03 57
2000-01-04 93
2000-01-05 129
Freq: D, dtype: int32
Infinity and negative infinity are no longer treated as NA by isnull and notnull. That they every were was
a relic of early pandas. This behavior can be re-enabled globally by the mode.use_inf_as_null option:
In [11]: s = pd.Series([1.5, np.inf, 3.4, -np.inf])
In [12]: pd.isnull(s)
Out[12]:
0 False
1 False
2 False
3 False
dtype: bool
In [13]: s.fillna(0)
Out[13]:
0 1.500000
1 inf
2 3.400000
3 -inf
dtype: float64
In [15]: pd.isnull(s)
Out[15]:
0 False
1 True
2 False
3 True
dtype: bool
In [16]: s.fillna(0)
Out[16]:
0 1.5
1 0.0
2 3.4
3 0.0
dtype: float64
In [17]: pd.reset_option('use_inf_as_null')
Methods with the inplace option now all return None instead of the calling object. E.g. code written like
df = df.fillna(0, inplace=True) may stop working. To fix, simply delete the unnecessary variable
assignment.
pandas.merge no longer sorts the group keys (sort=False) by default. This was done for performance
reasons: the group-key sorting is often one of the more expensive parts of the computation and is often unnec-
essary.
The default column names for a file with no header have been changed to the integers 0 through N - 1. This
is to create consistency with the DataFrame constructor with no columns specified. The v0.9.0 behavior (names
X0, X1, ...) can be reproduced by specifying prefix=X:
In [18]: data= 'a,b,c\n1,Yes,2\n3,No,4'
In [19]: print(data)
a,b,c
1,Yes,2
3,No,4
[3 rows x 3 columns]
[3 rows x 3 columns]
Values like Yes and No are not interpreted as boolean by default, though this can be controlled by new
true_values and false_values arguments:
In [22]: print(data)
a,b,c
1,Yes,2
3,No,4
In [23]: pd.read_csv(StringIO(data))
Out[23]:
a b c
0 1 Yes 2
1 3 No 4
[2 rows x 3 columns]
[2 rows x 3 columns]
The file parsers will not recognize non-string values arising from a converter function as NA if passed in the
na_values argument. Its better to do post-processing using the replace function instead.
Calling fillna on Series or DataFrame with no arguments is no longer valid code. You must either specify a
fill value or an interpolation method:
In [25]: s = Series([np.nan, 1., 2., np.nan, 4])
In [26]: s
Out[26]:
0 NaN
1 1
2 2
3 NaN
4 4
dtype: float64
In [27]: s.fillna(0)
Out[27]:
0 0
1 1
2 2
3 0
4 4
dtype: float64
In [28]: s.fillna(method='pad')
Out[28]:
0 NaN
1 1
2 2
3 2
4 4
dtype: float64
Series.apply will now operate on a returned value from the applied function, that is itself a series, and
In [31]: s = Series(np.random.rand(5))
In [32]: s
Out[32]:
0 0.013135
1 0.909855
2 0.098093
3 0.023540
4 0.141354
dtype: float64
In [33]: s.apply(f)
Out[33]:
x x^2
0 0.013135 0.000173
1 0.909855 0.827836
2 0.098093 0.009622
3 0.023540 0.000554
4 0.141354 0.019981
[5 rows x 2 columns]
Instead of printing the summary information, pandas now splits the string representation across multiple rows by
default:
In [35]: wide_frame = DataFrame(randn(5, 16))
In [36]: wide_frame
Out[36]:
0 1 2 3 4 5 6 \
0 2.520045 1.570114 -0.360875 -0.880096 0.235532 0.207232 -1.983857
1 0.422194 0.288403 -0.487393 -0.777639 0.055865 1.383381 0.085638
2 0.585174 -0.568825 -0.719412 1.191340 -0.456362 0.089931 0.776079
7 8 9 10 11 12 13 \
0 -1.702547 -1.621234 -0.906840 1.014601 -0.475108 -0.358944 1.262942
1 0.246392 0.965887 0.246354 -0.727728 -0.094414 -0.276854 0.158399
2 0.752889 -1.195795 -1.425911 -0.548829 0.774225 0.740501 1.510263
3 0.054399 0.241963 -0.471786 0.314510 -0.059986 -2.069319 -1.115104
4 1.695803 -1.025917 -0.910942 0.426805 -0.131749 0.432600 0.044671
14 15
0 -0.412451 -0.462580
1 -0.277255 1.331263
2 -1.642511 0.432560
3 -0.369325 -1.502617
4 -0.341265 1.844536
[5 rows x 16 columns]
The old behavior of printing out summary information can be achieved via the expand_frame_repr print option:
In [37]: pd.set_option('expand_frame_repr', False)
In [38]: wide_frame
Out[38]:
0 1 2 3 4 5 6 7 8 9
0 2.520045 1.570114 -0.360875 -0.880096 0.235532 0.207232 -1.983857 -1.702547 -1.621234 -0.906840
1 0.422194 0.288403 -0.487393 -0.777639 0.055865 1.383381 0.085638 0.246392 0.965887 0.246354
2 0.585174 -0.568825 -0.719412 1.191340 -0.456362 0.089931 0.776079 0.752889 -1.195795 -1.425911
3 1.218080 -0.564705 -0.581790 0.286071 0.048725 1.002440 1.276582 0.054399 0.241963 -0.471786
4 -0.376280 0.511936 -0.116412 -0.625256 -0.550627 1.261433 -0.552429 1.695803 -1.025917 -0.910942
[5 rows x 16 columns]
The width of each line can be changed via line_width (80 by default):
In [39]: pd.set_option('line_width', 40)
line_width has been deprecated, use display.width instead (currently both are
identical)
In [40]: wide_frame
Out[40]:
0 1 2 \
0 2.520045 1.570114 -0.360875
1 0.422194 0.288403 -0.487393
2 0.585174 -0.568825 -0.719412
3 1.218080 -0.564705 -0.581790
4 -0.376280 0.511936 -0.116412
3 4 5 \
0 -0.880096 0.235532 0.207232
1 -0.777639 0.055865 1.383381
2 1.191340 -0.456362 0.089931
3 0.286071 0.048725 1.002440
4 -0.625256 -0.550627 1.261433
6 7 8 \
0 -1.983857 -1.702547 -1.621234
9 10 11 \
0 -0.906840 1.014601 -0.475108
1 0.246354 -0.727728 -0.094414
2 -1.425911 -0.548829 0.774225
3 -0.471786 0.314510 -0.059986
4 -0.910942 0.426805 -0.131749
12 13 14 \
0 -0.358944 1.262942 -0.412451
1 -0.276854 0.158399 -0.277255
2 0.740501 1.510263 -1.642511
3 -2.069319 -1.115104 -0.369325
4 0.432600 0.044671 -0.341265
15
0 -0.462580
1 1.331263
2 0.432560
3 -1.502617
4 1.844536
[5 rows x 16 columns]
Docs for PyTables Table format & several enhancements to the api. Here is a taste of what to expect.
In [41]: store = HDFStore('store.h5')
In [43]: df
Out[43]:
A B C
2000-01-01 -2.036047 0.000830 -0.955697
2000-01-02 -0.898872 -0.725411 0.059904
2000-01-03 -0.449644 1.082900 -1.221265
2000-01-04 0.361078 1.330704 0.855932
2000-01-05 -1.216718 1.488887 0.018993
2000-01-06 -0.877046 0.045976 0.437274
2000-01-07 -0.567182 -0.888657 -0.556383
2000-01-08 0.655457 1.117949 -2.782376
[8 rows x 3 columns]
In [48]: store
Out[48]:
<class 'pandas.io.pytables.HDFStore'>
File path: store.h5
/df frame_table (typ->appendable,nrows->8,ncols->3,indexers->[index])
[8 rows x 3 columns]
In [51]: wp
Out[51]:
<class 'pandas.core.panel.Panel'>
Dimensions: 2 (items) x 5 (major_axis) x 4 (minor_axis)
Items axis: Item1 to Item2
Major_axis axis: 2000-01-01 00:00:00 to 2000-01-05 00:00:00
Minor_axis axis: A to D
# storing a panel
In [52]: store.append('wp',wp)
In [55]: store.select('wp')
Out[55]:
<class 'pandas.core.panel.Panel'>
Dimensions: 2 (items) x 3 (major_axis) x 4 (minor_axis)
Items axis: Item1 to Item2
Major_axis axis: 2000-01-01 00:00:00 to 2000-01-03 00:00:00
Minor_axis axis: A to D
# deleting a store
In [56]: del store['df']
In [57]: store
Out[57]:
<class 'pandas.io.pytables.HDFStore'>
File path: store.h5
/wp wide_table (typ->appendable,nrows->12,ncols->2,indexers->[major_axis,minor_axis])
Enhancements
added ability to hierarchical keys
In [58]: store.put('foo/bar/bah', df)
In [61]: store
Out[61]:
<class 'pandas.io.pytables.HDFStore'>
File path: store.h5
/foo/bar/bah frame (shape->[8,3])
/food/apple frame_table (typ->appendable,nrows->8,ncols->3,indexers->[index])
/food/orange frame_table (typ->appendable,nrows->8,ncols->3,indexers->[index])
/wp wide_table (typ->appendable,nrows->12,ncols->2,indexers->[major_ax
In [63]: store
Out[63]:
<class 'pandas.io.pytables.HDFStore'>
File path: store.h5
/foo/bar/bah frame (shape->[8,3])
/wp wide_table (typ->appendable,nrows->12,ncols->2,indexers->[major_ax
In [65]: df['int'] = 1
In [66]: store.append('df',df)
In [68]: df1
Out[68]:
A B C string int
2000-01-01 -2.036047 0.000830 -0.955697 string 1
2000-01-02 -0.898872 -0.725411 0.059904 string 1
[8 rows x 5 columns]
In [69]: df1.get_dtype_counts()
Out[69]:
float64 3
int64 1
object 1
dtype: int64
Adding experimental support for Panel4D and factory functions to create n-dimensional named panels. Docs for
NDim. Here is a taste of what to expect.
In [70]: p4d = Panel4D(randn(2, 2, 5, 4),
....: labels=['Label1','Label2'],
....: items=['Item1', 'Item2'],
....: major_axis=date_range('1/1/2000', periods=5),
In [71]: p4d
Out[71]:
<class 'pandas.core.panelnd.Panel4D'>
Dimensions: 2 (labels) x 2 (items) x 5 (major_axis) x 4 (minor_axis)
Labels axis: Label1 to Label2
Items axis: Item1 to Item2
Major_axis axis: 2000-01-01 00:00:00 to 2000-01-05 00:00:00
Minor_axis axis: A to D
See the full release notes or issue tracker on GitHub for a complete list.
This is a bugfix release from 0.9.0 and includes several new features and enhancements along with a large number of
bug fixes. The new features include by-column sort order for DataFrame and Series, improved NA handling for the
rank method, masking functions for DataFrame, and intraday time-series filtering for DataFrame.
Series.sort, DataFrame.sort, and DataFrame.sort_index can now be specified in a per-column manner to support
multiple sort orders (GH928)
In [1]: df = DataFrame(np.random.randint(0, 2, (6, 3)), columns=['A', 'B', 'C'])
[6 rows x 3 columns]
DataFrame.rank now supports additional argument values for the na_option parameter so missing values can
be assigned either the largest or the smallest rank (GH1508, GH2159)
In [3]: df = DataFrame(np.random.randn(6, 3), columns=['A', 'B', 'C'])
In [5]: df.rank()
Out[5]:
A B C
0 3 2 1
1 2 1 3
2 NaN NaN NaN
3 NaN NaN NaN
4 NaN NaN NaN
5 1 3 2
[6 rows x 3 columns]
In [6]: df.rank(na_option='top')
Out[6]:
A B C
0 6 5 4
1 5 4 6
2 2 2 2
3 2 2 2
4 2 2 2
5 4 6 5
[6 rows x 3 columns]
In [7]: df.rank(na_option='bottom')
Out[7]:
A B C
0 3 2 1
1 2 1 3
2 5 5 5
3 5 5 5
4 5 5 5
5 1 3 2
[6 rows x 3 columns]
DataFrame has new where and mask methods to select values according to a given boolean mask (GH2109,
GH2151)
DataFrame currently supports slicing via a boolean vector the same length as the DataFrame (inside
the []). The returned DataFrame has the same number of columns as the original, but is sliced on its
index.
In [8]: df = DataFrame(np.random.randn(5, 3), columns = ['A','B','C'])
In [9]: df
Out[9]:
A B C
0 0.706220 -1.130744 -0.690308
1 -0.885387 0.246004 1.986687
2 0.212595 -1.189832 -0.344258
3 0.816335 -1.514102 1.298184
4 0.089527 0.576687 -0.737750
[5 rows x 3 columns]
[4 rows x 3 columns]
If a DataFrame is sliced with a DataFrame based boolean condition (with the same size as the original
DataFrame), then a DataFrame the same size (index and columns) as the original is returned, with
elements that do not meet the boolean condition as NaN. This is accomplished via the new method
DataFrame.where. In addition, where takes an optional other argument for replacement.
In [11]: df[df>0]
Out[11]:
A B C
0 0.706220 NaN NaN
1 NaN 0.246004 1.986687
2 0.212595 NaN NaN
3 0.816335 NaN 1.298184
4 0.089527 0.576687 NaN
[5 rows x 3 columns]
In [12]: df.where(df>0)
Out[12]:
A B C
0 0.706220 NaN NaN
1 NaN 0.246004 1.986687
2 0.212595 NaN NaN
3 0.816335 NaN 1.298184
4 0.089527 0.576687 NaN
[5 rows x 3 columns]
In [13]: df.where(df>0,-df)
Out[13]:
A B C
0 0.706220 1.130744 0.690308
1 0.885387 0.246004 1.986687
2 0.212595 1.189832 0.344258
3 0.816335 1.514102 1.298184
4 0.089527 0.576687 0.737750
[5 rows x 3 columns]
Furthermore, where now aligns the input boolean condition (ndarray or DataFrame), such that partial
selection with setting is possible. This is analagous to partial setting via .ix (but on the contents rather
than the axis labels)
In [14]: df2 = df.copy()
In [16]: df2
Out[16]:
A B C
0 0.706220 -1.130744 -0.690308
1 -0.885387 3.000000 3.000000
2 3.000000 -1.189832 -0.344258
3 3.000000 -1.514102 3.000000
4 0.089527 0.576687 -0.737750
[5 rows x 3 columns]
A B C
0 0.706220 NaN NaN
1 NaN 0.246004 1.986687
2 0.212595 NaN NaN
3 0.816335 NaN 1.298184
4 0.089527 0.576687 NaN
[5 rows x 3 columns]
[7 rows x 3 columns]
Added option to disable pandas-style tick locators and formatters using series.plot(x_compat=True) or pan-
das.plot_params[x_compat] = True (GH2205)
Existing TimeSeries methods at_time and between_time were added to DataFrame (GH2149)
DataFrame.dot can now accept ndarrays (GH2042)
DataFrame.drop now supports non-unique indexes (GH2101)
Panel.shift now supports negative periods (GH2164)
DataFrame now support unary ~ operator (GH2110)
Upsampling data with a PeriodIndex will result in a higher frequency TimeSeries that spans the original time
window
In [20]: prng = period_range('2012Q1', periods=2, freq='Q')
In [22]: s.resample('M')
Out[22]:
2012-01 0.194513
2012-02 NaN
2012-03 NaN
2012-04 -0.854246
2012-05 NaN
2012-06 NaN
Freq: M, dtype: float64
Period.end_time now returns the last nanosecond in the time interval (GH2124, GH2125, GH1764)
In [23]: p = Period('2012')
In [24]: p.end_time
Out[24]: Timestamp('2012-12-31 23:59:59.999999999')
File parsers no longer coerce to float or bool for columns that have custom converters specified (GH2184)
In [25]: data = 'A,B,C\n00001,001,5\n00002,002,6'
[2 rows x 3 columns]
See the full release notes or issue tracker on GitHub for a complete list.
This is a major release from 0.8.1 and includes several new features and enhancements along with a large number of
bug fixes. New features include vectorized unicode encoding/decoding for Series.str, to_latex method to DataFrame,
more flexible parsing of boolean values, and enabling the download of options data from Yahoo! Finance.
Add encode and decode for unicode handling to vectorized string processing methods in Series.str (GH1706)
Add DataFrame.to_latex method (GH1735)
Add convenient expanding window equivalents of all rolling_* ops (GH1785)
Add Options class to pandas.io.data for fetching options data from Yahoo! Finance (GH1748, GH1739)
More flexible parsing of boolean values (Yes, No, TRUE, FALSE, etc) (GH1691, GH1295)
Add level parameter to Series.reset_index
TimeSeries.between_time can now select times across midnight (GH1871)
Series constructor can now handle generator as input (GH1679)
DataFrame.dropna can now take multiple axes (tuple/list) as input (GH924)
Enable skip_footer parameter in ExcelFile.parse (GH1843)
The default column names when header=None and no columns names passed to functions like read_csv
has changed to be more Pythonic and amenable to attribute access:
In [1]: data = '0,0,1\n1,1,0\n0,1,0'
In [3]: df
Out[3]:
0 1 2
0 0 0 1
1 1 1 0
2 0 1 0
[3 rows x 3 columns]
Creating a Series from another Series, passing an index, will cause reindexing to happen inside rather than treat-
ing the Series like an ndarray. Technically improper usages like Series(df[col1], index=df[col2])
that worked before by accident (this was never intended) will lead to all NA Series in some cases. To be per-
fectly clear:
In [4]: s1 = Series([1, 2, 3])
In [5]: s1
Out[5]:
0 1
1 2
2 3
dtype: int64
In [7]: s2
Out[7]:
foo NaN
bar NaN
baz NaN
dtype: float64
This release includes a few new features, performance enhancements, and over 30 bug fixes from 0.8.0. New features
include notably NA friendly string processing functionality and a series of new plot types and options.
This is a major release from 0.7.3 and includes extensive work on the time series handling and processing infrastructure
as well as a great deal of new functionality throughout the library. It includes over 700 commits from more than 20
distinct authors. Most pandas 0.7.3 and earlier users should not experience any issues upgrading, but due to the
migration to the NumPy datetime64 dtype, there may be a number of bugs and incompatibilities lurking. Lingering
incompatibilities will be fixed ASAP in a 0.8.1 release if necessary. See the full release notes or issue tracker on
GitHub for a complete list.
All objects can now work with non-unique indexes. Data alignment / join operations work according to SQL join
semantics (including, if application, index duplication in many-to-many joins)
Time series data are now represented using NumPys datetime64 dtype; thus, pandas 0.8.0 now requires at least NumPy
1.6. It has been tested and verified to work with the development version (1.7+) of NumPy as well which includes some
significant user-facing API changes. NumPy 1.6 also has a number of bugs having to do with nanosecond resolution
data, so I recommend that you steer clear of NumPy 1.6s datetime64 API functions (though limited as they are) and
only interact with this data using the interface that pandas provides.
See the end of the 0.8.0 section for a porting guide listing potential issues for users migrating legacy codebases from
pandas 0.7 or earlier to 0.8.0.
Bug fixes to the 0.7.x series for legacy NumPy < 1.6 users will be provided as they arise. There will be no more further
development in 0.7.x beyond bug fixes.
Note: With this release, legacy scikits.timeseries users should be able to port their code to use pandas.
New datetime64 representation speeds up join operations and data alignment, reduces memory usage, and
improve serialization / deserialization performance significantly over datetime.datetime
High performance and flexible resample method for converting from high-to-low and low-to-high frequency.
Supports interpolation, user-defined aggregation functions, and control over how the intervals and result labeling
are defined. A suite of high performance Cython/C-based resampling functions (including Open-High-Low-
Close) have also been implemented.
Revamp of frequency aliases and support for frequency shortcuts like 15min, or 1h30min
New DatetimeIndex class supports both fixed frequency and irregular time series. Replaces now deprecated
DateRange class
New PeriodIndex and Period classes for representing time spans and performing calendar logic, in-
cluding the 12 fiscal quarterly frequencies <timeseries.quarterly>. This is a partial port of, and a substantial
enhancement to, elements of the scikits.timeseries codebase. Support for conversion between PeriodIndex and
DatetimeIndex
New Timestamp data type subclasses datetime.datetime, providing the same interface while enabling working
with nanosecond-resolution data. Also provides easy time zone conversions.
Enhanced support for time zones. Add tz_convert and tz_lcoalize methods to TimeSeries and DataFrame.
All timestamps are stored as UTC; Timestamps from DatetimeIndex objects with time zone set will be localized
to localtime. Time zone conversions are therefore essentially free. User needs to know very little about pytz
library now; only time zone names as as strings are required. Time zone-aware timestamps are equal if and only
if their UTC timestamps match. Operations between time zone-aware time series with different time zones will
result in a UTC-indexed time series.
Time series string indexing conveniences / shortcuts: slice years, year and month, and index values with strings
Enhanced time series plotting; adaptation of scikits.timeseries matplotlib-based plotting code
New date_range, bdate_range, and period_range factory functions
Robust frequency inference function infer_freq and inferred_freq property of DatetimeIndex, with option
to infer frequency on construction of DatetimeIndex
to_datetime function efficiently parses array of strings to DatetimeIndex. DatetimeIndex will parse array or
list of strings to datetime64
Optimized support for datetime64-dtype data in Series and DataFrame columns
New NaT (Not-a-Time) type to represent NA in timestamp arrays
Optimize Series.asof for looking up as of values for arrays of timestamps
Milli, Micro, Nano date offset objects
Can index time series with datetime.time objects to select all data at particular time of day
(TimeSeries.at_time) or between two times (TimeSeries.between_time)
Add tshift method for leading/lagging using the frequency (if any) of the index, as opposed to a naive lead/lag
using shift
New cut and qcut functions (like Rs cut function) for computing a categorical variable from a continuous
variable by binning values either into value-based (cut) or quantile-based (qcut) bins
Rename Factor to Categorical and add a number of usability features
Add limit argument to fillna/reindex
More flexible multiple function application in GroupBy, and can pass list (name, function) tuples to get result in
particular order with given names
Add flexible replace method for efficiently substituting values
Enhanced read_csv/read_table for reading time series data and converting multiple columns to dates
Add comments option to parser functions: read_csv, etc.
Add :refdayfirst <io.dayfirst> option to parser functions for parsing international DD/MM/YYYY dates
Allow the user to specify the CSV reader dialect to control quoting etc.
Handling thousands separators in read_csv to improve integer parsing.
Enable unstacking of multiple levels in one shot. Alleviate pivot_table bugs (empty columns being intro-
duced)
Move to klib-based hash tables for indexing; better performance and less memory usage than Pythons dict
Add first, last, min, max, and prod optimized GroupBy functions
New ordered_merge function
Add flexible comparison instance methods eq, ne, lt, gt, etc. to DataFrame, Series
Improve scatter_matrix plotting function and add histogram or kernel density estimates to diagonal
Add kde plot option for density plots
Support for converting DataFrame to R data.frame through rpy2
Improved support for complex numbers in Series and DataFrame
Add pct_change method to all data structures
Add max_colwidth configuration option for DataFrame console output
Interpolate Series values using index values
Can select multiple columns from GroupBy
In [2]: fx['FR'].plot(style='g')
Out[2]: <matplotlib.axes._subplots.AxesSubplot at 0xa9d450cc>
../_static/whatsnew_secondary_y.png
Vytautas Jancauskas, the 2012 GSOC participant, has added many new plot types. For example, kde is a new
option:
In [4]: s = Series(np.concatenate((np.random.randn(1000),
...: np.random.randn(1000) * 0.5 + 3)))
...:
In [5]: plt.figure()
Out[5]: <matplotlib.figure.Figure at 0xac3c2e8c>
In [7]: s.plot(kind='kde')
Out[7]: <matplotlib.axes._subplots.AxesSubplot at 0xa9f4066c>
../_static/whatsnew_kde.png
Deprecation of offset, time_rule, and timeRule arguments names in time series functions. Warnings
will be printed until pandas 0.9 or 1.0.
The major change that may affect you in pandas 0.8.0 is that time series indexes use NumPys datetime64 data
type instead of dtype=object arrays of Pythons built-in datetime.datetime objects. DateRange has been
replaced by DatetimeIndex but otherwise behaved identically. But, if you have code that converts DateRange
or Index objects that used to contain datetime.datetime values to plain NumPy arrays, you may have bugs
lurking with code using scalar values because you are handing control over to NumPy:
In [8]: import datetime
In [10]: rng[5]
Out[10]: Timestamp('2000-01-06 00:00:00', offset='D')
In [14]: type(scalar_val)
Out[14]: numpy.datetime64
pandass Timestamp object is a subclass of datetime.datetime that has nanosecond support (the
nanosecond field store the nanosecond value between 0 and 999). It should substitute directly into any code that
used datetime.datetime values before. Thus, I recommend not casting DatetimeIndex to regular NumPy
arrays.
If you have code that requires an array of datetime.datetime objects, you have a couple of options. First, the
asobject property of DatetimeIndex produces an array of Timestamp objects:
In [15]: stamp_array = rng.asobject
In [16]: stamp_array
Out[16]:
Index([2000-01-01 00:00:00, 2000-01-02 00:00:00, 2000-01-03 00:00:00,
2000-01-04 00:00:00, 2000-01-05 00:00:00, 2000-01-06 00:00:00,
2000-01-07 00:00:00, 2000-01-08 00:00:00, 2000-01-09 00:00:00,
2000-01-10 00:00:00],
dtype='object')
In [17]: stamp_array[5]
Out[17]: Timestamp('2000-01-06 00:00:00', offset='D')
In [19]: dt_array
Out[19]:
array([datetime.datetime(2000, 1, 1, 0, 0),
datetime.datetime(2000, 1, 2, 0, 0),
datetime.datetime(2000, 1, 3, 0, 0),
datetime.datetime(2000, 1, 4, 0, 0),
datetime.datetime(2000, 1, 5, 0, 0),
datetime.datetime(2000, 1, 6, 0, 0),
datetime.datetime(2000, 1, 7, 0, 0),
datetime.datetime(2000, 1, 8, 0, 0),
datetime.datetime(2000, 1, 9, 0, 0),
datetime.datetime(2000, 1, 10, 0, 0)], dtype=object)
In [20]: dt_array[5]
Out[20]: datetime.datetime(2000, 1, 6, 0, 0)
matplotlib knows how to handle datetime.datetime but not Timestamp objects. While I recommend that you
plot time series using TimeSeries.plot, you can either use to_pydatetime or register a converter for the
Timestamp type. See matplotlib documentation for more on this.
Warning: There are bugs in the user-facing API with the nanosecond datetime64 unit in NumPy 1.6. In particular,
the string version of the array shows garbage values, and conversion to dtype=object is similarly broken.
In [22]: rng
Out[22]:
DatetimeIndex(['2000-01-01', '2000-01-02', '2000-01-03', '2000-01-04',
'2000-01-05', '2000-01-06', '2000-01-07', '2000-01-08',
'2000-01-09', '2000-01-10'],
dtype='datetime64[ns]', freq='D', tz=None)
In [23]: np.asarray(rng)
Out[23]:
array(['2000-01-01T01:00:00.000000000+0100',
'2000-01-02T01:00:00.000000000+0100',
'2000-01-03T01:00:00.000000000+0100',
'2000-01-04T01:00:00.000000000+0100',
'2000-01-05T01:00:00.000000000+0100',
'2000-01-06T01:00:00.000000000+0100',
'2000-01-07T01:00:00.000000000+0100',
'2000-01-08T01:00:00.000000000+0100',
'2000-01-09T01:00:00.000000000+0100',
'2000-01-10T01:00:00.000000000+0100'], dtype='datetime64[ns]')
In [25]: converted[5]
Out[25]: 947116800000000000L
Trust me: dont panic. If you are using NumPy 1.6 and restrict your interaction with datetime64 values to
pandass API you will be just fine. There is nothing wrong with the data-type (a 64-bit integer internally); all of the
important data processing happens in pandas and is heavily tested. I strongly recommend that you do not work
directly with datetime64 arrays in NumPy 1.6 and only use the pandas API.
Support for non-unique indexes: In the latter case, you may have code inside a try:... catch: block that
failed due to the index not being unique. In many cases it will no longer fail (some method like append still check for
uniqueness unless disabled). However, all is not lost: you can inspect index.is_unique and raise an exception
explicitly if it is False or go to a different code branch.
This is a minor release from 0.7.2 and fixes many minor bugs and adds a number of nice new features. There are
also a couple of API changes to note; these should not affect very many users, and we are inclined to call them bug
fixes even though they do constitute a change in behavior. See the full release notes or issue tracker on GitHub for a
complete list.
Add stacked argument to Series and DataFrames plot method for stacked bar plots.
df.plot(kind='bar', stacked=True)
df.plot(kind='barh', stacked=True)
Reverted some changes to how NA values (represented typically as NaN or None) are handled in non-numeric Series:
In [1]: series = Series(['Steve', np.nan, 'Joe'])
1 False
2 False
dtype: bool
In comparisons, NA / NaN will always come through as False except with != which is True. Be very careful with
boolean arithmetic, especially negation, in the presence of NA data. You may wish to add an explicit NA filter into
boolean array operations if you are worried about this:
In [4]: mask = series == 'Steve'
While propagating NA in comparisons may seem like the right behavior to some users (and you could argue on purely
technical grounds that this is the right thing to do), the evaluation was made that propagating NA everywhere, including
in numerical arrays, would cause a large amount of problems for users. Thus, a practicality beats purity approach
was taken. This issue may be revisited at some point in the future.
When calling apply on a grouped Series, the return value will also be a Series, to be more consistent with the
groupby behavior with DataFrame:
In [1]: df = DataFrame({'A' : ['foo', 'bar', 'foo', 'bar',
...: 'foo', 'bar', 'foo', 'foo'],
...: 'B' : ['one', 'one', 'two', 'three',
...: 'two', 'two', 'one', 'three'],
...: 'C' : np.random.randn(8), 'D' : np.random.randn(8)})
...:
In [2]: df
Out[2]:
A B C D
0 foo one 0.144909 1.387310
1 bar one -1.033812 0.063490
2 foo two 0.197333 1.437656
3 bar three -0.059730 -0.814844
4 foo two 0.087205 -0.482060
5 bar two -1.607906 1.521442
6 foo one -1.275249 0.882182
7 foo three -0.054460 -0.108020
[8 rows x 4 columns]
In [4]: grouped.describe()
Out[4]:
A
bar count 3.000000
mean -0.900483
std 0.782652
min -1.607906
25% -1.320859
50% -1.033812
75% -0.546771
...
foo mean -0.180052
std 0.619410
min -1.275249
25% -0.054460
50% 0.087205
75% 0.144909
max 0.197333
dtype: float64
This release targets bugs in 0.7.1, and adds a few minor features.
This release includes a few new features and addresses over a dozen bugs in 0.7.0.
Add to_clipboard function to pandas namespace for writing objects to the system clipboard (GH774)
Add itertuples method to DataFrame for iterating through the rows of a dataframe as tuples (GH818)
Add ability to pass fill_value and method to DataFrame and Series align method (GH806, GH807)
Add fill_value option to reindex, align methods (GH784)
Enable concat to produce DataFrame from Series (GH787)
Add between method to Series (GH802)
Add HTML representation hook to DataFrame for the IPython HTML notebook (GH773)
Support for reading Excel 2007 XML documents using openpyxl
New unified merge function for efficiently performing full gamut of database / relational-algebra operations.
Refactored existing join methods to use the new infrastructure, resulting in substantial performance gains
(GH220, GH249, GH267)
New unified concatenation function for concatenating Series, DataFrame or Panel objects along an axis.
Can form union or intersection of the other axes. Improves performance of Series.append and
DataFrame.append (GH468, GH479, GH273)
Can pass multiple DataFrames to DataFrame.append to concatenate (stack) and multiple Series to
Series.append too
Can pass list of dicts (e.g., a list of JSON objects) to DataFrame constructor (GH526)
You can now set multiple columns in a DataFrame via __getitem__, useful for transformation (GH342)
Handle differently-indexed output values in DataFrame.apply (GH498)
In [1]: df = DataFrame(randn(10, 4))
[8 rows x 4 columns]
One of the potentially riskiest API changes in 0.7.0, but also one of the most important, was a complete review of how
integer indexes are handled with regard to label-based indexing. Here is an example:
In [3]: s = Series(randn(10), index=range(0, 20, 2))
In [4]: s
Out[4]:
0 -0.392051
2 -0.189537
4 0.886170
6 -1.125894
8 0.319635
10 0.998222
12 0.091743
14 -2.032047
16 -0.448560
18 0.730510
dtype: float64
In [5]: s[0]
Out[5]: -0.39205110783730307
In [6]: s[2]
Out[6]: -0.18953739573269113
In [7]: s[4]
Out[7]: 0.88617008348573789
This is all exactly identical to the behavior before. However, if you ask for a key not contained in the Series, in
versions 0.6.1 and prior, Series would fall back on a location-based lookup. This now raises a KeyError:
In [2]: s[1]
KeyError: 1
In [4]: df
0 1 2 3
0 0.88427 0.3363 -0.1787 0.03162
2 0.14451 -0.1415 0.2504 0.58374
4 -1.44779 -0.9186 -1.4996 0.27163
6 -0.26598 -2.4184 -0.2658 0.11503
8 -0.58776 0.3144 -0.8566 0.61941
10 0.10940 -0.7175 -1.0108 0.47990
12 -1.16919 -0.3087 -0.6049 -0.43544
14 -0.07337 0.3410 0.0424 -0.16037
In [5]: df.ix[3]
KeyError: 3
In order to support purely integer-based indexing, the following methods have been added:
Method Description
Series.iget_value(i) Retrieve value stored at location i
Series.iget(i) Alias for iget_value
DataFrame.irow(i) Retrieve the i-th row
DataFrame.icol(j) Retrieve the j-th column
DataFrame.iget_value(i, j) Retrieve the value at row i and column j
Label-based slicing using ix now requires that the index be sorted (monotonic) unless both the start and endpoint are
contained in the index:
In [8]: s = Series(randn(6), index=list('gmkaec'))
In [9]: s
Out[9]:
g 1.269713
m 1.209524
k 2.160843
a 0.533532
e -2.371548
c 0.562726
dtype: float64
If the index had been sorted, the range selection would have been possible:
In [11]: s2 = s.sort_index()
In [12]: s2
Out[12]:
a 0.533532
c 0.562726
e -2.371548
g 1.269713
k 2.160843
m 1.209524
dtype: float64
In [13]: s2.ix['b':'h']
Out[13]:
c 0.562726
e -2.371548
g 1.269713
dtype: float64
As as notational convenience, you can pass a sequence of labels or a label slice to a Series when getting and setting
values via [] (i.e. the __getitem__ and __setitem__ methods). The behavior will be the same as passing
similar input to ix except in the case of integer indexing:
In [14]: s = Series(randn(6), index=list('acegkm'))
In [15]: s
Out[15]:
a 2.031757
c 0.851077
e 0.660056
g -1.662471
k 0.571380
m 0.945588
dtype: float64
In [17]: s['b':'l']
Out[17]:
c 0.851077
e 0.660056
g -1.662471
k 0.571380
dtype: float64
In [18]: s['c':'k']
Out[18]:
c 0.851077
e 0.660056
g -1.662471
k 0.571380
dtype: float64
In the case of integer indexes, the behavior will be exactly as before (shadowing ndarray):
In [19]: s = Series(randn(6), index=range(0, 12, 2))
In [21]: s[1:5]
Out[21]:
2 2.108285
4 -1.263534
6 2.617801
8 1.967592
dtype: float64
If you wish to do indexing with sequences and slicing on an integer index with label semantics, use ix.
Cythonized GroupBy aggregations no longer presort the data, thus achieving a significant speedup (GH93).
GroupBy aggregations with Python functions significantly sped up by clever manipulation of the ndarray data
type in Cython (GH496).
Better error message in DataFrame constructor when passed column labels dont match data (GH497)
Substantially improve performance of multi-GroupBy aggregation when a Python function is passed, reuse
ndarray object in Cython (GH496)
Can store objects indexed by tuples and floats in HDFStore (GH492)
Dont print length by default in Series.to_string, add length option (GH489)
Improve Cython code for multi-groupby to aggregate without having to sort the data (GH93)
Improve MultiIndex reindexing speed by storing tuples in the MultiIndex, test for backwards unpickling com-
patibility
Improve column reindexing performance by using specialized Cython take function
Further performance tweaking of Series.__getitem__ for standard use cases
Avoid Index dict creation in some cases (i.e. when getting slices, etc.), regression from prior versions
Friendlier error message in setup.py if NumPy not installed
Use common set of NA-handling operations (sum, mean, etc.) in Panel class also (GH536)
Default name assignment when calling reset_index on DataFrame with a regular (non-hierarchical) index
(GH476)
Use Cythonized groupers when possible in Series/DataFrame stat ops with level parameter passed (GH545)
Ported skiplist data structure to C to speed up rolling_median by about 5-10x in most typical use cases
(GH374)
Add Spearman and Kendall rank correlation options to Series.corr and DataFrame.corr (GH428)
Added get_value and set_value methods to Series, DataFrame, and Panel for very low-overhead access
(>2x faster in many cases) to scalar elements (GH437, GH438). set_value is capable of producing an
enlarged object.
Add PyQt table widget to sandbox (GH435)
DataFrame.align can accept Series arguments and an axis option (GH461)
Implement new SparseArray and SparseList data structures. SparseSeries now derives from SparseArray
(GH463)
Better console printing options (GH453)
Implement fast data ranking for Series and DataFrame, fast versions of scipy.stats.rankdata (GH428)
Implement DataFrame.from_items alternate constructor (GH444)
DataFrame.convert_objects method for inferring better dtypes for object columns (GH302)
Add rolling_corr_pairwise function for computing Panel of correlation matrices (GH189)
Add margins option to pivot_table for computing subgroup aggregates (GH114)
Add Series.from_csv function (GH482)
Can pass DataFrame/DataFrame and DataFrame/Series to rolling_corr/rolling_cov (GH #462)
MultiIndex.get_level_values can accept the level name
Improve memory usage of DataFrame.describe (do not copy data unnecessarily) (PR #425)
Optimize scalar value lookups in the general case by 25% or more in Series and DataFrame
Fix performance regression in cross-sectional count in DataFrame, affecting DataFrame.dropna speed
Column deletion in DataFrame copies no data (computes views on blocks) (GH #158)
VBENCH? Significant GroupBy performance enhancement with multiple keys with many empty combina-
tions
VBENCH New Cython vectorized function map_infer speeds up Series.apply and Series.map sig-
nificantly when passed elementwise Python function, motivated by (GH355)
VBENCH Significantly improved performance of Series.order, which also makes np.unique called on a
Series faster (GH327)
VBENCH Vastly improved performance of GroupBy on axes with a MultiIndex (GH299)
VBENCH Major performance improvements in file parsing functions read_csv and read_table
VBENCH Added Cython function for converting tuples to ndarray very fast. Speeds up many MultiIndex-related
operations
VBENCH Refactored merging / joining code into a tidy class and disabled unnecessary computations in the
float/object case, thus getting about 10% better performance (GH211)
VBENCH Improved speed of DataFrame.xs on mixed-type DataFrame objects by about 5x, regression from
0.3.0 (GH215)
VBENCH With new DataFrame.align method, speeding up binary operations between differently-indexed
DataFrame objects by 10-25%.
VBENCH Significantly sped up conversion of nested dict into DataFrame (GH212)
VBENCH Significantly speed up DataFrame __repr__ and count on large mixed-type DataFrame objects
Altered binary operations on differently-indexed SparseSeries objects to use the integer-based (dense) alignment
logic which is faster with a larger number of blocks (GH205)
Wrote faster Cython data alignment / merging routines resulting in substantial speed increases
Improved performance of isnull and notnull, a regression from v0.3.0 (GH187)
Refactored code related to DataFrame.join so that intermediate aligned copies of the data in each
DataFrame argument do not need to be created. Substantial performance increases result (GH176)
Substantially improved performance of generic Index.intersection and Index.union
Implemented BlockManager.take resulting in significantly faster take performance on mixed-type
DataFrame objects (GH104)
Improved performance of Series.sort_index
Significant groupby performance enhancement: removed unnecessary integrity checks in DataFrame internals
that were slowing down slicing operations to retrieve groups
Optimized _ensure_index function resulting in performance savings in type-checking Index objects
Wrote fast time series merging / joining methods in Cython. Will be integrated later into DataFrame.join and
related functions
TWO
INSTALLATION
The easiest way for the majority of users to install pandas is to install it as part of the Anaconda distribution, a cross
platform distribution for data analysis and scientific computing. This is the recommended installation method for most
users.
Instructions for installing from source, PyPI, various Linux distributions, or a development version are also provided.
The easiest way to start experimenting with pandas doesnt involve installing pandas at all.
Wakari is a free service that provides a hosted IPython Notebook service in the cloud.
Simply create an account, and have access to pandas from within your brower via an IPython Notebook in a few
minutes.
Installing pandas and the rest of the NumPy and SciPy stack can be a little difficult for inexperienced users.
The simplest way to install not only pandas, but Python and the most popular packages that make up the SciPy
stack (IPython, NumPy, Matplotlib, ...) is with Anaconda, a cross-platform (Linux, Mac OS X, Windows) Python
distribution for data analytics and scientific computing.
After running a simple installer, the user will have access to pandas and the rest of the SciPy stack without needing to
install anything else, and without needing to wait for any software to be compiled.
Installation instructions for Anaconda can be found here.
A full list of the packages available as part of the Anaconda distribution can be found here.
An additional advantage of installing with Anaconda is that you dont require admin rights to install it, it will install
in the users home directory, and this also makes it trivial to delete Anaconda at a later date (just delete that folder).
199
pandas: powerful Python data analysis toolkit, Release 0.16.2
The previous section outlined how to get pandas installed as part of the Anaconda distribution. However this approach
means you will install well over one hundred packages and involves downloading the installer which is a few hundred
megabytes in size.
If you want to have more control on which packages, or have a limited internet bandwidth, then installing pandas with
Miniconda may be a better solution.
Conda is the package manager that the Anaconda distribution is built upon. It is a package manager that is both
cross-platform and language agnostic (it can play a similar role to a pip and virtualenv combination).
Miniconda allows you to create a minimal self contained Python installation, and then use the Conda command to
install additional packages.
First you will need Conda to be installed and downloading and running the Miniconda will do this for you. The
installer can be found here
The next step is to create a new conda environment (these are analogous to a virtualenv but they also allow you to
specify precisely which Python version to install also). Run the following commands from a terminal window:
conda create -n name_of_my_env python
This will create a minimal environment with only Python installed in it. To put your self inside this environment run:
source activate name_of_my_env
The final step required is to install pandas. This can be done with the following command:
conda install pandas
If you require any packages that are available to pip but not conda, simply install pip, and use pip to install these
packages:
conda install pip
pip install django
This will likely require the installation of a number of dependencies, including NumPy, will require a compiler to
compile required bits of code, and can take a few minutes to complete.
See the contributing documentation for complete instructions on building from the git source tree. Further, see creating
a devevlopment environment if you wish to create a pandas development environment.
pandas is equipped with an exhaustive set of unit tests covering about 97% of the codebase as of this writing. To run it
on your machine to verify that everything is working (and you have all of the dependencies, soft and hard, installed),
make sure you have nose and run:
$ nosetests pandas
..........................................................................
.......................S..................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
.................S........................................................
....
----------------------------------------------------------------------
Ran 818 tests in 21.631s
OK (SKIP=2)
2.3 Dependencies
numexpr: for accelerating certain numerical operations. numexpr uses multiple cores as well as smart chunk-
ing and caching to achieve large speedups. If installed, must be Version 2.1 or higher.
bottleneck: for accelerating certain types of nan evaluations. bottleneck uses specialized cython routines
to achieve large speedups.
Note: You are highly encouraged to install these libraries, as they provide large speedups, especially if working with
large data sets.
httplib2
Needed for gbq
One of the following combinations of libraries is needed to use the top-level read_html() function:
BeautifulSoup4 and html5lib (Any recent version of html5lib is okay.)
BeautifulSoup4 and lxml
BeautifulSoup4 and html5lib and lxml
Only lxml, although see HTML reading gotchas for reasons as to why you should probably not take this
approach.
Warning:
if you install BeautifulSoup4 you must install either lxml or html5lib or both. read_html() will
not work with only BeautifulSoup4 installed.
You are highly encouraged to read HTML reading gotchas. It explains issues surrounding the installa-
tion and usage of the above three libraries
You may need to install an older version of BeautifulSoup4:
* Versions 4.2.1, 4.1.3 and 4.0.2 have been confirmed for 64 and 32-bit Ubuntu/Debian
Additionally, if youre using Anaconda you should definitely read the gotchas about HTML parsing
libraries
Note:
if youre on a system with apt-get you can do
sudo apt-get build-dep python-lxml
to get the necessary dependencies for installation of lxml. This will prevent further headaches down the
line.
Note: Without the optional dependencies, many useful features will not work. Hence, it is highly recommended that
you install these. A packaged distribution like Enthought Canopy may be worth considering.
THREE
CONTRIBUTING TO PANDAS
Table of contents:
Where to start?
Bug Reports/Enhancement Requests
Working with the code
Version Control, Git, and GitHub
Getting Started with Git
Forking
Creating a Branch
Creating a Development Environment
Making changes
Contributing to the documentation
About the pandas documentation
How to build the pandas documentation
* Requirements
* Building the documentation
* Built Master Branch Documentation
Contributing to the code base
Code Standards
Test-driven Development/Writing Code
* Writing tests
* Running the test suite
* Running the performance test suite
Documenting your code
Contributing your changes to pandas
Committing your code
Pushing your changes
Review your code
Finally, make the Pull Request
Delete your merged branch (optional)
All contributions, bug reports, bug fixes, documentation improvements, enhancements and ideas are welcome.
If you are simply looking to start working with the pandas codebase, navigate to the GitHub issues tab and start
looking through interesting issues. There are a number of issues listed under Docs and Difficulty Novice where you
could start out.
205
pandas: powerful Python data analysis toolkit, Release 0.16.2
Or maybe through using pandas you have an idea of you own or are looking for something in the documentation and
thinking this can be improved...you can do something about it!
Feel free to ask questions on mailing list
Bug reports are an important part of making pandas more stable. Having a complete bug report will allow others to
reproduce the bug and provide insight into fixing. Since many versions of pandas are supported, knowing version
information will also identify improvements made since previous versions. Often trying the bug-producing code out
on the master branch is a worthwhile exercise to confirm the bug still exists. It is also worth searching existing bug
reports and pull requests to see if the issue has already been reported and/or fixed.
Bug reports must:
1. Include a short, self-contained Python snippet reproducing the problem. You can have the code formatted nicely
by using GitHub Flavored Markdown:
```python
>>> from pandas import DataFrame
>>> df = DataFrame(...)
...
```
2. Include the full version string of pandas and its dependencies. In recent (>0.12) versions of pandas you can use
a built in function:
>>> from pandas.util.print_versions import show_versions
>>> show_versions()