Skip to content

DOC: remove okwarning once pyarrow 0.12 is released #24617

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jorisvandenbossche opened this issue Jan 4, 2019 · 5 comments · Fixed by #29395
Closed

DOC: remove okwarning once pyarrow 0.12 is released #24617

jorisvandenbossche opened this issue Jan 4, 2019 · 5 comments · Fixed by #29395
Labels
Milestone

Comments

@jorisvandenbossche
Copy link
Member

TODO: Revert #24591 once pyarrow is released

@jreback jreback added this to the 0.24.1 milestone Jan 4, 2019
@jbrockmendel
Copy link
Member

Do we have a minimal pyarrow we support? environment.yml lists pyarrow>=0.7.0. There are some special cases in internals.blocks for pyarrow compat that would be nice to get rid of eventually.

@jreback
Copy link
Contributor

jreback commented Jan 4, 2019

not averse to bumping

@jbrockmendel
Copy link
Member

It looks like the commit that removed pyarrow's deprecated usage was 2018-01-25 apache/arrow@6bb1d1b. The first release after that looks like 0.9.0 on 2018-03-16

@jreback
Copy link
Contributor

jreback commented Jan 5, 2019

bump to 0.9.0 would be fine

@jorisvandenbossche
Copy link
Member Author

I am also fine with bumping to 0.9.0.
That is however unrelated to the original issue here, though. @jbrockmendel can you open a new issue for that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants