Skip to content
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

WIP: environment.yml encounters import error with pyarrow #26670

Closed
wants to merge 0 commits into from

Conversation

minggli
Copy link
Contributor

@minggli minggli commented Jun 5, 2019

#LondonPythonSprints

This issue seems to be ubiquitous, and below link suggest solution:
apache/arrow#2213

@codecov
Copy link

codecov bot commented Jun 5, 2019

Codecov Report

Merging #26670 into master will decrease coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #26670      +/-   ##
==========================================
- Coverage   91.88%   91.87%   -0.01%     
==========================================
  Files         174      174              
  Lines       50701    50701              
==========================================
- Hits        46588    46584       -4     
- Misses       4113     4117       +4
Flag Coverage Δ
#multiple 90.41% <ø> (ø) ⬆️
#single 41.9% <ø> (-0.12%) ⬇️
Impacted Files Coverage Δ
pandas/io/gbq.py 78.94% <0%> (-10.53%) ⬇️
pandas/core/frame.py 97% <0%> (-0.12%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 649ad5c...96b8d03. Read the comment docs.

@simonjayhawkins simonjayhawkins added CI Continuous Integration Dependencies Required and optional dependencies labels Jun 5, 2019
@datapythonista datapythonista changed the title environment.yml encounters import error with pyarrow WIP: environment.yml encounters import error with pyarrow Jun 6, 2019
@datapythonista
Copy link
Member

@minggli is this expected to close the issue, or is it just a PR to debug the error in the CI? I guess it's the latter, and I edited the title to start by WIP, so we don't review it until it's finished.

Copy link
Contributor

@jreback jreback left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this actually an issue? why are we specifying transitive dependencies?

@minggli
Copy link
Contributor Author

minggli commented Jun 12, 2019

@jreback Hi, it appears the import error associated with pyarrow has disappeared on its own presumably due to fix on upstream. closing PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous Integration Dependencies Required and optional dependencies
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CI/DOC: pyarrow ImportError when using environment.yml to build the docs
4 participants