Skip to content

Don't import pyarrow just to check version #503

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

Merged
merged 4 commits into from
Dec 18, 2020

Conversation

martindurant
Copy link
Member

We would rather not import pyarrow, since from v2.0.0, we don't use it anyway.

Ref #411

cc @jorisvandenbossche - this is the chain of version checks that we talked about in your PR.

[ ] %time import fsspec
93 ms (this branch)
183 ms (master)

@jorisvandenbossche
Copy link
Contributor

Looks good!

@martindurant martindurant merged commit a5bb951 into fsspec:master Dec 18, 2020
@martindurant martindurant deleted the dont_import_pyarrow branch December 18, 2020 15:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants