Earthaccess and boto3 issues #1172
-
|
Hello, I've been trying to create a virtual environment that contains both earthaccess and boto3 packages but I've run into a lot of issues with boto3 not being compatible with earthaccess. Has anyone had any luck with getting earthaccess and boto3 to work together? I am starting out with https://github.com/nasa/LPDAAC-Data-Resources/blob/main/setup/environment.yml. Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
I hit this exact snag last year when trying to pair earthaccess with boto3 for S3‑based downloads. The conflict usually shows up as a botocore version mismatch - earthaccess pins an older botocore range while the latest boto3 pulls a newer one. First, keep the conda‑forge channel; it’s where both packages live cleanly. Add boto3 directly to the environment.yml under dependencies, but pin botocore to a range that earthaccess is happy with. For earthaccess 0.5.0 the sweet spot is botocore >=1.29.0,<1.30.0, which translates to boto3 ≈ 1.26.0. So edit the file like: |
Beta Was this translation helpful? Give feedback.
I hit this exact snag last year when trying to pair earthaccess with boto3 for S3‑based downloads. The conflict usually shows up as a botocore version mismatch - earthaccess pins an older botocore range while the latest boto3 pulls a newer one.
First, keep the conda‑forge channel; it’s where both packages live cleanly. Add boto3 directly to the environment.yml under dependencies, but pin botocore to a range that earthaccess is happy with. For earthaccess 0.5.0 the sweet spot is botocore >=1.29.0,<1.30.0, which translates to boto3 ≈ 1.26.0.
So edit the file like: