There are too many optional dependencies listed as part if the base requirements for the conda-forge package. This is creating situations where conflicting dependencies make it so that the PyPI package is preferred when drafting a conda recipe for a project requiring PyWPS.
|
dependencies = [ |
|
"humanize >=4.5.0", |
|
"jinja2 >=3.1.0", |
|
"jsonschema >=4.20.0", |
|
"lxml >=6.0.2", |
|
"markupsafe >=3.0.3", |
|
"numpy >=1.22.2", # not directly required, pinned by Snyk to avoid a vulnerability |
|
"owslib >=0.35.0", |
|
"python-dateutil", |
|
"requests >=2.32.5", |
|
"sqlalchemy >=2.0.44", |
|
"urllib3 >=2.5.0", # not directly required, pinned by Snyk to avoid a vulnerability |
|
"werkzeug >=3.1.4", |
|
] |
conda-forge recipe: https://github.com/conda-forge/pywps-feedstock/blob/main/recipe/meta.yaml
There are too many optional dependencies listed as part if the base requirements for the conda-forge package. This is creating situations where conflicting dependencies make it so that the PyPI package is preferred when drafting a conda recipe for a project requiring PyWPS.
pywps/pyproject.toml
Lines 35 to 48 in 5da4f20
conda-forge recipe: https://github.com/conda-forge/pywps-feedstock/blob/main/recipe/meta.yaml