News for hackers. Stuff that matters.
Re:2017 Outlook: Pandas, Arrow, Feather, Parquet, Spark, Ibis by aorth on Thursday December 29, 2016 @12:39PM (#13278667)
My goal is to deliver the same quality pandas user experience on 10x as much data. pandas works well on 1GB of data, but less well on 10GB. This has to change for pandas to remain a relevant tool in the future.

Awesome! Great to see such honest commitment. Pandas is already a great library, and I can't wait to see the progress!

Re:2017 Outlook: Pandas, Arrow, Feather, Parquet, Spark, Ibis by pixelmonkey on Thursday December 29, 2016 @09:02AM (#13277280)
Thank you for all you do for the Python and data community, Wes! Arrow and "native" parquet support for Python are very exciting developments.
Re:2017 Outlook: Pandas, Arrow, Feather, Parquet, Spark, Ibis by lintiness on Thursday December 29, 2016 @09:47AM (#13277499)
i've migrated back to r for various reasons, but wes really is a beast in the python finance world.
Re:2017 Outlook: Pandas, Arrow, Feather, Parquet, Spark, Ibis by peatmoss on Thursday December 29, 2016 @10:55AM (#13277946)
I'd expect that improvements to Arrow, Feather, Parquet etc. will help lift lots of data communities including those of us who also do R. I'm really looking forward to reusable in-memory dataframe structures like Arrow to be the foundations for R/Pandas-like data munging in lots of languages that aren't R or Python
Re:2017 Outlook: Pandas, Arrow, Feather, Parquet, Spark, Ibis by ttub on Thursday December 29, 2016 @10:58AM (#13277972)
Very cool, but does anyone know more about the plan to offer a "lib pandas" mentioned here?https://mail.python.org/pipermail/pandas-dev/2015-December/0...
Re:2017 Outlook: Pandas, Arrow, Feather, Parquet, Spark, Ibis by shoyer on Thursday December 29, 2016 @01:01PM (#13278815)
"lib pandas" has become pandas 2.0. See https://github.com/pandas-dev/pandas2 for ongoing design discussions and development.
Re:2017 Outlook: Pandas, Arrow, Feather, Parquet, Spark, Ibis by peatmoss on Thursday December 29, 2016 @12:38PM (#13278663)
Hoping Wes will chime in here if I'm wrong, but I'm guessing that the technologies he discusses here will more or less take the place of a lib pandas.
Re:2017 Outlook: Pandas, Arrow, Feather, Parquet, Spark, Ibis by wesm on Sunday January 08, 2017 @11:44AM (#13350541)
No, it's all closely inter-related. pandas as a project is responsible for data manipulation and in-memory analytics. These other projects are all complementary technologies.
Re:2017 Outlook: Pandas, Arrow, Feather, Parquet, Spark, Ibis by mojoe on Thursday December 29, 2016 @02:14PM (#13279305)
Feather is awesome, and I really hope that Dask (http://dask.pydata.org/en/latest/) can eventually integrate it so that we have a lightweight way to write to/from disk in parallel.
Re:2017 Outlook: Pandas, Arrow, Feather, Parquet, Spark, Ibis by Nexxxeh on Thursday December 29, 2016 @11:00AM (#13277989)
I was expecting a post about Microsoft's email client.

An annoying side effect of using commonly used words as product names. Signal being the most egregious offender recently.

The capital O of Outlook didn't help.

I know nothing of Python, R and big data, but things are looking up by the sound of it?

Re:2017 Outlook: Pandas, Arrow, Feather, Parquet, Spark, Ibis by SolarNet on Thursday December 29, 2016 @01:31PM (#13279023)
At first I thought this was a list of animals going extinct or something.
Re:2017 Outlook: Pandas, Arrow, Feather, Parquet, Spark, Ibis by xapata on Thursday December 29, 2016 @02:01PM (#13279209)
I hope the API becomes more Pythonic and less NumPy-ic. A little more purity would be practical in this case.
Re:2017 Outlook: Pandas, Arrow, Feather, Parquet, Spark, Ibis by ipstone2014 on Thursday December 29, 2016 @05:22PM (#13280692)
Nice road-map and Kudos to Wes for the great work/tools for the data community!
Re:2017 Outlook: Pandas, Arrow, Feather, Parquet, Spark, Ibis by filereaper on Thursday December 29, 2016 @12:20PM (#13278533)
Found out about Apache Kudu, written in C++...

Are these systems moving away from the JVM now?