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

Problem installing cfgrib via conda - module 'pyeccodes.compat' has no attribute #147

Closed
shimonw2 opened this issue Jun 12, 2020 · 3 comments · Fixed by #221
Closed

Problem installing cfgrib via conda - module 'pyeccodes.compat' has no attribute #147

shimonw2 opened this issue Jun 12, 2020 · 3 comments · Fixed by #221
Labels
won't fix This will not be worked on

Comments

@shimonw2
Copy link

image

@alexamici
Copy link
Contributor

pyeccodes is a highly experimental new package. Do not install it. Please uninstall it and try again.

@alexamici alexamici assigned alexamici and unassigned alexamici Sep 15, 2020
@alexamici alexamici added the won't fix This will not be worked on label Sep 15, 2020
@shimonw2
Copy link
Author

shimonw2 commented Sep 15, 2020 via email

@cdibble
Copy link

cdibble commented Nov 2, 2020

This is an ongoing issue for me. If I have the binary dependencies installed via sudo apt-get install libeccodes0 , then after pip install cfgrib, I can import cfgrib and work with it. This works for python3.6 on Ubuntu 18.x.

However, if I try to package that and deploy it in a serverless (AWS Lambda) environment, I cannot import cfgrib and instead get an error: No module named 'pyeccodes'. If I include that module as part of the deployment package, then I end up with the same module pyeccodes.compat has no attribute... error.

Does anyone have a better understanding of these dependencies? Is it not possible to package cfgrib for use in a serverless environment?

@alexamici perhaps you have an idea? Is there some way to eliminate or resolve the dependency on pyeccodes?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
won't fix This will not be worked on
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants