Skip to content

Splitting environment.yml into only the runtime depdendencies? #703

@scottstanie

Description

@scottstanie

Hi, what are the thoughts on having just the requirements needed for running in the environment.yml?

I ask because I tried to install raider-base in my "catch-all" geospatial environment, and while I do have basically everything in there, the hard pin of

- jsonschema==3.2.0  # this is for ASF DAAC ingest schema validation

meant I couldn't install it.
Alternatively, we could remove some of them from the feedstock requirements list: https://github.com/conda-forge/raider-feedstock/blob/main/recipe/meta.yaml#L56 (I see that jsonschema is only used in one test)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions