Skip to content
Discussion options

You must be logged in to vote

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:

dependencies:
 - python...

Replies: 1 comment 3 replies

Comment options

You must be logged in to vote
3 replies
@betolink
Comment options

@itxashancode
Comment options

@SashaNasonova
Comment options

Answer selected by SashaNasonova
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants