[Pandas-dev] Rewriting some of internals of pandas in C/C++? / Roadmap

[Wes McKinney]

At the moment, I don't have plans for PyArrow that extend beyond being the
point of contact with systems that use Arrow natively. For example, pandas
users will soon be able to read and write Parquet format files via pyarrow
(which will handle low-level conversion to/from pandas's NumPy memory
representation)

I'd like to continue the pandas refactoring / reorganization effort (+
organizing deprecations) to be able to encapsulate pandas's interactions
with NumPy so that alternate backends can be conceivable at all (possibly
in 2017-2018). I don't have a lot of bandwidth for this until 2nd half of
April at earliest, though. Happy to respond to inquiries at the meantime.

- Wes

On Wed, Mar 23, 2016 at 2:22 PM, Irwin Zaid <izaid at continuum.io> wrote:

> If it is of interest, I'll just mention that we recently split off DyND's
> type system to be its own independent library -- libdyndt (for the types)
> and libdynd (for the callables and array). Distributing them separately
> still needs work, but the binaries are there. DyND / Arrow compatibility
> would be interesting, and I'm always keen to avoid duplication of effort.
>
> _______________________________________________
> Pandas-dev mailing list
> Pandas-dev at python.org
> https://mail.python.org/mailman/listinfo/pandas-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pandas-dev/attachments/20160323/61c79704/attachment.html>