Mailman 3 February 2017 - Pandas-dev

pandas February dev meeting notes
by Wes McKinney Feb. 27, 2017

Feb. 27, 2017

hi all, Here are the rough notes about what was discussed on our recent public dev meeting call. Please let us know if you have any questions or comments for further discussion. thanks! Wes Meeting notes * Increasing worker capacity * Add 5 additional Travis CI builds for now * Add Circle CI for pandas-dev/pandas + plan to migrate Linux to CircleCI * Obtaining dedicated bare metal hardware for pandas? * Could be shared amongst Dask, pandas, other projects * Wes volunteeer personal desktop for a nightly benchmark job, upload benchmark results to a cloud postgres * Independently — write a generic job suitable for cron * pandas 2.0 * Preparation: * Separate test changes that will break (eg implicit dtype changes), separation can also in place using marker * Development focus * Defining abstract data interface to make interacting with out-of-process data and in-memory (including split / deferred concatenated arrays) * Backwards compatibility layer to run NumPy functions (__array__ / __array_finalize__) * Define implementation pattern for primitive analytics functions (e.g. string manipulations, math, binary options) * Define memory management semantics (lifetime, sharing, copy-on-write) * Resourcing * Wes allocating some time in Q1 2017, will become more free in Q2 and beyond * Website page for donations, listing project for which those funds will be used. * pandas 1.0 and current roadmap * What does stable mean? * Extreme conservatism around any changes that may impact correctness / data semantics * Careful about changes that may make rebasing in pandas2 branch more difficult * Deprecating panel * Consensus to deprecate Panel in 0.20.0 * Removing .ix * Should we remove in 1.0? * Consensus seems to me to leave DeprecationWarning/FutureWarning in 1.0, to be removed later in 2.0 * Handling of arguments in .agg: https://github.com/pandas-dev/pandas/pull/14668 - Please have a look! * Notebook 5.0 new tables * Joris will raise another issue with Jupyter to let them know how this will affect pandas users * We can maybe issue a 0.19.3 with only the changes in https://github.com/pandas-dev/pandas/issues/15379 * Next meeting * April 15 2017 time frame

1 0

Pandas dev hangout - wednesday 15 feb 14:00 UTC
by Joris Van den Bossche Feb. 13, 2017

Feb. 13, 2017

Hi all, This wednesday, 15 Feb, at 14:00 UTC, we are having an online developer meeting with the core team. But other people are certainly welcome as well! If you would like to join, let us know, so we are sure to invite you. Regards, joris

2 1

pandas 1.0 - API stability
by Joris Van den Bossche Feb. 8, 2017

Feb. 8, 2017

Hi all, To get to a pandas 1.0, there are still some things to discuss (timeline for 0.20 and 1.0, what do we still want to include/change in 1.0 that we think are blockers, what after that ..). To start some discussion, I want to focus in this mail on a specific aspect. Imagine 1.0 is released in a few months, how do we see its development of further 1.x releases? In earlier email threads we have spoken about a (more) "stable 1.x release". But what do we exactly mean with that? I had a chat with Jeff a while ago, and I remember we at least had some different interpretations, which is not necessarily a problem, but I think it is important that we clearly define how we, collectively, interpret this within the context of pandas. So what do we see as a 1.x API stable release series? And do we want this? Regards, Joris

1 1