Towards "pandas 1.0"

[jorisvandenbossche]

Here's our roadmap document: https://docs.google.com/document/d/151ct8jcZWwh7XStptjbLsda6h2b3C0IuiH_hfZnUA58/edit#

Just because it is a nice round number :-)

Or maybe we can use it to discuss how we imagine a possible pandas 1.0 ..

---

Some clarification (from @shoyer): This is not the place to make new feature requests -- please continue to make separate GitHub issues for those. Almost every new feature can be added without a 1.0 release. If there is a change you think would be necessary to do in pandas 1.0, feel free to reference issues where it is described in more detail.

[shoyer]

My wish list for pandas 1.0:

1. Fix []/__getitem__ (Overview of [] (__getitem__) API #9595)
2. Make the index/column distinction less painful (ENH/API: clarify groupby by to handle columns/index names #5677, Allowing the index to be referenced by name, like a column #8162)

I also have a fantasy world where the pandas Index becomes entirely optional, but that might be too big of a break even for pandas 1.0.

[jorisvandenbossche]

I want to add:

3. Clean up the Index vs MultiIndex API (Unify index and multindex (and possibly others) API #3268)

[jnmclarty]

What if, every pnl, df, s, had a mode, that changed the slicing/getitem behavior. One could set the default in the options, and change it on a per-object basis when necessary? It could allow old-new to transition smoother, plus, get more creative where desired.

[shoyer]

@jnmclarty A better option would be some sort of flag that could be set per module, similar to a future statement -- changing the way in which a specific DataFrame is queried is just begging for someone to pass it off to an incompatible function. In fact, I just asked if this is possible on StackOverflow: http://stackoverflow.com/questions/29905278/using-future-style-imports-for-module-specific-features-in-python/

[djchou]

It would be nice if there was an option to have boxplot X axis labels match line plot's X axis labels.

[shoyer]

@djchou is there an existing issue for that? If not, please make one :).

[sinhrks]

Congrats on the great package:D

My wish is:

• cythonize internals (Move Block internals code to Cython #163)
• Parallelize option for some ops, such as groupby / aggregation

[datnamer]

dplyr like macros: https://github.com/dalejung/naginpy

A guy can wish...

[TomAugspurger]

I've been working on problems recently where having groupbys run in parallel would have been great (I think). Also maps / applys.

[lexual]

ref #1907

[toddrjen]

These may be too small, but since this is a wishlist I would like to see some improvements in the consistency of the API. Some example:

• More consistent usage of singular vs. plural, for example index/indexes, column/columns, and level/levels. This includes both the names and whether they accept single values, multiple values, or both.
• Make sure the axis argument is available wherever operations are applied across along an axis.
• Go through related functions and make sure they have the same arguments in the same order. For example, for DataFrame, cumsum has a skip_na argument, while diff doesn't.
• If an argument does the same thing as a method, it should have the same name as the method. So for example fill_value should be fillna.
• Try to get the use of underscores more consistent. For example, in DataFrame we have sort_index and sortlevel, and is_copy, isin, and isnull.

[shoyer]

For the record, I'm strongly -1 on @toddrjen's suggestion to rename methods to make the use of underscores more consistent. Even Python 3 didn't clean things up like that.